From: "AlessandroPPC" <aleppcrossi@libero.it>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: cpu speed
Date: Fri, 28 Feb 2003 10:05:39 +0100 [thread overview]
Message-ID: <004801c2df08$90e5b1e0$0400a8c0@pc002> (raw)
Dear all,
I 've a MPC8260 board with 2.4.18 kernel version and nfs root fs . First I
have configurated it with cpu_clock = 133 MHz, cpm_clock = 100 MHz and
bus_clock = 33 Mhz with good results.
Then I have changed this configuration with cpu_clock = 166 MHz, cpm_clock =
100 MHz and bus_clock = 33 Mhz with bad results.
With cpu clock at 166 Mhz I have several error but typically "Illegal
istruction " error message is send on the console.
I have checked the bus timing (memory read/write access) with no difference
rispect to cpu_clock at 133 MHz.
Can be a cache problem ?
Tanks to all,
Alessandro.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-02-28 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 9:05 AlessandroPPC [this message]
2003-02-28 12:29 ` Information about Library Optimizer Kamaraj P
2003-02-28 18:03 ` Marius Groeger
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='004801c2df08$90e5b1e0$0400a8c0@pc002' \
--to=aleppcrossi@libero.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).