From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753905Ab1AZR72 (ORCPT ); Wed, 26 Jan 2011 12:59:28 -0500 Received: from mail-px0-f174.google.com ([209.85.212.174]:35213 "EHLO mail-px0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753794Ab1AZR7Z (ORCPT ); Wed, 26 Jan 2011 12:59:25 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=BFSo6j/9q4TfC2iVUSRQKsUajDkQgJjAe/TkQqPwqKiCRDFN/wGUai1aFIL/nVJbh5 WNEnBbLlvHQeM/wWbZjGZhHVJPQiBjSBLDnovIyqhaLdOc97jSZK5li1KHwL5/OHBsKi YTjgrii1vdky2SpVcUzkf+zOlWiI1biskBfRA= Date: Wed, 26 Jan 2011 09:59:18 -0800 From: Dmitry Torokhov To: Mauro Carvalho Chehab Cc: Mark Lord , Linux Kernel , linux-input@vger.kernel.org, linux-media@vger.kernel.org, Gerd Hoffmann Subject: Re: 2.6.36/2.6.37: broken compatibility with userspace input-utils ? Message-ID: <20110126175918.GA29268@core.coreip.homeip.net> References: <20110125164803.GA19701@core.coreip.homeip.net> <20110125205453.GA19896@core.coreip.homeip.net> <4D3F4804.6070508@redhat.com> <4D3F4D11.9040302@teksavvy.com> <20110125232914.GA20130@core.coreip.homeip.net> <20110126020003.GA23085@core.coreip.homeip.net> <4D4004F9.6090200@redhat.com> <4D403693.50702@teksavvy.com> <4D405CAD.5040107@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D405CAD.5040107@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 26, 2011 at 03:41:01PM -0200, Mauro Carvalho Chehab wrote: > Em 26-01-2011 12:58, Mark Lord escreveu: > > On 11-01-26 06:26 AM, Mauro Carvalho Chehab wrote: > > .. > >> However, as said previously in this thread, input-kbd won't work with any > >> RC table that uses NEC extended (and there are several devices on the > >> current Kernels with those tables), since it only reads up to 16 bits. > >> > >> ir-keytable works with all RC tables, if you use a kernel equal or upper to > >> 2.6.36, due to the usage of the new ioctl's. > > > > Is there a way to control the key repeat rate for a device > > controlled by ir-kbd-i2c ? > > > > It appears to be limited to a max of between 4 and 5 repeats/sec somewhere, > > and I'd like to fix that. > > It depends on what device do you have. Several I2C chips have the repeat > logic inside the I2C microcontroller PROM firmware. or at the remote > controller itself. So, there's nothing we can do to change it. > > I have even one device here (I think it is a saa7134-based Kworld device) > that doesn't send any repeat event at all for most keys (I think it only > sends repeat events for volume - Can't remember the specific details anymore - > too many devices!). > > The devices that produce repeat events can be adjusted via the normal > input layer tools like kbdrate. > Unfortunately kbdrate affects all connected devices and I am not sure if there is a utility allowing to set rate on individual devices. But here is the main part: static int input_set_rate(int fd, unsigned int delay, unsigned int period) { unsigned int rep[2] = { delay, period }; if (ioctl(fd, EVIOCSREP, rep) < 0) { perror("evdev ioctl"); return -1; } return 0; } -- Dmitry