From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@embeddededge.com>
Cc: Jean-Denis Boyer <jdboyer@mediatrix.com>,
"'Pavel Bartusek'" <pba@sysgo.de>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: MDIO clock speed computation
Date: Mon, 22 Jul 2002 22:15:29 +0200 [thread overview]
Message-ID: <20020722201534.F1B4910874@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 22 Jul 2002 15:51:15 EDT." <3D3C6233.3090007@embeddededge.com>
In message <3D3C6233.3090007@embeddededge.com> you wrote:
>
> system/bus clock speed. Up to this point, I don't believe there are
> any 8xx parts that are qualified to run beyond a 50 MHz CPU/bus
> speed, so the software is just fine. If you are running something
> faster than a 50 MHz bus, you may want to look into this.
There are. I've seen MPC823E, 860T, 860P and 862 qualified for 66 MHz
CPU/bus, and 862 for 100/50 MHz CPU/bus.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
They weren't that important. They were merely at the top. The people
who really run organizations are usually found several levels down,
where it's still possible to get things done.
- Terry Pratchett, _Small Gods_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-22 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 18:19 MDIO clock speed computation Jean-Denis Boyer
2002-07-22 19:51 ` Dan Malek
2002-07-22 20:12 ` Dan Malek
2002-07-22 20:15 ` Wolfgang Denk [this message]
2002-07-23 10:22 ` Pavel Bartusek
2002-07-23 15:01 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2002-07-23 19:41 Jean-Denis Boyer
2002-07-24 7:38 ` Pavel Bartusek
2002-07-23 15:47 Jean-Denis Boyer
2002-07-23 17:34 ` Dan Malek
2002-07-22 20:54 Jean-Denis Boyer
2002-07-22 17:19 Pavel Bartusek
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=20020722201534.F1B4910874@denx.denx.de \
--to=wd@denx.de \
--cc=dan@embeddededge.com \
--cc=jdboyer@mediatrix.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pba@sysgo.de \
/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).