linux-kernel - Re: [PATCH] lirc: remove backwards compatibility macro obfuscation

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] [day] [month] [year] [list]

Date:	04 Feb 2007 04:04:00 +0100
From:	lirc@...telmus.de (Christoph Bartelmus)
To:	vincent.vanackere@...il.com
cc:	penberg@...helsinki.fi
Subject: Re: [PATCH] lirc: remove backwards compatibility macro obfuscation

Hi Vincent,

on 02 Feb 07 at 12:04, you wrote:
> On 2/2/07, Pekka J Enberg <penberg@...helsinki.fi> wrote:
>> From: Pekka Enberg <penberg@...helsinki.fi>
>>  [...]
>>  drivers/lirc_atiusb/lirc_atiusb.c           |  102 -----------------
>                               ^^^^^^^^^^^^^^
>
>  I may be mistaken, but the lirc_atiusb module looks redondant with
> the driver already in drivers/usb/input/ati_remote.c.
> Moreover, I was under the impression that the input layer was
> currently considered the "right way" to implement the kernel side lirc
> needs

No. Using the input layer makes no sense for most lirc drivers. The  
hardare used does not decode the IR signals itself but only provides raw  
signal timings. Those signals are decoded in userspace by lircd.
It would be a really bad idea trying to do this decoding in kernel  
space.

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/