On Wed, 18 Oct 2000, David Woodhouse wrote:
>
> [EMAIL PROTECTED] said:
> > I can't control somebody else's use of `hwclock` or even some future
> > kernel module.
>
> What you actually need to do is use the same spinlock as other users of the
> RTC hardware do.
>
> extern spinlock_t rtc_lock;
>
> It is exported to modules for this very reason.
>
There is no such exported variable in the 'stable' kernel tree:
Script started on Wed Oct 18 11:46:53 2000
# grep rtc_lock System.map
# grep rtc_lock `find . -name "*.c"`
# grep rtc_lock `find . -name "*.h"`
# pwd
/usr/src/linux-2.2.17
# exit
exit
Script done on Wed Oct 18 11:48:08 2000
Cheers,
Dick Johnson
Penguin : Linux version 2.2.17 on an i686 machine (801.18 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
