From: Erik Rull <erik.rull@rdsoftware.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] USB Hostport Differences
Date: Sun, 10 Jun 2012 12:51:29 +0200 [thread overview]
Message-ID: <4FD47C31.8080701@rdsoftware.de> (raw)
In-Reply-To: <4FD26F71.2030803@redhat.com>
Hans de Goede wrote:
> Hi,
>
> On 06/08/2012 10:56 PM, Erik Rull wrote:
>> Hans de Goede wrote:
>>> Hi,
>>>
>>> On 06/08/2012 06:33 PM, Erik Rull wrote:
>>>> Hi all,
>>>>
>>>> when assigning USB host devices to a guest using the hostport option,
>>>> there seem to be different formats, when calling info usbhost:
>>>>
>>>> - On my vanilla kernel linux there is a hostport format e.g. "1.5" or
>>>> "1.2"
>>>> - On my Debian 6.0 full blown linux there is a hostport format "2" or
>>>> "4", that means, there are no dots and only one number
>>>>
>>>
>>> Hmm, is this on the same machine, with the usb devices hooked up the same
>>> way? Normally these differences come
>>> from there being hubs in the chain, ie "2" or "4" indicate devices plugged
>>> directly into a root hub,
>>> "1.5" and "1.2" mean devices plugged into a hub, which itself is plugged
>>> into root port "1"
>>>
>>> Regards,
>>>
>>> Hans
>>
>> No it's on different machines - first with Intel Hardware, second with
>> AMD Hardware. I have no hubs attached, I use the ports that are offered
>> directly on the mainboard (EPIC Nano Connectors / ATX rear side panel).
>> On all other Intel systems I see the same effect with the "1.x" ports.
>> Only the AMD system shows the single numbers.
>>
>
> Those would be sandy bridge or newer Intel machines then, these no longer have
> an EHCI usb controller + UHCI companion controllers, but only an EHCI
> controller,
> so the root ports are USB-2 only. In order for USB-1 devices to still work the
> chipset has an integrated USB-2 hub (which can handle USB-1 ports), of you do
> lsusb you should see something like this in there:
>
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
>
> Which is why you get the 1.x for the motherboard ports, because there is
> actually
> a hub between the root hub and the ports.
>
> Regards,
>
> Hans
>
Hi Hans,
thanks for the explanation - so I will try to find out which way of USB
handling is given on the current system and then add the correct hostport
filters.
Is there an easier way of finding this kind of architecture automatically
beside grep'ing for such a Hub?
Best regards,
Erik
next prev parent reply other threads:[~2012-06-10 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 16:33 [Qemu-devel] USB Hostport Differences Erik Rull
2012-06-08 18:20 ` Hans de Goede
2012-06-08 20:56 ` Erik Rull
2012-06-08 21:32 ` Hans de Goede
2012-06-10 10:51 ` Erik Rull [this message]
2012-06-10 12:02 ` Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD47C31.8080701@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=hdegoede@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).