public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@comcast.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] builtin OF tree dtb gone
Date: Sat, 16 Dec 2006 11:07:55 -0500	[thread overview]
Message-ID: <458419DB.7050406@comcast.net> (raw)
In-Reply-To: <005a01c72125$d407b550$1e67a8c0@Jocke>

Joakim Tjernlund wrote:
> While trying out the latest u-boot from my board I noticed that
> support for using a prebuilt OF tree compiled int u-boot is gone.
> The oftree_dtb symbol is gone and I can't find a replacement.
> 
> Why was it removed and is there a replacement?
> 
> If there isn't a replacement I request that
> one is added.
> 
>  Jocke

I'm not the authority on this, but I believe the intent is that you 
compile the blob outside of u-boot and then you can load it into RAM via 
tftp or burn it into flash if you want it permanently on the board. 
Other than having to download and burn two things (u-boot and the dtb 
blob) rather than one, having it burn into flash separately is no 
different from compiling it into the u-boot image and is aesthetically 
much cleaner and more flexible.

The New Improved[tm] bootm command takes address of the OF blob as the 
third parameter (help bootm).

IIRC, Wolfgang was not wild about building the blob into u-boot, it 
really isn't a u-boot "thing."

I am looking into/working on a flattened device tree command that would 
allow you to manipulate a OF blob in flash or RAM like the current env 
variables.  I have a dream of integrating it with the env storage, but 
all this takes time.  (I volunteer for too much - my ego writes checks 
that my brain cannot cash. ;-)

Best regards,
gvb

  parent reply	other threads:[~2006-12-16 16:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16 15:21 [U-Boot-Users] builtin OF tree dtb gone Joakim Tjernlund
2006-12-16 15:45 ` Grant Likely
2006-12-16 17:23   ` Joakim Tjernlund
2006-12-16 16:07 ` Jerry Van Baren [this message]
2006-12-16 16:32   ` Joakim Tjernlund
2006-12-16 17:18     ` Pantelis Antoniou
2006-12-16 18:39       ` Dan Malek
2006-12-16 19:39         ` Joakim Tjernlund
2006-12-16 21:27           ` Dan Malek
2006-12-16 19:04     ` Wolfgang Denk
2006-12-16 19:59       ` Joakim Tjernlund
2006-12-17  0:37         ` Wolfgang Denk
2006-12-17 14:23           ` Joakim Tjernlund
2006-12-17 15:10             ` Grant Likely
2006-12-17 15:40               ` Joakim Tjernlund
2006-12-17 16:07                 ` Joakim Tjernlund
2006-12-17 17:13                   ` Wolfgang Denk
2006-12-17 18:03                     ` Joakim Tjernlund
2006-12-17 23:56                       ` Wolfgang Denk
2006-12-18 14:39                         ` Joakim Tjernlund
2006-12-30 13:10                           ` Joakim Tjernlund
2006-12-17 16:50                 ` Pantelis Antoniou
2007-01-22 21:03                   ` Timur Tabi
2007-01-22 22:06                     ` Wolfgang Denk
2006-12-17 17:10             ` 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=458419DB.7050406@comcast.net \
    --to=gerald.vanbaren@comcast.net \
    --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