| 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: <m3zl5ttva0.fsf@intrepid.localdomain> Date: Tue, 08 Dec 2009 15:06:31 +0100 From: Krzysztof Halasa <khc@...waw.pl> To: Mauro Carvalho Chehab <mchehab@...hat.com> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, Gerd Hoffmann <kraxel@...hat.com>, Jarod Wilson <jarod@...sonet.com>, Christoph Bartelmus <lirc@...telmus.de>, awalls@...ix.net, j@...nau.net, jarod@...hat.com, jonsmirl@...il.com, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org, linux-media@...r.kernel.org, superm1@...ntu.com Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? Mauro Carvalho Chehab <mchehab@...hat.com> writes: > Yes, an opaque type for scancode at the userspace API can be better, but > passing a pointer to kernel will require some compat32 logic (as pointer > size is different on 32 and 64 bits). Yes. I think we can't avoid that, but it's a single compat handler, I wouldn't worry about it too much. We don't need it in every driver fortunately. > We may use something like an u8[] with an arbitrary large number of > bytes. Yes. All of this pointed to by the pointer. > In this case, we need to take some care to avoid LSB/MSB troubles. Sure. -- 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