Re: Timing Under MiNT

[mk@anuurn.ruhr.de (Martin Koehling)]

In <199601291425.OAA21427@burn6.ncl.ac.uk>,
Craig.Graham@newcastle (Craig.Graham@newcastle.ac.uk) wrote:

>In case anyone missed it ;) I'm working on the XaAES AES replacement for
>MiNT. I've got a problem, and thought someone might be able to help.
>
>At the moment I use Talarm() to set timer callbacks in order to implement
>evnt_timer() and evnt_multi(MU_TIMER). This works fine (there's a delta queue
>backing up the signal handler to allow multiple events), but the problem
>is the Talarm() only has a resolution of 1 second, which is to long for
>several apps (notably Yukon calls evnt_timer() in between dealing each card
>- with a minimum 1sec delay, dealling a full deck takes ages).
>
>I think I should implement my own clock device (write a time in milliseconds,
>select on it and it will write back after n millisecond) - can anyone give me
>a few pointers on devices (I don't really have time to work it out myself, as
>there is still a fair bit of XaAES to finish).

Why don't you simply use the timeout feature of Fselect(), which *has*
a (theoretical) resolution of one milisecond?
Or am I completely missing the point? 8-)

Martin

-- 
 Martin Koehling // NEW email address: mk@anuurn.ruhr.de