From: Dan Malek <dmalek@jlc.net>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PReP RTC vs Decrementer accuracy...
Date: Mon, 14 Dec 1998 01:45:30 -0500 [thread overview]
Message-ID: <3674B40A.8B152375@jlc.net> (raw)
In-Reply-To: Pine.HPP.3.96.981213172728.17076D-100000@gra-ux1.iram.es
Gabriel Paubert wrote:
> Yes, the problem is the good old 601. The TB uses different register
> numbers (it's called the RTC, split into RTCU and RTCL like TBU and TBL).
I'll take a look at this. I don't think it is a problem. I only use the
lower part to count 10 millisecond timer interrupts, and as long
as I know where it wraps around, it should be fine. As long as
there are timebase compare registers that interrupt when a match
occurs on either upper or lower, we are all set. Different register
numbers are OK because all get/set operations are implementation
defined functions.
-- Dan
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1998-12-14 6:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-07 12:31 USB, PCI and registers Benjamin Herrenschmidt
1998-12-07 21:02 ` PReP RTC vs Decrementer accuracy Troy Benjegerdes
1998-12-08 5:00 ` Cort Dougan
1998-12-08 20:32 ` Dan Malek
1998-12-08 23:52 ` Cort Dougan
1998-12-09 7:30 ` Troy Benjegerdes
1998-12-09 8:25 ` Cort Dougan
1998-12-09 23:52 ` Corey Minyard
1998-12-10 4:20 ` Corey Minyard
1998-12-10 5:48 ` Cort Dougan
1998-12-10 10:58 ` Geert Uytterhoeven
1998-12-10 16:00 ` Corey Minyard
1998-12-09 20:37 ` Dan Malek
1998-12-10 5:57 ` Guy G. Sotomayor, Jr.
1998-12-10 17:53 ` Dan Malek
1998-12-10 19:26 ` Guy G. Sotomayor, Jr.
1998-12-11 5:53 ` Dan Malek
1998-12-13 17:05 ` Gabriel Paubert
1998-12-14 6:45 ` Dan Malek [this message]
1998-12-15 20:12 ` 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=3674B40A.8B152375@jlc.net \
--to=dmalek@jlc.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.