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: Fri, 5 May 2006 09:31:56 -0600 [thread overview]
Message-ID: <528646bc0605050831y75abe02dib2abe85ee88374d1@mail.gmail.com> (raw)
In-Reply-To: <445B5597.9010801@ics-ltd.com>
On 5/5/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> I generated the xparameters_ml300.h file and built my kernel configured
> for the ML300 board, but I still had the same problem. I'm wondering if
> there's something in the hardware that's not being setup by u-boot as
> the linux kernel expects it. I'm looking through the ML300 code in
> u-boot 1.1.4 to see if can spot anything that's being done in there
> that's not being done in my u-boot code. Do you have any ideas about
> some hardware (or other) initialization that I could be neglecting to
> do in u-boot that might cause things to hang?
Probably not; The nice thing about the V2Pro is that there is pretty
much no setup that needs to be done. The bitstream takes care of
configuring SDRAM. :). For my daily work; I don't even use u-boot.=20
I'm downloading a zImage directly through my BDI 2000. (But u-boot
does work for me too)
Can you post your xparameters file? (Or email it to me directly)
Are you using a full UART or UART lite?
> On a similar note, is there any guide to porting u-boot that I could
> read that would enumerate all the steps I should be taking in u-boot? I
> know the README in the u-boot source basically says to browse the
> mailing list (which I'm doing), read the DULG (which I've done), and
> read the source (which I'm also doing), but some kind of succinct guide
> would be nice, if it exists.
Not that I know of; I had to pile throught the same stuff to learn it.
> Interactive Circuits and Systems Ltd.
> 5430 Canotek Road
> Ottawa, ON
Hey; you going to OLS this year?
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 399-0195
prev parent reply other threads:[~2006-05-05 15:31 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
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 [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=528646bc0605050831y75abe02dib2abe85ee88374d1@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).