From: Larry Johnson <lrj@acm.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Running Linux from ARCH=powerpc on Sequoia board
Date: Wed, 23 Apr 2008 21:11:30 -0400 [thread overview]
Message-ID: <480FDE42.6040302@acm.org> (raw)
In-Reply-To: <200804231512.03751.sr@denx.de>
Stefan Roese wrote:
> Hi Larry,
>
> On Tuesday 22 April 2008, Grant Likely wrote:
>>> Currently, I can build "zImage" for Sequoia using the powerpc
>>> architecture, and load it using U-Boot without a separate FDT binary.
>>> Is this the best way to run a Linux from the powerpc tree?
>> Sorry, I don't understand what you're asking.
>>
>> There are two way to boot a Linux image from arch/powerpc.
>>
>> 1) build a uImage and get u-boot to pass a device tree blob (if your u-boot
>> had device tree support)
>> 2) build a cuImage which wraps the device tree in the kernel image.
>
> Correct. Personally I prefer 1), since it makes the Linux ports easier. No
> bootwrapper is needed in this case. And all the "infrastructure" for fdt
> enabled U-Boot images for 4xx is available. Please take a look at
> sequoia.c/.h and search for CONFIG_OF_LIBFDT.
>
> Just let me know if this is not clear or if you have additional questions.
>
> Best regards,
> Stefan
>
> =====================================================================
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
> =====================================================================
Thanks Stefan, Grant, and Wolfgang for your comments. Method 2 is
working for me, as it turns out that files "cuImage.sequoia and "zImage"
are identical.
I'd prefer to use method one. Here's an abbreviated listing of what I
get when I try.
<listing>
=> tftp 200000 sequoia/uImage
[...]
Bytes transferred = 1497002 (16d7aa hex)
=> tftp 1000000 sequoia/sequoia.dtb
[...]Bytes transferred = 6659 (1a03 hex)
=> run ramargs addmtd addip addide addtty; bootm 200000 ${ramdisk_addr} 1000000
## Booting kernel from Legacy Image at 00200000 ...
Image Name: Linux-2.6.25-rc8-01262-g80afde7
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1496938 Bytes = 1.4 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Flattened Device Tree blob at 01000000
Booting using the fdt blob at 0x1000000
## Loading init Ramdisk from Legacy Image at fc400000 ...
Image Name: sequoia Ramdisk Rev 006
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 19409859 Bytes = 18.5 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Device Tree to 007fe000, end 007ffa02 ... OK
fdt_chosen: FDT_ERR_NOSPACE
ERROR: /chosen node create failed - must RESET the board to recover.
U-Boot 1.3.2-00497-g58c5376 (Apr 23 2008 - 16:24:13)
[...]
</listing>
The file "sequoia.dtb was created by
$dtc dts/sequoia.dts -O dtb -o sequoia.dtb
Can anyone tell me what went wrong?
Best regards,
Larry
next prev parent reply other threads:[~2008-04-24 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 18:55 [U-Boot-Users] Running Linux from ARCH=powerpc on Sequoia board Larry Johnson
2008-04-22 19:18 ` Grant Likely
2008-04-23 13:12 ` Stefan Roese
2008-04-24 1:11 ` Larry Johnson [this message]
2008-04-24 2:20 ` Grant Likely
2008-04-24 4:31 ` Stefan Roese
2008-04-22 19:48 ` Wolfgang Denk
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=480FDE42.6040302@acm.org \
--to=lrj@acm.org \
--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 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.