[lkml]   [2009]   [Nov]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] What are the goals for the architecture of an in-kernel IR system?
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.

> 32/64 binary compatibility needs some minimal effort.
> --
> Krzysztof Halasa

Jon Smirl

 \ /
  Last update: 2009-11-28 21:17    [W:0.225 / U:5.228 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site