On Tue, 22 Aug 2017, Nicolas Boichat wrote:
> Computes and forwards the device timestamp according to the
> specification.
>
> Many devices use a 16-bit timestamp field, with a resolution
> of 100us, therefore rolling around very frequently (every
> 6.5 seconds). To make sure there is no
On Tue, 22 Aug 2017, Nicolas Boichat wrote:
> Computes and forwards the device timestamp according to the
> specification.
>
> Many devices use a 16-bit timestamp field, with a resolution
> of 100us, therefore rolling around very frequently (every
> 6.5 seconds). To make sure there is no
On Oct 02 2017 or thereabouts, Jiri Kosina wrote:
> On Tue, 22 Aug 2017, Nicolas Boichat wrote:
>
> > Computes and forwards the device timestamp according to the
> > specification.
> >
> > Many devices use a 16-bit timestamp field, with a resolution
> > of 100us, therefore rolling around very
On Oct 02 2017 or thereabouts, Jiri Kosina wrote:
> On Tue, 22 Aug 2017, Nicolas Boichat wrote:
>
> > Computes and forwards the device timestamp according to the
> > specification.
> >
> > Many devices use a 16-bit timestamp field, with a resolution
> > of 100us, therefore rolling around very
On Tue, 22 Aug 2017, Nicolas Boichat wrote:
> Computes and forwards the device timestamp according to the
> specification.
>
> Many devices use a 16-bit timestamp field, with a resolution
> of 100us, therefore rolling around very frequently (every
> 6.5 seconds). To make sure there is no
On Tue, 22 Aug 2017, Nicolas Boichat wrote:
> Computes and forwards the device timestamp according to the
> specification.
>
> Many devices use a 16-bit timestamp field, with a resolution
> of 100us, therefore rolling around very frequently (every
> 6.5 seconds). To make sure there is no
Computes and forwards the device timestamp according to the
specification.
Many devices use a 16-bit timestamp field, with a resolution
of 100us, therefore rolling around very frequently (every
6.5 seconds). To make sure there is no ambiguity, the
timestamp reported to the input stack reset to 0
Computes and forwards the device timestamp according to the
specification.
Many devices use a 16-bit timestamp field, with a resolution
of 100us, therefore rolling around very frequently (every
6.5 seconds). To make sure there is no ambiguity, the
timestamp reported to the input stack reset to 0
8 matches
Mail list logo