From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Chris Dumoulin" <cdumoulin@ics-ltd.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Moving from 2.4 to 2.6 kernel
Date: Thu, 4 May 2006 12:11:33 -0600 [thread overview]
Message-ID: <528646bc0605041111o1b652d60w3f5847a19abe5c95@mail.gmail.com> (raw)
In-Reply-To: <445A3AB1.7040405@ics-ltd.com>
On 5/4/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> I am trying to take a working embedded linux system from kernel 2.4 to
> 2.6. The hardware is a custom board using a Virtex II Pro with PPC405
> processor.
> The working system uses u-boot 1.1.1 with linux kernel 2.4.18.
>
> I am using the same u-boot and I am trying to port linux kernel 2.6.15
> to our platform. Using the stuff from the working 2.4 kernel port and
> other PPC4xx platforms in the 2.6.15 code as examples, I believe I have
> done everything required to get the kernel booting. However, the kernel
> seems to hang after being uncompressed. Here is what I see after running
> bootm from u-boot:
The V2pro is already supported in the 2.6 kernel. Are you using that
code; or starting from scratch? V2Pro (ML300) and V4FX (ML403) are
both supported in the latest 2.6 kernel.
I had similar problems when I was porting to the V4FX. Do you have a
JTAG debugger (Like a BDI-2000)? I think your best bet is to get in
there with a debugger to find out where it goes off into Lala land.
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 399-0195
next prev parent reply other threads:[~2006-05-04 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 17:32 Moving from 2.4 to 2.6 kernel Chris Dumoulin
2006-05-04 18:11 ` Grant Likely [this message]
2006-05-04 19:04 ` Andy Gospodarek
2006-05-04 19:17 ` Chris Dumoulin
2006-05-04 20:04 ` Grant Likely
2006-05-05 13:39 ` Chris Dumoulin
2006-05-05 15:31 ` Grant Likely
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=528646bc0605041111o1b652d60w3f5847a19abe5c95@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=cdumoulin@ics-ltd.com \
--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).