From: Domen Puncer <domen.puncer@telargo.com>
To: Pradyumna Sampath <pradyumna.sampath@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: arch/powerpc for lite5200b
Date: Wed, 25 Apr 2007 07:29:59 +0200 [thread overview]
Message-ID: <20070425052959.GX18236@moe.telargo.com> (raw)
In-Reply-To: <f87351060704240431m2218910cs65510472218459b0@mail.gmail.com>
On 24/04/07 17:01 +0530, Pradyumna Sampath wrote:
> Hi Everyone,
>
> I have been trying to get the linux-2.6.20-rt3 for arch/powerpc to
> boot on my lite5200b. Here are the things that I have tried so far. I
> have a custom board based on the lite5200b and then the evaluation
> board too.
>
> - I have a working 2.6.16-rt29 kernel compiled using ARCH=ppc for both
> these boards.
>
> - I tried the default configs for lite5200 for both the custom board
> and the EVB. Both hang at "Transferring control to Linux (at address
> 00000000) ..."
Device tree missing?
You need to compile it with dtc, then in u-boot use something like:
bootp; tftp 0x400000 uImage.ppc; tftp 0x600000 lite5200b.dtb
set your bootargs
bootm 0x400000 - 0x600000
>
> - I downloaded roberts
> http://www.pengutronix.de/oselas/bsp/phytec/index_en.html#phyCORE-MPC5200B-tiny
> patches, but still ended up with the same result.
>
> I read ( http://www.nabble.com/Re%3A-MPC52xx-support-rework-for-2.6.20-p7568655.html
> ) that the arch/powerpc port for lite5200 works right out of the box.
> Am I doing something wrong ?
>
> The one thing I am yet to try is to do a git checkout from
> git.secretlabs.ca. Unfortunately thanks to some internal firewalling
> policies I still have not been able to do that.
kernel.org tree will also work with lite5200b, if you need ethernet
download fec/bestcomm patches from Grant's tree.
Domen
prev parent reply other threads:[~2007-04-25 5:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 11:31 arch/powerpc for lite5200b Pradyumna Sampath
2007-04-25 5:29 ` Domen Puncer [this message]
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=20070425052959.GX18236@moe.telargo.com \
--to=domen.puncer@telargo.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=pradyumna.sampath@gmail.com \
/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).