Messages in this thread | | | Date | Mon, 23 Nov 2009 23:18:12 -0500 | From | Jarod Wilson <> | Subject | Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure |
| |
On 11/23/2009 04:10 PM, Christoph Bartelmus wrote: > Hi Jarod, > > on 23 Nov 09 at 14:17, Jarod Wilson wrote: >>> Krzysztof Halasa wrote: > [...] >>> If you see patch 3/3, of the lirc submission series, you'll notice a driver >>> that has hardware decoding, but, due to lirc interface, the driver >>> generates pseudo pulse/space code for it to work via lirc interface. > >> Historically, this is true. > > No, it's not. > I think you misunderstood the code. The comment may be a bit misleading, > too. > Early iMON devices did not decode in hardware and the part of the driver > that Krzystof is referring to is translating a bit-stream of the sampled > input data into pulse/space durations.
Sorry, no, I know the newer devices don't actually send pulse/data info out to userspace, just hex codes that correspond to key presses. What I meant was "onboard decoding devices can operate as pure input devices or in classic lirc mode", leaving out the details on exactly what they were sending out to userspace. :)
-- Jarod Wilson jarod@wilsonet.com
| |