From: K Richard Pixley <rpixley@graphitesystems.com>
To: Tim Bird <tim.bird@sonymobile.com>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Re: embedding dtb file into kernel
Date: Thu, 12 Feb 2015 14:30:06 -0800 [thread overview]
Message-ID: <54DD296E.7080901@graphitesystems.com> (raw)
In-Reply-To: <54DD22BF.4040607@sonymobile.com>
On 2/12/15 14:01 , Tim Bird wrote:
> On 02/12/2015 11:33 AM, K Richard Pixley wrote:
>> 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.
> The normal method is just to cat the two files together, like so:
> $ cat zImage <filename>.dtb > zImage_w_dtb
>
> See https://community.freescale.com/thread/315543 for one example, on ARM.
> I'm not sure what the status is for appended DTBs on powerpc, but it's
> easy enough you can just try it and see what happens.
> -- Tim
Thanks!
How do I tell the kernel where to find that dtb? Is there a relevant
config option?
--rich
next prev parent reply other threads:[~2015-02-12 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 19:33 embedding dtb file into kernel K Richard Pixley
2015-02-12 22:01 ` Tim Bird
2015-02-12 22:30 ` K Richard Pixley [this message]
2015-02-13 0:56 ` Tim Bird
2015-02-13 6:10 ` Rob Landley
2015-02-13 6:15 ` Hugh Blemings
2015-02-13 13:31 ` Sam Protsenko
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=54DD296E.7080901@graphitesystems.com \
--to=rpixley@graphitesystems.com \
--cc=linux-embedded@vger.kernel.org \
--cc=tim.bird@sonymobile.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).