Re: [PATCH update] ieee1394: cycle timer read extension for raw1394/libraw1394

From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Pieter Palmers <pieterp@joow.be>
Cc: Dan Dennedy <dan@dennedy.org>,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH update] ieee1394: cycle timer read extension for raw1394/libraw1394
Date: Sat, 03 Feb 2007 20:03:51 +0100	[thread overview]
Message-ID: <45C4DC97.3050101@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.e06f68103e99e517@s5r6.in-berlin.de>

I wrote:
> +++ linux/drivers/ieee1394/raw1394.h	2007-02-03 13:47:34.000000000 +0100
> @@ -178,4 +178,14 @@ struct raw1394_iso_status {
>  	__s16 xmit_cycle;
>  };
>  
> +/* 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 */

Pieter,
one more thing. Do you want to hand out the cycle_timer bitfield to
userspace as-is, or would it make sense to postprocess it in some way?
-- 
Stefan Richter
-=====-=-=== --=- ---==
http://arcgraph.de/sr/