From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Smirl Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? Date: Sat, 28 Nov 2009 15:14:32 -0500 Message-ID: <9e4733910911281214o614fd912wbbe5dcc50108aeea@mail.gmail.com> References: <9e4733910911280906if1191a1jd3d055e8b781e45c@mail.gmail.com> <4B116954.5050706@s5r6.in-berlin.de> <9e4733910911281058i1b28f33bh64c724a89dcb8cf5@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mail-qy0-f194.google.com ([209.85.221.194]:39149 "EHLO mail-qy0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752373AbZK1UO2 (ORCPT ); Sat, 28 Nov 2009 15:14:28 -0500 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Krzysztof Halasa Cc: Stefan Richter , Christoph Bartelmus , awalls@radix.net, dmitry.torokhov@gmail.com, j@jannau.net, jarod@redhat.com, jarod@wilsonet.com, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, maximlevitsky@gmail.com, mchehab@redhat.com, superm1@ubuntu.com On Sat, Nov 28, 2009 at 2:55 PM, Krzysztof Halasa wrote: > Jon Smirl writes: > >> EVIOCSKEYCODE is lacking, first parameter is an INT. Some decoded IR >> codes are over 32b. Christoph posted an example that needs 128b. > > This only means that the existing interface is limited. > >> This >> is a problem with ioctls, they change size depending on platform and >> endianess. > > But not this: you can use fixed-width u16, u32, u64 and e.g. u8[x]. > I don't know an arch which changes int sizes depending on endianness, > is there any? Endianess comes into play when send/receiving multibyte integers on platforms with different endianess. That where the hton() stuff comes from. IOCTLs obviously work, you just have to allow for all of this stuff when writing them. http://linux.die.net/man/3/htonl > 32/64 binary compatibility needs some minimal effort. > -- > Krzysztof Halasa > -- Jon Smirl jonsmirl@gmail.com