All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:09:56 -0500	[thread overview]
Message-ID: <4E6002B4.90503@freescale.com> (raw)
In-Reply-To: <20110901215931.D4D0B13B8A29@gemini.denx.de>

Wolfgang Denk wrote:
> What sort of "confusion" do you have?  I see two situations:  in
> 99.99% of all cases U-Boot is just a means to boot an OS, and nobody
> cares a bit about the actual U-Boot output, as long as the OS is
> runnign after a few seconds, and rather sooner than later. 

The confusion stems mostly from the fact that we've been displaying this
information for years.  If suddenly we stop displaying it, people are going to
think that something is wrong.  Also, you need to know which U-Boot you're
running before you boot the kernel, because the device tree needs to match.  No
one is going to think to use the 'bdinfo' command to find it.

Many board configurations come in 32-bit and 36-bit versions.  E.g.

make P1022DS_config
vs.
make P1022DS_36BIT_config

The problem is that this isn't standard.  "make P1022DS" builds a 32-bit U-Boot.
 But "make P4080DS" builds a 36-bit U-Boot.  So we've been displaying the
address map size at boot time in some situations, but not all.  My patch makes
this standard.

> For a few
> use cases where developers are working on a board, they might wonder
> which state a board is in - then itis very useful to have a command to
> display this information any time they are interested in it - even
> without having to reboot the system.

I agree with adding that information to the bdinfo command.  I'm just worried
about having it available only there.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2011-09-01 22:09 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
2011-09-01 21:59         ` Wolfgang Denk
2011-09-01 22:09           ` Timur Tabi [this message]
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=4E6002B4.90503@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.