At 12:47 PM 5/21/2007, Alan Stern wrote:
Dave:
The situation with regard to start_frame is a mess. Although the name
and the documentation refer to frame numbers, for high speed devices
the value stored there is a microframe number instead.
Clearly anyone who's interested in the value will
On Mon, 21 May 2007, Steve Calfee wrote:
Hi Alan,
About EHCI frame numbers. From the EHCI manual section 2.3.4:
quote
...
/quote
That's alright; I have a copy of the spec. You don't need to include
a lengthy extract, just put a reference to a section number.
So FRINDEX does count
Dave:
The situation with regard to start_frame is a mess. Although the name
and the documentation refer to frame numbers, for high speed devices
the value stored there is a microframe number instead.
Clearly anyone who's interested in the value will want to know the full
microframe number. But
On Monday 21 May 2007, Alan Stern wrote:
Dave:
The situation with regard to start_frame is a mess. Although the name
and the documentation refer to frame numbers, for high speed devices
the value stored there is a microframe number instead.
Clearly anyone who's interested in the value
Clearly anyone who's interested in the value will want to know the full
microframe number. But on the other hand, the value returned from
ehci_get_frame() actually _is_ a frame number, so there's no way for
drivers to learn the current microframe. Thus we have several related
problems:
On Mon, 21 May 2007, David Brownell wrote:
On Monday 21 May 2007, Alan Stern wrote:
Dave:
The situation with regard to start_frame is a mess. Although the name
and the documentation refer to frame numbers, for high speed devices
the value stored there is a microframe number instead.
