Messages in this thread | | | Date | Sun, 30 May 2010 19:58:38 -0700 | From | Randy Dunlap <> | Subject | Re: Documentation/timers/hpet_example.c compile bug |
| |
On 05/30/10 19:49, Arjan van de Ven wrote: > On Sun, 30 May 2010 19:34:35 -0700 > Randy Dunlap <randy.dunlap@oracle.com> wrote: >> >> Does it even make sense to build hpet_example on s390? >> I.e., does s390 have hpet? >> If not, then a simple Kconfig "depends on X86" or "depends on !S390" >> will fix this. > > HPET is very PC specific. > > but.. even on x86, it does not really make sense, and exposing this as > an interface to userspace is a historical mistake, the use of which we > really ought to discourage.
Do you mean exposing anything that is in /usr/include/linux/hpet.h via ioctls? especially struct hpet_info ?
-- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***
| |