From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tegra: Specify debugging serial port at boot.
Date: Wed, 21 Mar 2012 10:29:07 -0600 [thread overview]
Message-ID: <4F6A01D3.3020506@wwwdotorg.org> (raw)
In-Reply-To: <20120321093808.E6E72202A4D@gemini.denx.de>
On 03/21/2012 03:38 AM, Wolfgang Denk wrote:
...
> To bring this to a constructive end:
>
> It appears that all you are trying here is an annoying, but somewhat
> unlikely error situation. As marked above (see *), it might make
> sense to think of alternative ways to find out what the console port
> might be. One possibility to do this is to use the environment.
> You need access to the environment anyway to initialize the console
> port (for reading the "baudrate" setting). So why not encoding the
> console UART port for example as part of a "hwconfig" setting? This
> setting could be auto-initialized when you load a DT on this board
> (eventually after verifying that it works).
>
> OK, there is still a chance that the environment settings are missing
> or incorrect _and_ the DT cannot be loaded, but the probability for
> such a double-fault is much, much smaller.
>
> Could this be an acceptable solution for you?
I'd prefer to just have a different U-Boot (build) config for each HW
configuration, and define the console UART as part of that configuration
using the existing defines that are for that purpose.
If we put the UART ID into the environment, then we either need to:
a) Have a different U-Boot configuration anyway, in order to define the
different environment during the U-Boot build process.
b) Post-process the U-Boot binary after building it, in order to modify
the environment that's contained in that binary.
Neither of those seem better to me that simply putting the UART ID into
the U-Boot config directly in the first place.
next prev parent reply other threads:[~2012-03-21 16:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 19:57 [U-Boot] [PATCH] tegra: Specify debugging serial port at boot Stephen Warren
2012-03-20 20:13 ` Simon Glass
2012-03-20 21:17 ` Stephen Warren
2012-03-20 23:28 ` Graeme Russ
2012-03-20 23:33 ` Simon Glass
2012-03-20 23:52 ` Graeme Russ
2012-03-21 0:02 ` Simon Glass
2012-03-21 0:17 ` Graeme Russ
2012-03-21 0:19 ` Simon Glass
2012-03-21 0:39 ` Graeme Russ
2012-03-21 1:18 ` Simon Glass
2012-03-21 1:46 ` Graeme Russ
2012-03-21 0:42 ` Stephen Warren
2012-03-21 1:54 ` Simon Glass
2012-03-21 9:38 ` Wolfgang Denk
2012-03-21 10:35 ` Graeme Russ
2012-03-21 16:49 ` Stephen Warren
2012-03-21 16:59 ` Simon Glass
2012-03-21 17:09 ` Stephen Warren
2012-03-21 17:13 ` Simon Glass
2012-03-21 17:38 ` Stephen Warren
2012-03-21 17:50 ` Simon Glass
2012-03-21 18:25 ` Stephen Warren
2012-03-21 23:00 ` Wolfgang Denk
2012-03-21 22:56 ` Wolfgang Denk
2012-03-21 23:01 ` Simon Glass
2012-03-21 23:07 ` Wolfgang Denk
2012-03-21 23:16 ` Simon Glass
2012-03-22 13:25 ` Wolfgang Denk
2012-03-22 15:17 ` Simon Glass
2012-03-22 23:00 ` Wolfgang Denk
2012-03-22 23:03 ` Simon Glass
2012-03-22 23:07 ` Wolfgang Denk
2012-03-22 23:41 ` Graeme Russ
2012-03-23 15:08 ` Simon Glass
2012-03-22 15:40 ` Doug Anderson
2012-03-21 16:29 ` Stephen Warren [this message]
2012-03-21 22:52 ` Wolfgang Denk
2012-03-20 23:29 ` Simon Glass
2012-03-21 9:19 ` Wolfgang Denk
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=4F6A01D3.3020506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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