Re: [PATCH 001/001] INPUT: new ioctl's to retrieve values of EV_REP and EV_SND event codes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 25, 2006 at 09:19:42AM -0400, Dmitry Torokhov wrote:
> On 4/24/06, Dmitry Torokhov <[email protected]> wrote:
> > On 4/24/06, Vojtech Pavlik <[email protected]> wrote:
> > > On Mon, Apr 24, 2006 at 10:31:39AM -0400, Dmitry Torokhov wrote:
> > > >
> > > > Vojtech, could you remind me why EVIOC{G|S}REP were removed? Some
> > > > people want to have ability to separate keyboards (via grabbing); they
> > > > also might want to control repeat rate independently. Shoudl we
> > > > reinstate these ioctls?
> > >
> > > I believe they were replaced by the ability to send EV_REP style events
> > > to the device, setting the repeat rate.
> > >
> >
> > Argh, why am I always forgetting about ability to write events into devices?
> 
> Thinking about it some more - writing to the event device is an
> elegant way to set repeat rate but how do you retrieve current repeat
> rate for a given device?
 
You can't. And that's likely a problem that needs fixing.

-- 
Vojtech Pavlik
Director SuSE Labs
-
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]
  Powered by Linux