From: Dan Malek <dan@mvista.com>
To: Brian Ford <ford@vss.fsi.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 66 Mhz bus clock for EST8260?
Date: Fri, 08 Dec 2000 14:03:06 -0500 [thread overview]
Message-ID: <3A31306A.8E8A900A@mvista.com> (raw)
In-Reply-To: Pine.GSO.4.21.0012081225350.24199-100000@eos
Brian Ford wrote:
> .... I have made a few corrections to the
> bootrom so the decrementer frequency is set correctly from the user
> dip switches in addition to setting the core, cpm, and bus speeds.
You are going to have to reprogram the memory controller timing.......
> Has anyone had any luck with the 66 Mhz bus clock?
Yes, on boards with processor/memory interface properly initialized
to run at that speed.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-08 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 18:47 66 Mhz bus clock for EST8260? Brian Ford
2000-12-08 19:03 ` Dan Malek [this message]
2000-12-08 21:55 ` Jerry Van Baren
2000-12-08 20:09 ` Jerry Van Baren
[not found] <7283DE19D141D111AD0E00A0C95B195502581E41@mail2.aiinet.com>
2000-12-11 15:32 ` Brian Ford
2000-12-11 16:47 ` Stephen B. Johnson
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=3A31306A.8E8A900A@mvista.com \
--to=dan@mvista.com \
--cc=ford@vss.fsi.com \
--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).