From: "Guy G. Sotomayor, Jr." <ggs@shiresoft.com>
To: Dan Malek <dmalek@jlc.net>
Cc: Cort Dougan <cort@persephone.cs.nmt.edu>,
Troy Benjegerdes <hozer@drgw.net>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: PReP RTC vs Decrementer accuracy...
Date: Wed, 09 Dec 1998 21:57:32 -0800 [thread overview]
Message-ID: <366F62CC.1C4B225E@shiresoft.com> (raw)
In-Reply-To: 366EDF74.6EE17E0D@jlc.net
Dan Malek wrote:
>
> Cort Dougan wrote:
>
> > Take a look at the decrementer code - I think it's possible to miss a decr
> > when resetting it. That could explain drift.
>
> I finally had a look (after I saw my original message _finally_
> got sent to the list :-).
>
> We are either going to get it right, or miss a bunch. If the
> instructions fit in a cache line, I think we are OK because
> nothing should affect the stream between the get_dec()
> and set_dec(). If we have to do a cache line fill between
> these, I think we are hosed........
>
> This is why I used the PIT in my original port of the 8xx
> stuff. Since the hardware did the reload, there was no
> timer drift that could be the result of the software (unless
> you missed one of the imterrupts, which better not
> happen :-). I went back to the decrementer for the 8xx
> because it presented an integration hassle....I may
> now reconsider.....
>
Umm, but why are you keeping track of time with the decrementer? Why
don't you use the timebase to keep track of time and the decrementer
to deliver periodic interrupts? The two do not necessarily need to be
linked and solve the drift problem.
TTFN - Guy
[[ 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-10 5:57 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. [this message]
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
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=366F62CC.1C4B225E@shiresoft.com \
--to=ggs@shiresoft.com \
--cc=cort@persephone.cs.nmt.edu \
--cc=dmalek@jlc.net \
--cc=hozer@drgw.net \
--cc=linuxppc-dev@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).