From: "John W. Linville" <linville@tuxdriver.com>
To: Jostein Pettersen <jostein.pettersen@westerngeco.com>
Cc: u-boot-users@lists.sourceforge.net,
Tormod Tjaberg <ttjaberg@oslo.westerngeco.slb.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: Linux hangs after early_init()
Date: Tue, 11 Jan 2005 16:07:52 -0500 [thread overview]
Message-ID: <20050111210750.GE10725@tuxdriver.com> (raw)
In-Reply-To: <5.1.0.14.2.20050111210842.024ca490@wgmail3.oslo.eur.slb.com>
On Tue, Jan 11, 2005 at 09:29:38PM +0100, Jostein Pettersen wrote:
> I'm trying to get Linux (2.4.19) up and running on a BMW board (from
> Broadcom) with a 8245 processor. I'm using ppcboot 1.2.0.
IMHO, the BMW support from Broadcom is wretchedly bad. At my former
employer, I implemented my own BMW support and ignored the Broadcom
code completely. This helped my disposition immensely.
PPCboot 1.2.0 (or any version called "PPCboot") is pretty old.
Did you get reasonably fresh code from Broadcom (if they have any)?
Or is this the same BMW support that has been in the base for years?
Broadcom released a number of variations on the BMW platform,
including multiple CPCI cards and multiple pizza-box variations.
It is extremely likely that your board doesn't match what is in
the ppcboot/u-boot source in some crucial detail, e.g. clock speed.
Some experimentation may be worthwhile.
I spent a couple of years as "the" Linux (and U-Boot) guy for a
company which used nearly every Broadcom board based on BMW (and
Mousse, fwiw). I may be able to help you. Contact me off list if
you'd like to arrange something.
Thanks,
John
P.S. linuxppc-embedded is not the right list to ask about
PPCboot/U-boot...try u-boot-users@lists.sourceforge.net instead...
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2005-01-11 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 20:29 Linux hangs after early_init() Jostein Pettersen
2005-01-11 21:07 ` John W. Linville [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=20050111210750.GE10725@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=jostein.pettersen@westerngeco.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ttjaberg@oslo.westerngeco.slb.com \
--cc=u-boot-users@lists.sourceforge.net \
/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).