From: Dan Malek <dan@netx4.com>
To: Grant Carter <gcarter@eng.uct.ac.za>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel woes for versions > 2.2.5
Date: Fri, 10 Dec 1999 15:03:39 -0500 [thread overview]
Message-ID: <38515C9B.359D913@netx4.com> (raw)
In-Reply-To: 3850F28A.D36731A3@eng.uct.ac.za
Grant Carter wrote:
> processor just hangs with no output on the console.
Take a look at arch/ppc/mbxboot/embed_config.c. At the end
of this is the function for initializing the board information
structure. Make sure you use the same information from the
kernel that is booting correctly, in particular assigning the
proper processor speed. I have discussed this with Stuart of
BrightStar Engineering, and I haven't yet included a processor
speed variable in the environment variables. The default
configuration is not correct for this processor, so you have
to assign the proper values here. I am likely to have missed
this when making the last kernel update.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-12-10 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-10 12:31 Kernel woes for versions > 2.2.5 Grant Carter
1999-12-10 20:03 ` Dan Malek [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=38515C9B.359D913@netx4.com \
--to=dan@netx4.com \
--cc=gcarter@eng.uct.ac.za \
--cc=linuxppc-embedded@lists.linuxppc.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).