this is problematic.
you cannot add a new element before the pending firing because you can't
tell how far into the present trigger you are.
This is not a problem for readable counters like the i8254. The problem
for the i8254 is that reading and writing it takes a long time (perhaps
5 usec
On Wed, 7 Jul 1999 19:46:38 -0700 (PDT),
Julian Elischer jul...@whistle.com said:
julian With your scheme the clock needs to be always running at elevated
speed.
julian Possibly you might have a startup routine that turns on the elevated
julian frequency, (basically does an 'aquire_timer0()'
On Thu, 8 Jul 1999, Seigo Tanimura wrote:
On Wed, 7 Jul 1999 19:46:38 -0700 (PDT),
Julian Elischer jul...@whistle.com said:
julian With your scheme the clock needs to be always running at elevated
speed.
julian Possibly you might have a startup routine that turns on the elevated
this is problematic.
you cannot add a new element before the pending firing because you can't
tell how far into the present trigger you are.
On Thu, 8 Jul 1999, Doug Rabson wrote:
On Thu, 8 Jul 1999, Seigo Tanimura wrote:
On Wed, 7 Jul 1999 19:46:38 -0700 (PDT),
Julian Elischer
From: Julian Elischer jul...@whistle.com
Subject: Re: Rewriting pca(4) using finetimer(9) (was: Re: MPU401 now works
under New Midi Driver Framework with a Fine Timer)
Date: Thu, 8 Jul 1999 11:23:42 -0700 (PDT)
Message-ID: pine.bsf.3.95.990708112244.25198c-100...@current1.whistle.com
julian
Another idea has come to my mind...
pca(4) currently uses acquire_timer0(), which changes the timer
frequency directly, breaking finetimer(9). I am considering to
move acquire_timer0()s in pca(4) to finetimer(9), so that pca(4)
comes to work again. Furthermore, we can get rid of acquire_timer0()
uh...
[phaser.whistle.com] 536 man 9 finetimer
No entry for finetimer in section 9 of the manual
On Thu, 8 Jul 1999, Seigo Tanimura wrote:
Another idea has come to my mind...
pca(4) currently uses acquire_timer0(), which changes the timer
frequency directly, breaking finetimer(9). I
On Wed, 7 Jul 1999 19:06:48 -0700 (PDT),
Julian Elischer jul...@whistle.com said:
julian uh...
julian [phaser.whistle.com] 536 man 9 finetimer
julian No entry for finetimer in section 9 of the manual
Sorry, finetimer(9) is the new timer implemented in my latest midi driver.
You can read the
On Thu, 8 Jul 1999, Seigo Tanimura wrote:
On Wed, 7 Jul 1999 19:06:48 -0700 (PDT),
Julian Elischer jul...@whistle.com said:
julian uh...
julian [phaser.whistle.com] 536 man 9 finetimer
julian No entry for finetimer in section 9 of the manual
Sorry, finetimer(9) is the new timer
On Wed, 7 Jul 1999 19:18:57 -0700 (PDT),
Julian Elischer jul...@whistle.com said:
Sorry, finetimer(9) is the new timer implemented in my latest midi driver.
You can read the short paper describing the feature and principle in:
Message-Id: 199907060959.saa05...@rina.naklab.dnj.ynu.ac.jp
On Thu, 8 Jul 1999, Seigo Tanimura wrote:
Ow, I thought it was in the mailing list archive, turned out not.
I will attach the paper below. Sorry for a long mail.
--- v --- cut here --- v ---
Unlike 16550, MPU401 does not generate an interrupt on TX-ready.
So we have to choose one of
11 matches
Mail list logo
