| 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: <m3bpig2ar9.fsf@intrepid.localdomain> Date: Thu, 03 Dec 2009 19:06:02 +0100 From: Krzysztof Halasa <khc@...waw.pl> To: Jarod Wilson <jarod@...sonet.com> Cc: Trent Piepho <xyzzy@...akeasy.org>, Dmitry Torokhov <dmitry.torokhov@...il.com>, Jarod Wilson <jarod@...hat.com>, Jon Smirl <jonsmirl@...il.com>, Mauro Carvalho Chehab <mchehab@...hat.com>, Devin Heitmueller <dheitmueller@...nellabs.com>, Maxim Levitsky <maximlevitsky@...il.com>, awalls@...ix.net, j@...nau.net, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org, linux-media@...r.kernel.org, lirc-list@...ts.sourceforge.net, superm1@...ntu.com, Christoph Bartelmus <lirc@...telmus.de> Subject: Re: [RFC v2] Another approach to IR Jarod Wilson <jarod@...sonet.com> writes: > Perhaps we should clarify something here. Are we intending to > auto-create a new input device for every IR command set we see arrive > at the IR receiver? We don't want this, and we aren't really able to do this, because we never know if two different scan codes are part of the same or different command set. Sharing the protocol and e.g. group code doesn't mean it's the same remote. Different protocol doesn't mean it's a different remote and what's more important, doesn't mean the user wants it to be a different logical remote. -- 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