Neil Horman wrote:
On Wed, Jul 26, 2006 at 01:29:25AM +0200, Segher Boessenkool wrote:
Yes, but if its in trade for something thats being used currently
which hurts
more (case in point being the X server), using this solution is a
net gain.
...in the short term.
And for any arch that isn't able to leverage a speedup via a vdso implementation
of a simmilar functionality in the long term
If they can't, then they can't use your driver either.
I'm not arguing with you that adding a low res gettimeofday
vsyscall is a better
long term solution, but doing that requires potentially several
implementations
in the C library accross a range of architectures, some of which
may not be able
to provide a time solution any better than what the gettimeofday
syscall
provides today. The /dev/rtc solution is easy, available right
now, and applies
to all arches.
"All"?
It there any arch for which the rtc driver doesn't function?
Yes, there are plenty of systems which don't have an RTC, or have an RTC
which can't generate interrupts.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
