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, 24 Jun 2013 16:30:54 -0400 [thread overview]
Message-ID: <20130624203054.GA28078@bill-the-cat> (raw)
In-Reply-To: <20130622113311.1d1b1746@lilith>
On Sat, Jun 22, 2013 at 11:33:11AM +0200, Albert ARIBAUD wrote:
> Hi Tom,
>
> On Tue, 11 Jun 2013 11:53:42 -0400, Tom Rini <trini@ti.com> wrote:
>
> > On Thu, Jun 06, 2013 at 04:30:38PM -0500, Dan Murphy wrote:
> >
> > > Correct the console sys prompt to display the correct processor
> > > and the corrent board
> > >
> > > Signed-off-by: Dan Murphy <dmurphy@ti.com>
> > > Reported-by: Lubomir Popov <lpopov@mm-sol.com>
> >
> > Reviewed-by: Tom Rini <trini@ti.com>
> >
> > But personally, this is why I'm a fan of 'U-Boot # ' as the prompt :)
>
> I'd like it too if we could simply have all boards using the same
> prompt, but there might be some scripts out there which rely on the
> prompt being something else than "U-Boot # ' or worse yet, using the
> prompt to determine which variant of the HW the scripts are dealing
> with.
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.
--
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/20130624/0f247fb9/attachment.pgp>
next prev parent reply other threads:[~2013-06-24 20:30 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 [this message]
2013-06-27 7:00 ` Albert ARIBAUD
2013-07-15 16:36 ` Tom Rini
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=20130624203054.GA28078@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