[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45CDD490.2020004@s5r6.in-berlin.de>
Date: Sat, 10 Feb 2007 15:20:00 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: linux-kernel@...r.kernel.org
CC: Pieter Palmers <pieterp@...w.be>, Dan Dennedy <dan@...nedy.org>,
linux1394-devel@...ts.sourceforge.net
Subject: compat_ioctl (was [PATCH update] ieee1394: cycle timer read extension
for raw1394/libraw1394)
I wrote on 2007-02-03:
> +#define RAW1394_IOC_GET_CYCLE_TIMER \
> + _IOR ('#', 0x30, struct raw1394_cycle_timer)
...
> +/* argument to RAW1394_IOC_GET_CYCLE_TIMER ioctl */
> +struct raw1394_cycle_timer {
> + /* contents of Isochronous Cycle Timer register,
> + as in OHCI 1.1 clause 5.13 (also with non-OHCI hosts) */
> + __u32 cycle_timer;
> +
> + /* local time in microseconds since Epoch,
> + simultaneously read with cycle timer */
> + __u64 local_time;
> +};
> #endif /* IEEE1394_RAW1394_H */
Hmm, is this struct padded on 64bit platforms?
If so, would
struct raw1394_cycle_timer {
__u64 local_time;
__u32 cycle_timer;
};
be padded too?
--
Stefan Richter
-=====-=-=== --=- -=-=-
http://arcgraph.de/sr/
-
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