From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: omap5_uevm: Correct the console sys prompt for 5432
Date: Mon, 15 Jul 2013 12:36:21 -0400 [thread overview]
Message-ID: <20130715163621.GF12301@bill-the-cat> (raw)
In-Reply-To: <20130627090059.1b01e0f6@lilith>
On Thu, Jun 27, 2013 at 09:00:59AM +0200, Albert ARIBAUD wrote:
> Hi Tom,
>
> On Mon, 24 Jun 2013 16:30:54 -0400, Tom Rini <trini@ti.com> wrote:
[snip]
> > True. Looking ahead however, given device trees and the need to know
> > what tree to request/load, I hope more boards will go with enabling
> > CONFIG_ENV_VARS_UBOOT_CONFIG and can then use cpu/board/board_name as
> > needed to determine those things at run-time.
>
> How about announcing (as in, "letting the whole world know by slipping
> it in our public announcement of 2013.07") that custom prompts will be
> deprecated starting with 2013.10 and that targets still having them by
> 2014.01 will be retired?
>
> That's what we did for ARM ELF relocation IIRC.
>
> Of course, that would require a few round of e-mails to maintainers, at
> least to those whose targets' config header files still have custom
> prompts when reaching 2014.01-rc1; and there will be some yelling that
> such or such board has been dropped from U-Boot and why were users not
> told, etc.
>
> Alternatively, we could announce and deprecate in 2013.10 and remove
> all custom prompts in 2013.14 ourselves, then wait for annoyed people
> to yell at us, and advise them to enable CONFIG_ENV_VARS_UBOOT_CONFIG
> and uptate their scripts. Less prep work, slightly more yelling.
>
> We could even shift the schedule, deprecate for 2013.07 and remove in
> 2013.10. Same amount of work, yelling goes away earlier.
>
> My vote goes to this last proposal. :)
With the self-inflicted bootm/FIT problems, I set this email aside for a
bit longer than I had wanted. My plan, right now, is to just start with
letting the wider world know, in the releae email, that hey, we have
more reliable methods of determing what board you are on, at run time.
And seeing where things go from there.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130715/b569cfce/attachment.pgp>
prev parent reply other threads:[~2013-07-15 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 21:30 [U-Boot] [PATCH] arm: omap5_uevm: Correct the console sys prompt for 5432 Dan Murphy
2013-06-11 15:53 ` Tom Rini
2013-06-22 9:33 ` Albert ARIBAUD
2013-06-24 20:30 ` Tom Rini
2013-06-27 7:00 ` Albert ARIBAUD
2013-07-15 16:36 ` Tom Rini [this message]
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=20130715163621.GF12301@bill-the-cat \
--to=trini@ti.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