On Thu, Dec 03, 2009 at 10:51:00PM +0100, Christoph Bartelmus wrote: > Hi Mauro, > > on 03 Dec 09 at 19:10, Mauro Carvalho Chehab wrote: > [...] > >>> So the lirc_imon I submitted supports all device types, with the > >>> onboard decode devices defaulting to operating as pure input devices, > >>> but an option to pass hex values out via the lirc interface (which is > >>> how they've historically been used -- the pure input stuff I hacked > >>> together just a few weeks ago), to prevent functional setups from > >>> being broken for those who prefer the lirc way. > >> > >> Hmm. I'd tend to limit the lirc interface to the 'raw samples' case. > > >> Historically it has also been used to pass decoded data (i.e. rc5) from > >> devices with onboard decoding, but for that in-kernel mapping + input > >> layer really fits better. > > > I agree. > > Consider passing the decoded data through lirc_dev. > - there's a large user base already that uses this mode through lirc and > would be forced to switch to input layer if it disappears. I believe it was agreed that lirc-dev should be used mainly for decoding protocols that are more conveniently decoded in userspace and the results would be looped back into input layer through evdev which will be the main interface for consumer applications to use. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
