From: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>
To: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: 8260 System clock
Date: Fri, 28 Mar 2003 16:36:05 +0100 [thread overview]
Message-ID: <00e201c2f53f$befd20c0$0700a8c0@pc005> (raw)
Hi to All.
We are currently working with a custom board which uses an 8260 with 33MHz
external oscillator. We have applied the clocks programming that is almost
the slower we could, and correspond to 133/100/33 MHz. In this conditions
Linux and related applications run well.
We have tried to increment the CPU clock by changing the MODCLK1÷MODCLK3
configuration pins and in both 166/100/33 and 200/100/33 the system hangs
after the hash table programming.
The CPU is an HIP3 - B.3 (6K23 mask) revision and is marked with 200/166/66.
Does anybody has an idea about such behaviour ?
many thanks
Gianfranco
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-03-28 15:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='00e201c2f53f$befd20c0$0700a8c0@pc005' \
--to=gianfranco.morandi@euro-studio.it \
--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).