| 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
| ||
|
Message-ID: <m31vjorgyz.fsf@intrepid.localdomain> Date: Mon, 23 Nov 2009 23:53:08 +0100 From: Krzysztof Halasa <khc@...waw.pl> To: Devin Heitmueller <dheitmueller@...nellabs.com> Cc: Christoph Bartelmus <lirc@...telmus.de>, dmitry.torokhov@...il.com, j@...nau.net, jarod@...hat.com, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org, linux-media@...r.kernel.org, mchehab@...hat.com, superm1@...ntu.com Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure Devin Heitmueller <dheitmueller@...nellabs.com> writes: > For example, you might want the IR receiver to be listening for codes > using the "Universal Remote Control XYZ" profile and the IR > transmitter pretending to be "Cable Company Remote Control ABC" when > blasting IR codes to the cable box. Ideally, there would be a single > shared database of the definitions of the remote controls, regardless > of whether you are IR receiving or transmitting. Well, with different receivers, the maps must certainly be different. There can be single database in the userspace but the kernel must be uploaded the relevant info only. -- Krzysztof Halasa -- 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/
Powered by blists - more mailing lists