public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Arnd Bergmann <abergman@de.ibm.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH] hpet header sanitization
Date: Wed, 22 Mar 2006 12:14:46 +0100	[thread overview]
Message-ID: <20060322111446.GA7675@turing.informatik.uni-halle.de> (raw)
In-Reply-To: <200603221118.43853.abergman@de.ibm.com>

Arnd Bergmann wrote:
> On Tuesday 21 March 2006 23:46, Randy.Dunlap wrote:
> > +#define        HPET_IE_ON      _IO('h', 0x01)  /* interrupt on */
> > +#define        HPET_IE_OFF     _IO('h', 0x02)  /* interrupt off */
> > +#define        HPET_INFO       _IOR('h', 0x03, struct hpet_info)
> > +#define        HPET_EPI        _IO('h', 0x04)  /* enable periodic */
> > +#define        HPET_DPI        _IO('h', 0x05)  /* disable periodic */
> > +#define        HPET_IRQFREQ    _IOW('h', 0x6, unsigned long)   /* IRQFREQ usec */
> 
> By the way, HPET_INFO and HPET_IRQFREQ don't work for 32 bit user space,
> the driver needs a compat_ioctl() method to handle those.

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.


Clemens

  reply	other threads:[~2006-03-22 11:15 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 [this message]
2006-03-22 17:01     ` Randy.Dunlap
2006-03-23 10:18       ` Clemens Ladisch
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=20060322111446.GA7675@turing.informatik.uni-halle.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