Messages in this thread | | | Date | Wed, 10 Sep 2008 09:37:19 -0400 | From | "Jon Smirl" <> | Subject | Re: [PATCH 06/18] lirc driver for the ATI USB RF remote receiver |
| |
On 9/10/08, Christoph Hellwig <hch@infradead.org> wrote: > On Wed, Sep 10, 2008 at 09:05:58AM -0400, Jarod Wilson wrote: > > True, though I think some users still prefer using them with the lirc drivers > > for assorted reasons. Configuring something like mythtv to work with the > > ati_remote{,2} driver appears to be a bit more complex (or at least non- > > standard vs. several other popular remotes) and not as functional vs. > > configuring mythtv w/lirc_atiusb. > > > Bad idea to have two drivers for the same piece of hardware. And this > gets straight back into the why should lirc be different from the input > layer point raised earlies. I think we really shouldn't keep lirc as > a separate subsystem, but make sure all the drivers are written to the > input layer. To make the migration easier for exiting users we could > add a /dev/lirc driver ontop of the input layer, similar to how the ps2 > mouse and joystick drivers sit ontop of the input core.
There have been concerns on the lirc list that integrating with the input core would mean that the kernel has to translate from the lirc timing data to key strokes. Keyboards do their translation in user space, lirc can do the same, right? User space app receives lirc event and then calls a translation library function.
A second issue is that some IR drivers are completely in user space. Is there a mechanism for these user space drivers to send events down into the input layer? These events would then get queued with the other kernel generated events and be delivered to consuming apps in order.
> > > -- > 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/ >
-- Jon Smirl jonsmirl@gmail.com
| |