linux-kernel - Re: [PATCH 01/18] lirc core device driver infrastructure

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: <AlnE2jFojFB@christoph>
Date:	13 Sep 2008 09:20:00 +0200
From:	lirc@...telmus.de (Christoph Bartelmus)
To:	maximlevitsky@...il.com
Cc:	superm1@...ntu.com
Subject: Re: [PATCH 01/18] lirc core device driver infrastructure

Hi Maxim,

on 12 Sep 08 at 00:28, Maxim Levitsky wrote:
[...]
> What do you, lirc developers think about making lircd a daemon that injects
> input events via uinput?

I have already agreed to implement this in lircd.
The reason why I didn't until now is that there never was any reguest for
such a feature from real users of LIRC. This is often suggested by people
from an architectural viewpoint, because it's nice to have a unified
interface through the input layer. But if you start using LIRC you usually
realise quite fast that simple key events are not enough to build a remote
controlled home entertainment system for example.
But if enough people want this feature, it will be in the next release.

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/