Date: Sun, 23 Nov 2008 21:33:11 +0100 (CET)
From: Jiri Kosina <jkosina@suse.cz>
To: Christoph Bartelmus <lirc@bartelmus.de>
cc: pavel@suse.cz, jonsmirl@gmail.com, jrm8005@gmail.com,
       linux-kernel@vger.kernel.org
Subject: Re: In-kernel IR remote control support
In-Reply-To: <AqQThtpZjFB@christoph>
Message-ID: <alpine.LRH.1.10.0811232128050.26670@twin.jikos.cz>
References: <AqQThtpZjFB@christoph>
User-Agent: Alpine 1.10 (LRH 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1263
Lines: 31

On Sun, 23 Nov 2008, Christoph Bartelmus wrote:

> You can have LIRC setup to decode all common remote control protocols.  
> It's just a matter of proper packaging and pre-configuration. You don't 
> have to write a single line of code for this (I still have to add uinput 
> support, though, which I probably would have done by now, if I weren't 
> busy writing posts like this).

Just a question -- how much is the situation different to what we 
currently have for HID devices?

For these, we currently have common code, that is able to handle all the 
"normal" devices by default, that are fully compliant with the HID 
standard.
For the devices that don't behave that well, we have specialized drivers, 
that use all the generic HID infrastructure to handle the 
standard-compliant behavior of the device and allows the specialized 
drivers to implement only the parts that violate standard.

It's pretty lightweight and seems to work well. Wouldn't this work also 
for LIRC drivers?

-- 
Jiri Kosina
SUSE Labs

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/