RTC precision?

[Thaddeus P. Floryan]

In article <5578 at acorn.co.uk> agodwin at acorn.co.uk (Adrian Godwin) writes:
>[...]
>I need to perform something like the following code, under CTIX 5.1 on a 
>mini-20. This is part of ka9q's tcp/ip code, and wants its parent to be 
>woken up at frequent intervals. I think it's normally set to 200ms.
>
>My current hack for this polls times(), which is far from satisfactory.
>
>Is this OS sufficiently closely related to the 3b1's that the same ideas
>can be used ?

Programs running under CTIX on the Miniframe (and its kissing cousin, the
Motorola 6300 and 6350) run just fine on the 3B1 (at least everything I've
tried to date) as long as no shared libraries are being used ... this really
only affects executable binary transportability from the 3B1 to CTIX.

>I think one of the postings suggested using a device driver to produce
>some sort of timing mark. I don't have any of the appropriate documentation
>for writing a device driver under CTIX - again, is the 3b1 documentation
>Thad was distributing at all relevant to my system ?

Some of the code samples "should be" relevant, but I don't have sufficient
experience with device drivers to say "Yes" or "No".

>Here's the code distributed for systems like SVR3 :
.[...]
>	if (poll(&fds,1,timeout) == -1) {
            ^^^^
I don't see anything like "poll()" in the permuted index I have for the 3B1
as of 3.51

Sigh.  Short duration (under 1 sec) timing on the 3B1 is a royal pain; I've
been on-and-off over the past several months attempting to get a working
"ping(1)" program working on the 3B1 based on the 4.3BSD stuff at uunet.

Thad Floryan [ thad at btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]