From: "Pali Rohár" <pali.rohar@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Nokia RX-51: Use generic board
Date: Sat, 31 Jan 2015 15:19:16 +0100 [thread overview]
Message-ID: <201501311519.16717@pali> (raw)
In-Reply-To: <20150130160948.GB10826@bill-the-cat>
On Friday 30 January 2015 17:09:48 Tom Rini wrote:
> On Fri, Jan 30, 2015 at 03:49:08PM +0100, Pali Roh?r wrote:
> > On Friday 30 January 2015 15:19:53 Tom Rini wrote:
> > > On Thu, Jan 15, 2015 at 10:26:36AM +0100, Pali Roh?r wrote:
> > > > Generic board with #define CONFIG_SYS_GENERIC_BOARD is
> > > > working fine. There is no visible difference between
> > > > legacy and generic board code.
> > > >
> > > > Signed-off-by: Pali Roh?r <pali.rohar@gmail.com>
> > > > Acked-by: Pavel Machek <pavel@ucw.cz>
> > >
> > > 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).
>
> 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.
--
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>
next prev parent reply other threads:[~2015-01-31 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 9:26 [U-Boot] [PATCH] Nokia RX-51: Use generic board Pali Rohár
2015-01-15 20:54 ` Pavel Machek
2015-01-30 14:19 ` [U-Boot] " Tom Rini
2015-01-30 14:49 ` Pali Rohár
2015-01-30 16:09 ` Tom Rini
2015-01-31 14:19 ` Pali Rohár [this message]
2015-02-01 0:16 ` Albert ARIBAUD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201501311519.16717@pali \
--to=pali.rohar@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox