From: Stefan Roese <sr@denx.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: u-boot ppc440epx bootstrap configuration without eval board
Date: Wed, 2 Apr 2008 21:00:33 +0200 [thread overview]
Message-ID: <200804022100.33364.sr@denx.de> (raw)
In-Reply-To: <000901c894eb$e0707170$2001a8c0@DCOGLEYNEW>
On Wednesday 02 April 2008, Dave Cogley wrote:
> Disregard the boot strapping problem. It appears we are hardwired strapped
> to use option "C" however my CPU is not being recognized as a 667MHz.
> Which option should I be using for the 667MHz processor?
First, this is the wrong mailing list for this discussion. Please post to the
U-Boot list instead.
But here some general comments:
The bootstrap controller has multiple configuration options. Some of them
result in hardwired frequencies (CPU, PLB, OPB...), and some of them load the
PLL setup from an I2C EEPROM. Using this bootstrap EEPROM is the most
flexible solution. If you have only option "C", then you hardwired to 533MHz.
There is no way to "detect" which frequency this CPU is labeled.
But it *is* possible to reconfigure the PLL from within U-Boot an reset the
PPC to run with this different PLL setup. I just recently added some code the
u-boot-ppc4xx custodian repository.
Let's continue this thread on the U-Boot list.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de
=====================================================================
next prev parent reply other threads:[~2008-04-02 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 18:03 u-boot ppc440epx bootstrap configuration without eval board Dave Cogley
2008-04-02 19:00 ` Stefan Roese [this message]
2008-04-02 21:16 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2008-04-02 17:14 Dave Cogley
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=200804022100.33364.sr@denx.de \
--to=sr@denx.de \
--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).