Skip to contentSkip to conversation

Nokia RX-51: Use generic board

PATCH In review Pali Rohár 4 participants 7 messages Jan 15, 2015 – Feb 1, 2015

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Nokia RX-51: Use generic board

Generic board with #define CONFIG_SYS_GENERIC_BOARD is working fine. There is no visible difference between legacy and generic board code.

---
 include/configs/nokia_rx51.h |    1 +
 1 file changed, 1 insertion(+)
include/configs/nokia_rx51.h +1 -0
index 982b689..46fc91e 100644
@@ -28,6 +28,7 @@
 #define CONFIG_OMAP3_RX51		/* working with RX51 */
 #define CONFIG_SYS_L2CACHE_OFF		/* pretend there is no L2 CACHE */
 #define CONFIG_OMAP_COMMON
+#define CONFIG_SYS_GENERIC_BOARD
 
 #define CONFIG_MACH_TYPE		MACH_TYPE_NOKIA_RX51
 
Signature · 1 line
1.7.9.5
#1 lore raw

PATCH 1/1 Nokia RX-51: Use generic board

Quoted 4 lines · Pali Roh?r

Generic board with #define CONFIG_SYS_GENERIC_BOARD is working fine. There is no visible difference between legacy and generic board code.

Thanks!

(I added Albert Aribaud to the To: list, as he's an ARM maintainer IIRC).

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#2 lore raw
In reply to Pali Rohár
Quoted 5 lines · Pali Roh?r

Generic board with #define CONFIG_SYS_GENERIC_BOARD is working fine. There is no visible difference between legacy and generic board code.

Applied to u-boot-ti/master, thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150130/c5c1df66/attachment.sig>
#3 lore raw
Quoted 9 lines · On Friday 30 January 2015 15:19:53 Tom Rini wrote:
Quoted 6 lines · Pali Roh?r

Generic board with #define CONFIG_SYS_GENERIC_BOARD is working fine. There is no visible difference between legacy and generic board code.

Applied to u-boot-ti/master, thanks!

Tom, or anybody else, in future when you are going to change some parts in u-boot and remove boards which do not convert in time... please can you contact me about it (via email, I see that contact info in file board/nokia/rx51/MAINTAINERS is correct)? I'm not following u-boot ML and I really did not know that conversion to generic board code is required before end of last year...

Basically Maemo users & developers use uboot v2013.04 version and for Nokia N900 there is no new functionality in new uboot versions. So there is nothing like "new features & fixed bugs" motivation.

But I do not want to see n900 board code removed from uboot as uboot bootloader is for n900 really useful (most for end-users who does not even know about existence of git, uboot ML, etc).

Signature · 9 lines
Pali Roh?r
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150130/48e686c3/attachment.sig>
#4 lore raw
Quoted 18 lines · Pali Roh?r
Quoted 9 lines · On Friday 30 January 2015 15:19:53 Tom Rini wrote:
Quoted 6 lines · Pali Roh?r

Generic board with #define CONFIG_SYS_GENERIC_BOARD is working fine. There is no visible difference between legacy and generic board code.

Applied to u-boot-ti/master, thanks!

Tom, or anybody else, in future when you are going to change some parts in u-boot and remove boards which do not convert in time... please can you contact me about it (via email, I see that contact info in file board/nokia/rx51/MAINTAINERS is correct)? I'm not following u-boot ML and I really did not know that conversion to generic board code is required before end of last year...

Quoted 8 lines

Basically Maemo users & developers use uboot v2013.04 version and for Nokia N900 there is no new functionality in new uboot versions. So there is nothing like "new features & fixed bugs" motivation.

But I do not want to see n900 board code removed from uboot as uboot bootloader is for n900 really useful (most for end-users who does not even know about existence of git, uboot ML, etc).

Before we do the (very soon now, -rc1 comes Monday) nuking, any board with a MAINTAINERS will get a CC, yes. But I expect MAINTAINERS to do some sort of sanity test at least once every few releases, especially since we have a regular release cycle.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150130/dc8eee16/attachment.sig>
#5 lore raw
Quoted 30 lines · On Friday 30 January 2015 17:09:48 Tom Rini wrote:
Quoted 24 lines · Pali Roh?r
Quoted 9 lines · On Friday 30 January 2015 15:19:53 Tom Rini wrote:
Quoted 6 lines · Pali Roh?r

Generic board with #define CONFIG_SYS_GENERIC_BOARD is working fine. There is no visible difference between legacy and generic board code.

Applied to u-boot-ti/master, thanks!

Tom, or anybody else, in future when you are going to change some parts in u-boot and remove boards which do not convert in time... please can you contact me about it (via email, I see that contact info in file board/nokia/rx51/MAINTAINERS is correct)? I'm not following u-boot ML and I really did not know that conversion to generic board code is required before end of last year...

Basically Maemo users & developers use uboot v2013.04 version and for Nokia N900 there is no new functionality in new uboot versions. So there is nothing like "new features & fixed bugs" motivation.

Quoted 4 lines

But I do not want to see n900 board code removed from uboot as uboot bootloader is for n900 really useful (most for end-users who does not even know about existence of git, uboot ML, etc).

Quoted 5 lines

Before we do the (very soon now, -rc1 comes Monday) nuking, any board with a MAINTAINERS will get a CC, yes. But I expect MAINTAINERS to do some sort of sanity test at least once every few releases, especially since we have a regular release cycle.

Sanity test on n900 device means to build image and run it. And it is working. Because uboot write warning message to stdout and n900 screen (where is my stdout) is too small it is very early rewritten by next messages. And if error message is print before uboot set stdout to screen I was not able to read it. So I did not have to know about that warning... Do not remember that community members do not have special equipment for debugging early stage bootloader errors and also do not have special Nokia (TM) serial console cable, pins & handler...

I think it is better to CC maintainers immediately after you decide and create such warning and not one year later.

Signature · 9 lines
Pali Roh?r
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150131/1dd8f1dc/attachment.sig>
#6 lore raw
In reply to Tom Rini

Hello Tom,

Quoted 3 lines · Tom Rini

But I expect MAINTAINERS to do
some sort of sanity test at least once every few releases, especially since we have a regular release cycle.

How about Bcc:ing all maintainers upon each release announcement to the list?

Quoted 2 lines
Signature · 1 line
Tom

Amicalement,

Signature · 1 line
Albert.