From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Halasa Subject: Re: [RFC] Should we create a raw input interface for IR's ? Date: Wed, 25 Nov 2009 21:49:28 +0100 Message-ID: References: <829197380911251020y6f330f15mba32920ac63e97d3@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from khc.piap.pl ([195.187.100.11]:52066 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933459AbZKYUtX (ORCPT ); Wed, 25 Nov 2009 15:49:23 -0500 In-Reply-To: (Jarod Wilson's message of "Wed, 25 Nov 2009 13:43:24 -0500") Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Jarod Wilson Cc: Devin Heitmueller , Christoph Bartelmus , awalls@radix.net, dmitry.torokhov@gmail.com, j@jannau.net, jarod@redhat.com, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, mchehab@redhat.com, superm1@ubuntu.com Jarod Wilson writes: > Well, we've got a number of IOCTLs already, could extend those. > (Although its been suggested elsewhere that we replace the IOCTLs with > sysfs knobs). Not sure if sysfs would be fast enough. > A simple sysfs attr that contains the name of the default config file > for the bundled remote of a given receiver would seem simple enough to > implement. A model name maybe. Though there is this mapping thing which I think need ioctl(). -- Krzysztof Halasa