On Wednesday 10 September 2008 15:14:32 Christoph Hellwig wrote:
quoted text
> 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.

Some drivers don't report events but deliver the signal to the lirc 
daemon. The daemon decodes the signal. Decoding of several IR protocols 
and mapping of each possible remote to events are things much easier 
done in userspace.
Aslo LIRC is not only about IR input but also output.

See following mail from Christoph Bertelmus for more details.
http://sourceforge.net/mailarchive/message.php?msg_id=AAryKgq9UOB%40bartelmus.de

quoted text
> To make the migration easier for exiting 
> users we could add a /dev/lirc driver ontop of the input layer,

This shouldn't be necessary since the lirc daemon can already read from 
input devices.

Janne
--
unsubscribe notice
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/