From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932214AbWDYNTp (ORCPT ); Tue, 25 Apr 2006 09:19:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932215AbWDYNTo (ORCPT ); Tue, 25 Apr 2006 09:19:44 -0400 Received: from nz-out-0102.google.com ([64.233.162.203]:61802 "EHLO nz-out-0102.google.com") by vger.kernel.org with ESMTP id S932214AbWDYNTo convert rfc822-to-8bit (ORCPT ); Tue, 25 Apr 2006 09:19:44 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KdTbob99eUTsfVnjJTpFzLB+luTIeQoyvAhQUo6acyzC4Gu07Uf7PTCgmbetM18jGBffjeyORONPuOT41IpepCkdjni8Ng61uorbjYixC9GbRrPAJn7GstgWncXLSaCNSjKnCmCzaYEXMBl9IwMWoW2lzeIjqiFm5nnGzSki+Tc= Message-ID: Date: Tue, 25 Apr 2006 09:19:42 -0400 From: "Dmitry Torokhov" Reply-To: dtor_core@ameritech.net To: "Vojtech Pavlik" Subject: Re: [PATCH 001/001] INPUT: new ioctl's to retrieve values of EV_REP and EV_SND event codes Cc: bjd , linux-kernel@vger.kernel.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Content-Disposition: inline References: <20060422204844.GA16968@skyscraper.unix9.prv> <20060424145747.GA5906@suse.cz> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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? -- Dmitry