From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure Date: Thu, 26 Nov 2009 13:39:09 -0800 Message-ID: <1F6BE32B-13EE-4FB4-96AD-D4526F435777@gmail.com> References: <200910200956.33391.jarod@redhat.com> <200910200958.50574.jarod@redhat.com> <4B0A765F.7010204@redhat.com> <4B0A81BF.4090203@redhat.com> <20091123173726.GE17813@core.coreip.homeip.net> <20091126052155.GD23244@core.coreip.homeip.net> Mime-Version: 1.0 (iPhone Mail 7C144) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-media-owner@vger.kernel.org To: Krzysztof Halasa Cc: Mauro Carvalho Chehab , Jarod Wilson , "linux-kernel@vger.kernel.org" , Mario Limonciello , "linux-input@vger.kernel.org" , "linux-media@vger.kernel.org" , Janne Grunau , Christoph Bartelmus List-Id: linux-input@vger.kernel.org On Nov 26, 2009, at 9:46 AM, Krzysztof Halasa wrote: > Dmitry Torokhov writes: > >> In what way the key interface is unsufficient for delivering button >> events? > > At present: 128 different keys only (RC5: one group). Where did this limitation come from? We have more than 256 keycodes already _defined_ in the input core and we can add more if needed. > One remote per > device only. Why would you want more? One physical device usually corresponds to a logical device. If you have 2 remotes create 2 devices. > The protocol itself doesn't have the above limitations, but has > others, > with are acceptable for key input. > -- > Krzysztof Halasa -- Dmitry