From: Robin Gilks <robin.gilks@tait.co.nz>
To: linuxppc-embedded@ozlabs.org
Subject: 2.6.18 on mpc859t stuck in __delay
Date: Thu, 02 Nov 2006 13:25:43 +1300 [thread overview]
Message-ID: <45493B07.7030806@tait.co.nz> (raw)
I'm sure this is a common one but I'm a bit stuck (like the target is
really!!)
I'm real confused about what options to enable for a generic 866 series
target - I'm got CONFIG_MPC86xADS and CONFIG_FADS enabled in the
platform section but I'm not clear as to whether that will cause the
startup code to look for an ADS EPROM chip or look for a bd_t struct of
data from the bootloader.
I've checked the bdinfo at __res and it looks OK (booting from u-boot)
with valid CPU, bus and console speeds but I get the impression that the
decrementer isn't being started.
--
Robin Gilks
Senior Design Engineer Phone: (+64)(3) 357 1569
Tait Electronics Fax : (+64)(3) 359 4632
PO Box 1645 Christchurch Email : robin.gilks@tait.co.nz
New Zealand
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
next reply other threads:[~2006-11-02 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 0:25 Robin Gilks [this message]
2006-11-02 6:03 ` 2.6.18 on mpc859t stuck in __delay Kalle Pokki
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=45493B07.7030806@tait.co.nz \
--to=robin.gilks@tait.co.nz \
--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