linux-kernel - Re: [PATCH 06/18] lirc driver for the ATI USB RF remote receiver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Sep 2008 10:13:18 -0400
From:	Jarod Wilson <jwilson@...hat.com>
To:	Janne Grunau <j@...nau.net>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Ville Syrjälä <syrjala@....fi>,
	linux-kernel@...r.kernel.org,
	Christoph Bartelmus <lirc@...telmus.de>
Subject: Re: [PATCH 06/18] lirc driver for the ATI USB RF remote receiver

On Wednesday 10 September 2008 09:44:17 Janne Grunau wrote:
> On Wednesday 10 September 2008 15:14:32 Christoph Hellwig 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.
>
> 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%40bartelm
>us.de

Yeah, I think that pretty well covers the issues.

> > 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.

Okay, so what I'm hearing and thinking is that we should at drop lirc_atiusb 
from consideration for inclusion, and instead extend ati_remote{,2} as/if 
necessary to be able to let the lirc daemon use it via the provided input 
device, so people can get the best of both worlds (it behaves like a keyboard 
if so configured, talks to lircd if so configured).

-- 
Jarod Wilson
jarod@...hat.com

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