On Sun, Feb 20, 2000 at 06:21:57PM +0100, Ralf Baechle wrote:
> > hwclock tries to use /dev/rtc to read and set the hardware clock.
> >
> > [Of course the idea is that if the kernel provides this access
> > then a userspace program need not try to access the hardware itself.
> > Today there are still machines where "hwclock --directisa" works
> > but "hwclock" fails, so the kernel code for rtc is not perfect yet.]
>
> I'd actually like to see --directisa support to be removed from hwclock or
> at least to be a #ifdef __i386__. The last time I had to hack hwclock for
> the n+1th MIPS port it was much more portable than it's predecessor clock
> but the direct port accesses still make it somewhat messy.
>
> What is the problem with /dev/rtc on those machines where hwclock fails?
It fails :-)
The symptoms vary. Sometimes it just doesnt work.
Sometimes it causes a kernel hang.
On all machines I have access to hwclock works.
But there are sufficiently many reports of "hwclock" failing
and "hwclock --directisa" succeeding (especially on more
obscure alpha versions, but not only on alpha) to leave
the directisa option for the moment.
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:25 EST