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: Tue, 07 Dec 2010 10:40:40 -0800	[thread overview]
Message-ID: <4CFE7FA8.2030701@mentor.com> (raw)
In-Reply-To: <20101207065234.DC3BB280@gemini.denx.de>

On 12/06/2010 10:52 PM, Wolfgang Denk wrote:
> If you define that the device tree is the "master" for information
> about the memory layout (and potentially other hardware specifics),
> then you should be consequent and pass make U-Boot process this
> information.  We've discussed before that there are a number of cases
> where it would be nice if U-Boot itself could be configured usign a
> device tree.  This appears to be another one.
I *think* what you're suggesting is basically providing u-boot with a 
single device tree, even when it will load multiple operating systems. 
The tree would then look something like this:

/
     cpus
         ...
     memory
         reg = <0 20000000>
     soc
         ...
     partitions
         partition at 0
             memory
                 reg = <0 10000000>
         partition at 1
             memory
                 reg = <10000000 10000000>

U-boot would then be responsible for constructing multiple device trees 
(one for each partition) itself, based on the additional information 
found in the "partitions" node.

Is that correct?

Hollis Blanchard
Mentor Graphics, Embedded Systems Division

  parent reply	other threads:[~2010-12-07 18:40 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
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 [this message]
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=4CFE7FA8.2030701@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