From: Detlev Zundel <dzu@denx.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Boot 2.6.26 (or similar) on mpc5200 using powerpc
Date: Thu, 04 Sep 2008 14:05:44 +0200 [thread overview]
Message-ID: <m28wu8f753.fsf@ohwell.denx.de> (raw)
In-Reply-To: 135716.58253.qm@web23107.mail.ird.yahoo.com
Hi Angelo,
> Does anyone boots on mpc5200 board, the linux kernel 2.6.26 (or .24 .25) using
> ARCH=powerpc?
Sure, many people do this successfully.
> Looking on web i known that it's very different from ppc mode and the right
> procedure to follow is:
>
> 1 - make lite5200b_defconfig ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-
Note that this changes to "make 52xx/lite5200b_defconfig ..." in recent kernels.
> 2 - make cuImage.lite5200b ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-
Well, this is debatable. Here you explicitely request a backward
compatability wrapped uImage (for firmwares being FDT ignorant):
> The output of second command is:
> ...
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CALL scripts/checksyscalls.sh
> CHK include/linux/compile.h
> CALL arch/powerpc/kernel/systbl_chk.sh
> CALL arch/powerpc/kernel/prom_init_check.sh
> arch/powerpc/boot/dtc -O dtb -o arch/powerpc/boot/lite5200b.dtb -b 0 /home/
> asimmini/Scrivania/linux-2.6.26.3/arch/powerpc/boot/dts/lite5200b.dts
> DTC: dts->dtb on file "/home/asimmini/Scrivania/linux-2.6.26.3/arch/powerpc/
> boot/dts/lite5200b.dts"
> WRAP arch/powerpc/boot/cuImage.lite5200b
^---- Here the wrapper gets added.
> Image Name: Linux-2.6.26.3
> Created: Wed Sep 3 15:56:16 2008
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size: 1597696 Bytes = 1560.25 kB = 1.52 MB
> Load Address: 0x00400000
> Entry Point: 0x00400550
> rm arch/powerpc/boot/lite5200b.dtb
>
> But, at this point, if i crosscompile in ppc mode i had to modify the Load
> Address wiht the mkimage tool because the SDRAM at the Bootloader time starts
> from 0xF8000000, while the uImage has a Load Address and Entry Point at
> 0x00000000.
Well still in newer kernels, uImage has load and entry address 0. Its
only the cuImage.lite5200b (and I presume other wrapped kernels) that
have this load address.
> What should i do in powerpc mode??
I suggest that you use a recent U-Boot on your board which can
explicitely pass a .dtb to the kernel and use a plain uImage + flat
device tree blob. I gather this is the best tested combination. I
myself saw problems with the wrapped image that went away when passing
the device tree explicitely.
So in 2.6.26 I'd advise you to do a "make uImage" + "make lite5200b.dtb"
and use the results in a recent U-Boot.
Cheers
Detlev
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de
next prev parent reply other threads:[~2008-09-04 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 14:10 Boot 2.6.26 (or similar) on mpc5200 using powerpc Angelo
2008-09-04 12:05 ` Detlev Zundel [this message]
2008-09-04 13:08 ` Angelo
2008-09-04 13:28 ` powerpc405 versus powerpc440 Wood, Robert (GE EntSol, Intelligent Platforms)
2008-09-04 15:07 ` Josh Boyer
2008-09-17 9:25 ` Grant Likely
2008-09-04 14:47 ` Boot 2.6.26 (or similar) on mpc5200 using powerpc Detlev Zundel
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=m28wu8f753.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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 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.