From: anupbehare at gmail.com <anupbehare@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] dts support in u-boot
Date: Mon, 30 Nov 2009 10:01:28 +0000 [thread overview]
Message-ID: <001485f645b49e0a49047993b9b0@google.com> (raw)
In-Reply-To: <4B0FE776.9050106@gmail.com>
Hi Jerry,
Thanks for the information.
Please find my understanding about dts:
1. I will have to create board specific *.dts file.
2. Need to download latest dtc compiler.
3. Compile dts file using dtc compiler which will generate *.dtb file
4. Enable following macros in u-boot code
#define CONFIG_OF_LIBFDT
#define CONFIG_OF_BOARD_SETUP
5. Apart from these macros no code changes in u-boot source code.
Thanks,
Anup B.
On 27-Nov-2009 8:21pm, Jerry Van Baren <gvb.uboot@gmail.com> wrote:
> Hi Anup,
> anupbehare at gmail.com wrote:
> Hi,
> I am porting u-boot on ppc440x5 core based board. I need to support dts
> in uboot.
> As i am new to dts, can anyone please let me know the procedure to
> support it in uboot?
> Thanks,
> Anup B.
> It is already supported in u-boot.
> http://www.denx.de/wiki/view/DULG/UBootCmdFDT>
> You will need to create a .dts file to describe your board, compile it
> with the dtc compiler, and boot using either the 3 parameter version of
> bootm or using a FIT all-in-one image (preferred).
> txt>
> See also the linux documentation:
> booting-without-of.txt>
> and some more FDT background:
> http://www.denx.de/wiki/view/U-Boot/UBootFdtInfo#Background_Information_on_Flatte>
> If you have specific questions after reading the above, ask away.
> Best regards,
> gvb
next prev parent reply other threads:[~2009-11-30 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 14:11 [U-Boot] dts support in u-boot anupbehare at gmail.com
2009-11-27 14:51 ` Jerry Van Baren
2009-11-30 10:01 ` anupbehare at gmail.com [this message]
2009-12-01 12:11 ` Jerry Van Baren
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=001485f645b49e0a49047993b9b0@google.com \
--to=anupbehare@gmail.com \
--cc=u-boot@lists.denx.de \
/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