From: Robin Gilks <robin.gilks@tait•co.nz>
To: linuxppc mail list <linuxppc-embedded@lists•linuxppc.org>
Subject: Clock rate on MPC8xx CPUs
Date: Mon, 21 Jul 2003 14:10:41 +1200 [thread overview]
Message-ID: <3F1B4BA1.6000204@tait.co.nz> (raw)
Greetings
Can anyone shed some light on a question of clock rates?
We're playing with the mpc866ads board and currently running both the
CPU core and bus at 50MHz to keep things simple. As a result it seems
that the internal Linux time is 50% out despite passing the clock rate
from u-boot as being 50MHz.
Since the mpc866 can run its core at x2 the bus rate, does the timer
setup in Linux for this port assume that the CPU _will_ be running at x2
from the rate passed at boot time or is there something else
'interesting' with this new '866 CPU :-))
--
Robin Gilks
Senior Design Engineer Phone: (+64)(3) 357 1569
Tait Electronics Fax : (+64)(3) 359 4632
PO Box 1645 Christchurch Email : robin.gilks@tait•co.nz
New Zealand
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-07-21 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 2:10 Robin Gilks [this message]
2003-07-22 22:07 ` Clock rate on MPC8xx CPUs Robin Gilks
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=3F1B4BA1.6000204@tait.co.nz \
--to=robin.gilks@tait$(echo .)co.nz \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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