From: Brendan J Simon <brendan.simon@bigpond.com>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Cc: Dan Malek <dmalek@jlc.net>
Subject: linuxppc-embedded: mpc8260 bus frequency calculations
Date: Fri, 02 Mar 2001 12:40:54 +1100 [thread overview]
Message-ID: <3A9EFA26.8030805@bigpond.com> (raw)
I've come accross a problem where our custom embedded 8260 board is
losing time. I've tracked it down to the bi_busfreq value being set to
66 instead of the true value of
66.6666666666666666666666666666666666666. One solution is to have the
board_info fields in units of Hz instead of MHz. I could then set the
bi_busfreq value to 66666667 for much better accuracy.
Another solution might be to regularly read the real time clock. Does
linux do this normally or does it just read the RTC once at boot up and
then just rely on it's internal timers for the system time. I can't see
how this can be very accurate.
Thanks,
Brendan Simon.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-03-02 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 1:40 Brendan J Simon [this message]
2001-03-02 4:20 ` linuxppc-embedded: mpc8260 bus frequency calculations Neil Russell
2001-03-02 4:32 ` Brendan J Simon
2001-03-02 5:27 ` Murray Jensen
2001-03-02 14:50 ` Daris A Nevil
2001-03-02 7:26 ` Dan Malek
2001-03-02 14:20 ` Magnus Damm
2001-03-08 6:06 ` Dan Malek
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=3A9EFA26.8030805@bigpond.com \
--to=brendan.simon@bigpond.com \
--cc=dmalek@jlc.net \
--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).