From: aperez@igalia.com (Adrian Perez de Castro)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to use .dts file for Kernel Image Compilation
Date: Thu, 23 Jan 2014 17:45:19 +0200 [thread overview]
Message-ID: <87a9emvh0w.fsf@igalia.com> (raw)
In-Reply-To: <CA+V-a8tSWYkeHv8Qfy0i6eCdkn=y3jiTZPLF3PoEOoGzEV-m2Q@mail.gmail.com>
Hello,
Prabhakar Lad <prabhakar.csengg@gmail.com> writes:
> On Wed, Jan 22, 2014 at 3:41 PM, sanchayan maity
> <victorascroft@gmail.com> wrote:
>>
>> I want to know if this is the correct way of specifying a device tree file
>> for which .dtb has been generated?
>>
>> The kernel version for which i am trying to do this is 3.12.6.
>>
> If your configuration supports (defconfig) DT booting for your platform you
> can build .dtb by just replacing the "uImage" to "dtbs" in the command what you
> used for building the uImage.
>
> Note:- For DT booting there should be also support in the U-Boot.
Alternatively, if your U-Boot does not support loading a DT, you can
enable the ARM_APPENDED_DTB option in the kernel, and append the .dtb
file to your kernel image, like this:
cat path/to/zImage path/to/board.dtb > zImageWithDT
The resulting file can be passed to U-Boot's ?mkimage? as a normal
kernel. With this options, if the kernel detects that a DT has
already been loaded by the bootloader, it will use it, otherwise
it will try to read the .dtb file that has been appended to it.
Cheers,
-Adrian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140123/fc4e7bd7/attachment.bin
next prev parent reply other threads:[~2014-01-23 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 10:11 How to use .dts file for Kernel Image Compilation sanchayan maity
2014-01-23 6:46 ` Prabhakar Lad
2014-01-23 15:45 ` Adrian Perez de Castro [this message]
2014-01-28 18:08 ` sanchayan maity
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=87a9emvh0w.fsf@igalia.com \
--to=aperez@igalia.com \
--cc=kernelnewbies@lists.kernelnewbies.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.