From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] powerpc/85xx: standardize display of address map size (32-bit vs. 36-bit)
Date: Thu, 1 Sep 2011 09:54:05 -0500 [thread overview]
Message-ID: <4E5F9C8D.3080503@freescale.com> (raw)
In-Reply-To: <20110901142237.E2D85166C886@gemini.denx.de>
Wolfgang Denk wrote:
> But you are right - I'd much rather see this printed for example as
> part of the "bdinfo" command than with the regular boot messages.
Recently, we've been adding boards that have CONFIG_PCI_SCAN_SHOW defined. Are
you saying that we should not be doing that? That adds a lot more text than my
patch does.
Examples:
http://patchwork.ozlabs.org/patch/108682/
http://patchwork.ozlabs.org/patch/108533/
Kumar, are you okay with not displaying the address map size at all during boot
time? If we bury this information in the 'bdinfo' command, we're going to have
even more confusion as to which U-Boot we're booting.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-09-01 14:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 22:15 [U-Boot] [PATCH 1/2] powerpc/85xx: CONFIG_ENABLE_36BIT_PHYS does not depend on CONFIG_PHYS_64BIT Timur Tabi
2011-08-31 22:15 ` [U-Boot] [PATCH 2/2] powerpc/85xx: standardize display of address map size (32-bit vs. 36-bit) Timur Tabi
2011-09-01 14:07 ` Kumar Gala
2011-09-01 14:13 ` Timur Tabi
2011-09-01 14:22 ` Wolfgang Denk
2011-09-01 14:54 ` Timur Tabi [this message]
2011-09-01 21:59 ` Wolfgang Denk
2011-09-01 22:09 ` Timur Tabi
2011-09-05 14:11 ` Wolfgang Denk
2011-09-02 3:38 ` Kumar Gala
2011-09-02 11:36 ` Tabi Timur-B04825
2011-09-02 13:12 ` Kumar Gala
2011-09-02 13:41 ` Timur Tabi
2011-09-02 18:24 ` Kumar Gala
2011-09-02 18:25 ` Timur Tabi
2011-09-02 22:10 ` Wolfgang Denk
2011-09-05 14:15 ` Wolfgang Denk
2011-09-05 14:14 ` 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=4E5F9C8D.3080503@freescale.com \
--to=timur@freescale.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