All of lore.kernel.org
 help / color / mirror / Atom feed
From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: [Query] Does u-boot processes dtb file
Date: Fri, 14 Sep 2012 09:35:30 +0200	[thread overview]
Message-ID: <5052DE42.6080109@de.bosch.com> (raw)
In-Reply-To: <CAKohpomubFQMj2uoP+Pb1xBsO7B14W3nR1ddSQ-ajRERNBQ+kg@mail.gmail.com>

On 14.09.2012 09:16, Viresh Kumar wrote:
> On 14 September 2012 12:38, Dirk Behme <dirk.behme@de.bosch.com> wrote:
>> Working with U-Boot, to my understanding U-Boot modifies ('patches') the dtb
>> read from the boot device before passing it to the kernel. It e.g. adds the
>> kernel command line and the memory size you specify in U-Boot to the dtb.
> 
> Thanks for your response.
> 
> But, if this information is also embedded in the dts earlier, will my workaround
> of filling r2 work?

I think so, but I never tried it. It's on my todo list to try this ;) If 
you add all the information needed in the dts file and the resulting dtb 
file is identical to the 'patched' dtb U-Boot passes to the kernel, 
there should be no difference (?).

> Is filling bootargs and memory size the only stuff or some other things too?

I'm not totally sure on this. You could debug this: (a) Take the dtb 
file from your boot device. (b) dump the dtb file U-Boot passes to the 
kernel (i.e. do a memory dump from the pointer U-Boot passes in r2). 
Compare (a) and (b) with a binary diff.

Best regards

Dirk

  reply	other threads:[~2012-09-14  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  6:58 [Query] Does u-boot processes dtb file Viresh Kumar
2012-09-14  7:08 ` Dirk Behme
2012-09-14  7:16   ` Viresh Kumar
2012-09-14  7:35     ` Dirk Behme [this message]
2012-09-14  9:16       ` Stefan Roese

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=5052DE42.6080109@de.bosch.com \
    --to=dirk.behme@de.bosch.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.