linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: christophe leroy <christophe.leroy@c-s.fr>
To: K Richard Pixley <rpixley@graphitesystems.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: embedding dtb file into kernel
Date: Sat, 14 Feb 2015 11:29:50 +0100	[thread overview]
Message-ID: <54DF239E.6080705@c-s.fr> (raw)
In-Reply-To: <54DE3732.2080707@graphitesystems.com>


Le 13/02/2015 18:41, K Richard Pixley a écrit :
> I'm having trouble figuring out how to embed a dtb file into my 
> kernel.  I'm thinking that there should be a standard, architecture 
> independent facility for this akin to initramfs, yes?
>
> Could someone please either point me to the standard facility, 
> relevant doc, a currently building board that uses the standard 
> facility, or outline what needs to be done to do this with a new board?
>
> If it matters, (I can't think why it would), I'm working with powerpc 
> on a 3.10 kernel.  But if there are better facilities in other 
> versions I'd appreciate hearing about that too.
>
> Thank you in advance.
>

Hi,

The device tree (DTB file) is not supposed to be embedded into the 
kernel but loaded independently by the boot loader (for instance Uboot).
Then a pointer to the device tree is handed over by Uboot to the kernel 
when calling the _start function.

You also have in arch/powerpc/boot/ a facility called cuboot which 
allows to create a ppcboot image with kernel and device tree bound together.

Christophe

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
http://www.avast.com

  reply	other threads:[~2015-02-14 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 17:41 embedding dtb file into kernel K Richard Pixley
2015-02-14 10:29 ` christophe leroy [this message]
2015-02-15 13:44 ` Stefano Babic

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=54DF239E.6080705@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=rpixley@graphitesystems.com \
    /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;
as well as URLs for NNTP newsgroup(s).