From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932260AbWDYP0E (ORCPT ); Tue, 25 Apr 2006 11:26:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932264AbWDYP0E (ORCPT ); Tue, 25 Apr 2006 11:26:04 -0400 Received: from styx.suse.cz ([82.119.242.94]:9452 "EHLO mail.suse.cz") by vger.kernel.org with ESMTP id S932260AbWDYP0D (ORCPT ); Tue, 25 Apr 2006 11:26:03 -0400 Date: Tue, 25 Apr 2006 17:26:00 +0200 From: Vojtech Pavlik To: dtor_core@ameritech.net Cc: bjd , 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 Message-ID: <20060425152600.GA30398@suse.cz> References: <20060422204844.GA16968@skyscraper.unix9.prv> <20060424145747.GA5906@suse.cz> <20060425151628.GA11078@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Bounce-Cookie: It's a lemon tree, dear Watson! User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 25, 2006 at 11:23:02AM -0400, Dmitry Torokhov wrote: > On 4/25/06, Vojtech Pavlik wrote: > > On Tue, Apr 25, 2006 at 09:19:42AM -0400, Dmitry Torokhov wrote: > > > On 4/24/06, Dmitry Torokhov wrote: > > > > On 4/24/06, Vojtech Pavlik 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. > > > > So do you agree that we need to ressurect EVIOCGREP (and EVIOCSREP > just to complement the interface)? Yes. And EVIOCSREP should just generate the events needed to notify the drivers to do the change. -- Vojtech Pavlik Director SuSE Labs