From: Vojtech Pavlik <vojtech@suse.cz>
To: dtor_core@ameritech.net
Cc: bjd <bjdouma@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 001/001] INPUT: new ioctl's to retrieve values of EV_REP and EV_SND event codes
Date: Tue, 25 Apr 2006 17:16:28 +0200 [thread overview]
Message-ID: <20060425151628.GA11078@suse.cz> (raw)
In-Reply-To: <d120d5000604250619r6170c18bh8d26fc041141c056@mail.gmail.com>
On Tue, Apr 25, 2006 at 09:19:42AM -0400, Dmitry Torokhov wrote:
> On 4/24/06, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > On 4/24/06, Vojtech Pavlik <vojtech@suse.cz> 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
next prev parent reply other threads:[~2006-04-25 15:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 20:48 [PATCH 001/001] INPUT: new ioctl's to retrieve values of EV_REP and EV_SND event codes bjd
2006-04-24 14:31 ` Dmitry Torokhov
2006-04-24 14:57 ` Vojtech Pavlik
2006-04-24 15:03 ` Dmitry Torokhov
2006-04-25 13:19 ` Dmitry Torokhov
2006-04-25 15:16 ` Vojtech Pavlik [this message]
2006-04-25 15:23 ` Dmitry Torokhov
2006-04-25 15:26 ` Vojtech Pavlik
2006-04-26 5:06 ` Dmitry Torokhov
2006-04-26 9:38 ` Vojtech Pavlik
2006-04-26 10:43 ` bjdouma
2006-04-26 14:24 ` Dmitry Torokhov
2006-04-26 19:09 ` bjdouma
2006-04-28 17:03 ` Dmitry Torokhov
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=20060425151628.GA11078@suse.cz \
--to=vojtech@suse.cz \
--cc=bjdouma@xs4all.nl \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
/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