| 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
| ||
|
Date: Wed, 25 Nov 2009 18:40:42 +0100 From: Krzysztof Halasa <khc@...waw.pl> To: lirc@...telmus.de (Christoph Bartelmus) Cc: awalls@...ix.net, dmitry.torokhov@...il.com, j@...nau.net, jarod@...hat.com, jarod@...sonet.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 lirc@...telmus.de (Christoph Bartelmus) writes: > I'm not sure what two ways you are talking about. With the patches posted > by Jarod, nothing has to be changed in userspace. > Everything works, no code needs to be written and tested, everybody is > happy. The existing drivers use input layer. Do you want part of the tree to use existing lirc interface while the other part uses their own in-kernel (badly broken for example) code to do precisely the same thing? We can have a good code for both, or we can end up with "badly broken" media drivers and incompatible, suboptimal existing lirc interface (though most probably much better in terms of quality, especially after Jarod's work). -- 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