linux-kernel - Re: In-kernel IR remote control support

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]

Message-ID: <Ar6VqEpojFB@christoph>
Date:	02 Dec 2008 19:00:00 +0100
From:	lirc@...telmus.de (Christoph Bartelmus)
To:	pavel@...e.cz
Cc:	linux-kernel@...r.kernel.org
Subject: Re: In-kernel IR remote control support

Hi Pavel,

on 23 Nov 08 at 19:01, Pavel Machek wrote:
[...]
>>> support for the common remotes. That seems like a net plus to me, and
>>> you can still keep the obscure ones in userland.
>>
>> Jon's code and the LIRC approach exclude each other. It does not make
>> sense to have both in the kernel. There have been attempts to clean up
>> LIRC code to be included in the kernel. The current discussion lessens my
>> hope that this will happen anytime soon.

> I don't see why we could not use Jon's code for common remotes decoded
> mostly by hw, and your code for the obscure cases.

Ok, how about this:
there's one common point in lirc_dev where all IR timing data is handled.
Jon's code can grab the data at this point and feed it into its state  
machine. That way there's no need to change any of the existing drivers.
And we all work together to get this stuff ready for inclusion into the  
kernel.

Christoph
--
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/