public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis_blanchard@mentor.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Honor /memory/reg node in DTB files
Date: Wed, 08 Dec 2010 10:30:25 -0800	[thread overview]
Message-ID: <4CFFCEC1.6000103@mentor.com> (raw)
In-Reply-To: <20101207190936.EC285D0E429@gemini.denx.de>

On 12/07/2010 11:09 AM, Wolfgang Denk wrote:
> There are many board vendors who shipt boards with different
> configurations - with or without NAND flash; with or without other
> peripherals like CAN contollers, LCD, etc.; with different LCD sizes
> and types, in portrait or landscape orientation, etc.  Some of these
> features can be determined by probing the hardware, others (like the
> orientation of a LCD) cannot.  It is sometimes a maintenance nightmare
> to provide tens of different configurations of U-Boot for a single
> product.  Being able to cinfigure available hardware through the DT,
> and using a single common binary image of U-Boot for such systems
> would be a great benefit.
That's fine, but so far I don't see how it's related. This is 
information u-boot needs during its own initialization, right?

We need a way for our tools to specify information to the kernels' 
initialization, and still want u-boot to do all the hardware 
configuration it does today. It really doesn't matter to us if in the 
future u-boot uses device trees for that configuration: we just need a 
way to interact with the kernels.

Hollis Blanchard
Mentor Graphics, Embedded Systems Division

  reply	other threads:[~2010-12-08 18:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07  0:56 [U-Boot] [PATCH] Honor /memory/reg node in DTB files Deepak Saxena
2010-12-07  6:52 ` Wolfgang Denk
2010-12-07 18:05   ` Deepak Saxena
2010-12-07 19:09     ` Wolfgang Denk
2010-12-08 18:30       ` Hollis Blanchard [this message]
2010-12-08 20:53         ` Wolfgang Denk
2010-12-08 21:08           ` Hollis Blanchard
2010-12-08 21:38             ` Wolfgang Denk
2010-12-08 22:08               ` Dan Malek
2010-12-08 22:34                 ` Wolfgang Denk
2010-12-08 23:33                   ` Peter Tyser
2010-12-08 23:59                   ` Dan Malek
2010-12-09 10:00                     ` Wolfgang Denk
2010-12-10 18:04                   ` Deepak Saxena
2010-12-12 21:19                     ` Wolfgang Denk
2010-12-08 18:59       ` Deepak Saxena
2010-12-08 21:00         ` Wolfgang Denk
2010-12-07 18:40   ` Hollis Blanchard
2010-12-07 19:21     ` Wolfgang Denk
2010-12-07 21:22 ` Scott Wood
2010-12-08 18:59   ` Deepak Saxena
2010-12-08 19:11     ` Scott Wood
2010-12-08 19:22       ` Dan Malek
2010-12-08 19:33         ` Scott Wood
2012-03-31 19:32 ` Marek Vasut

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=4CFFCEC1.6000103@mentor.com \
    --to=hollis_blanchard@mentor.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