On 05/25/10 15:40, David S. Ahern wrote:
USB 2.0 leverages companion UHCI or OHCI host controllers for full and
low speed devices. I do not see an appropriate means for doing that bus
transition and could use some suggestions.
Hmm. Well. That doesn't really fit into the qdev tree model ...
Am 26.05.2010 13:47, schrieb Gerd Hoffmann:
On 05/25/10 15:40, David S. Ahern wrote:
USB 2.0 leverages companion UHCI or OHCI host controllers for full and
low speed devices. I do not see an appropriate means for doing that bus
transition and could use some suggestions.
Hmm. Well. That
Hi,
USB devices can support both 1.1 and 2.0, right? Who decides which
protocol is used then? I think the OS can speak 1.1 to the device even
in case a ehci controller is present (but unused by the OS), right?
AFAIK the OS must tell the EHCI that it should hand the device off to
the
On 05/26/2010 06:48 AM, Gerd Hoffmann wrote:
Hi,
USB devices can support both 1.1 and 2.0, right? Who decides which
protocol is used then? I think the OS can speak 1.1 to the device even
in case a ehci controller is present (but unused by the OS), right?
AFAIK the OS must tell the
Am 26.05.2010 15:06, schrieb David S. Ahern:
On 05/26/2010 06:48 AM, Gerd Hoffmann wrote:
Hi,
USB devices can support both 1.1 and 2.0, right? Who decides which
protocol is used then? I think the OS can speak 1.1 to the device even
in case a ehci controller is present (but unused by
On 05/26/2010 07:23 AM, Kevin Wolf wrote:
Am 26.05.2010 15:06, schrieb David S. Ahern:
On 05/26/2010 06:48 AM, Gerd Hoffmann wrote:
Hi,
USB devices can support both 1.1 and 2.0, right? Who decides which
protocol is used then? I think the OS can speak 1.1 to the device even
in case
On Wed, May 26, 2010 at 08:00:33AM -0600, David S. Ahern wrote:
On 05/26/2010 07:23 AM, Kevin Wolf wrote:
Am 26.05.2010 15:06, schrieb David S. Ahern:
My understanding is that the port routing happens internally to the host
controller based on device speed - section 4.2 (pag 64) of:
USB 2.0 leverages companion UHCI or OHCI host controllers for full and
low speed devices. I do not see an appropriate means for doing that bus
transition and could use some suggestions.
I've read through the code for the legacy path in handling USB devices
(-usbdevice CLI arg and usb_add monitor
