[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3bpimwfz0.fsf@intrepid.localdomain>
Date: Sat, 28 Nov 2009 21:29:23 +0100
From: Krzysztof Halasa <khc@...waw.pl>
To: Jon Smirl <jonsmirl@...il.com>
Cc: Stefan Richter <stefanr@...6.in-berlin.de>,
Christoph Bartelmus <lirc@...telmus.de>, awalls@...ix.net,
dmitry.torokhov@...il.com, j@...nau.net, jarod@...hat.com,
jarod@...sonet.com, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
maximlevitsky@...il.com, mchehab@...hat.com, superm1@...ntu.com
Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system?
Jon Smirl <jonsmirl@...il.com> writes:
> Endianess comes into play when send/receiving multibyte integers on
> platforms with different endianess.
It's the case when you're sending this data to a machine with
a different endianness. For example, in a network or to another CPU in
e.g. add-on card.
Ioctls are not affected by this, since both ends are the same.
Obviously you can be affected if you try to access data as integers in
one point and as arrays of bytes in the other, but it has nothing to do
with ioctls.
--
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