From: Clemens Ladisch <clemens@ladisch.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: abergman@de.ibm.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] hpet header sanitization
Date: Thu, 23 Mar 2006 11:18:32 +0100 [thread overview]
Message-ID: <1143109112.442275f83c95e@www.domainfactory-webmail.de> (raw)
In-Reply-To: <20060322090125.8fc13711.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> On Wed, 22 Mar 2006 12:14:46 +0100 Clemens Ladisch wrote:
> > There isn't any program (except the example in the docs) that
> > uses any of these ioctls, and I'm writing patches to make this
> > device available through portable timer APIs like hrtimer/POSIX
> > clocks/ALSA that are much easier to use besides, so I think it
> > would be a good idea to just schedule these ioctls for removal.
>
> How do you (or can you) know that there are no programs that use
> that ioctl?
Because most parts of hpet.c were orignially written on an emulator
and were so buggy as to be effectively unusable until recently.
Additionally, there aren't many BIOSes out there that manage to
initialize the third HPET timer (the one used by these ioctls)
correctly, or that bother to enable the HPET device at all. (This
seems to be changing due to the Windows Vista logo requirements.)
Regards,
Clemens
next prev parent reply other threads:[~2006-03-23 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 22:46 [PATCH] hpet header sanitization Randy.Dunlap
2006-03-22 0:13 ` Andrew Morton
2006-03-22 0:26 ` Randy.Dunlap
2006-03-22 9:02 ` Arjan van de Ven
2006-03-22 17:26 ` Randy.Dunlap
2006-03-22 20:08 ` Arjan van de Ven
2006-03-22 20:55 ` Randy.Dunlap
2006-03-22 10:18 ` Arnd Bergmann
2006-03-22 11:14 ` Clemens Ladisch
2006-03-22 17:01 ` Randy.Dunlap
2006-03-23 10:18 ` Clemens Ladisch [this message]
2006-03-22 22:45 ` Arnd Bergmann
2006-03-23 8:13 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1143109112.442275f83c95e@www.domainfactory-webmail.de \
--to=clemens@ladisch.de \
--cc=abergman@de.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox