From: Wolfgang Grandegger <wg@grandegger.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: How to use the device tree for lite5200
Date: Wed, 06 Dec 2006 20:16:49 +0100 [thread overview]
Message-ID: <45771721.1080102@grandegger.com> (raw)
In-Reply-To: <B1186D1B-C47D-46C3-B928-8FDE4A55363B@kernel.crashing.org>
Kumar Gala wrote:
>
> On Dec 6, 2006, at 9:59 AM, Wolfgang Grandegger wrote:
>
>> Hello,
>>
>> I want to boot PowerPC Linux 2.6.19 on my Icecube board but I didn't
>> succeed yet to get lite5200.dts compiled and an appropriate image
>> created:
>>
>> $ dtc -b0 lite5200.dts
>> DTC: dts->dts on file "lite5200.dts"
>> ERROR: Missing /chosen node
>> Input tree has errors
>>
>> What is the procedure to make and boot an uImage for the U-Boot
>> bootloader. I read about the third argument for bootm but did not
>> understand how to use it.
>
> How have you booted in the past? Do you tftp down the images or run
> from flash?
Yes, at least for development.
> Here's an example assuming you have a kernel image at address $loadaddr
> and the dtb at $ftaddr
>
> dtc -b0 -Idts -Odtb -V16 lite5200.dts > lite5200.dtb
>
> download lite5200.dtb to the system
>
> => bootm $loadaddr - $fdtaddr
Great, that worked with the additional "-f" option, as suggested by
Grant. Now I can boot the kernel but BESTCOM and FEC support seem still
missing. Are there already patches around?
Thanks to all who replied.
Wolfgang.
next prev parent reply other threads:[~2006-12-06 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 15:59 How to use the device tree for lite5200 Wolfgang Grandegger
2006-12-06 16:09 ` Kumar Gala
2006-12-06 19:16 ` Wolfgang Grandegger [this message]
2006-12-06 23:11 ` Grant Likely
2006-12-07 9:13 ` Wolfgang Grandegger
2006-12-06 16:20 ` Grant Likely
2006-12-06 16:21 ` Grant Likely
2006-12-06 17:49 ` Jon Loeliger
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=45771721.1080102@grandegger.com \
--to=wg@grandegger.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.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 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).