Hello,

Prabhakar Lad [off-list ref] writes:

On Wed, Jan 22, 2014 at 3:41 PM, sanchayan maity
[off-list ref] wrote:

quoted

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