public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] using a flat device tree to drive u-boot config
Date: Sun, 03 Aug 2008 17:47:02 +0200	[thread overview]
Message-ID: <20080803154702.84435248CD@gemini.denx.de> (raw)
In-Reply-To: Your message of "Sun, 03 Aug 2008 08:57:55 EDT." <9e4733910808030557t269eb1fye375d66f8bb7f200@mail.gmail.com>

In message <9e4733910808030557t269eb1fye375d66f8bb7f200@mail.gmail.com> you wrote:
>
> > No, no, no. The DTB *must not* be included with the U-Boot image.  It
> >  shall  always  be  kept  separate  so we canupdate it independently -
> >  otherwise you lose a lot of advantages.
> 
> A DTB is only about 8K. I was thinking that a user supplied one would
> override the one contained inside uboot.

Then you have to take special care  that  the  DTB  is  flash  sector
aligned  and sufficiently padded - this extra effort and introduces a
new, avoidable single point of failure. If the  DTB  can  be  at  any
flash location, you can for example have a fall-back version which is
used  to bring up U-Boot in a minimal configuration for recovery mode
if the new DTB fails to work.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Space is big. You just won't believe how vastly, hugely, mind-
bogglingly big it is. I mean, you may think it's a long way down the
road to the drug store, but that's just peanuts to space.
                              -- The Hitchhiker's Guide to the Galaxy

  reply	other threads:[~2008-08-03 15:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 15:07 [U-Boot-Users] using a flat device tree to drive u-boot config Kumar Gala
2008-07-28 17:28 ` Ben Warren
2008-07-28 17:32   ` Scott Wood
2008-07-28 17:35     ` Ben Warren
2008-07-28 17:43       ` Scott Wood
2008-07-28 18:05         ` Ben Warren
2008-07-28 18:59           ` Scott Wood
2008-07-29  8:26           ` André Schwarz
2008-07-29  8:41             ` Wolfgang Grandegger
2008-07-29  9:09               ` André Schwarz
2008-08-03  1:10         ` Jerry Van Baren
2008-07-29 16:41     ` Timur Tabi
2008-07-28 17:40 ` Grant Likely
2008-07-28 18:17   ` Kumar Gala
2008-07-28 19:07     ` Scott Wood
2008-07-29  7:54     ` Haavard Skinnemoen
2008-07-28 18:13 ` Wolfgang Grandegger
2008-07-28 18:19   ` Kumar Gala
2008-07-29 14:30     ` Jon Loeliger
2008-07-29 15:51       ` Robert Schwebel
2008-07-29 15:51 ` Robert Schwebel
2008-07-29 16:46 ` Timur Tabi
2008-08-03  1:58   ` Jon Smirl
2008-08-03  7:51     ` Wolfgang Denk
2008-08-03 12:57       ` Jon Smirl
2008-08-03 15:47         ` Wolfgang Denk [this message]
2008-08-03 17:49           ` Timur Tabi
2008-08-03 19:06             ` Grant Likely
2008-08-03 20:08               ` Timur Tabi
2008-08-04  8:08                 ` Albert ARIBAUD
2008-08-04  7:16               ` Jens Gehrlein
2008-08-03 19:45             ` Wolfgang Denk
2008-08-04 14:33               ` Timur Tabi
2008-08-04 15:31                 ` Wolfgang Denk
2008-08-04 15:36                   ` Timur Tabi
2008-08-03 20:47         ` Andrew Dyer
2008-08-04 15:02       ` Jon Smirl
2008-08-04 15:05         ` Timur Tabi

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=20080803154702.84435248CD@gemini.denx.de \
    --to=wd@denx.de \
    --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