| 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: <m3r5riy7py.fsf@intrepid.localdomain> Date: Sat, 28 Nov 2009 16:44:41 +0100 From: Krzysztof Halasa <khc@...waw.pl> To: Maxim Levitsky <maximlevitsky@...il.com> Cc: Stefan Richter <stefanr@...6.in-berlin.de>, Jon Smirl <jonsmirl@...il.com>, Christoph Bartelmus <christoph@...telmus.de>, jarod@...sonet.com, awalls@...ix.net, 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] What are the goals for the architecture of an in-kernel IR system? Maxim Levitsky <maximlevitsky@...il.com> writes: > Generic decoder that lirc has is actually much better and more tolerant > that protocol specific decoders that you propose, Actually, it is not the case. Why do you think it's better (let alone "much better")? Have you at least seen my RC5 decoder? > You claim you 'fix' the decoder, right? Sure. > But what about all these lirc userspace drivers? Nothing. They are not relevant and obviously have to use lircd. If you can have userspace driver, you can have lircd as well. > How they are supposed to use that 'fixed' decoder. They are not. Is it a problem for you? How is your keyboard supposed to use scanner driver? -- 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