gecko said:
have two Enhanced entries, for the two EHCI blocks.
Thanks Paul. I will try to digest what you say above.
As I have said in earlier un-related posts, I have two machines.
I looked closely at both and this is what I see:
Machine 1 (XP)
-MachSpeed K8M8MSR2 mobo.
-Six physical USB ports on the back.
-Four USB ports are connected to one part of the mobo.
-Two USB ports are connected to different mobo header.
Machine 2 (VISTA)
-ASUS K8V SE Deluxe mobo.
-Eight physical USB ports on the back.
-Four USB ports are connected to one part of the mobo.
-Four USB ports are connected to different mobo header.
Strangely (to me), Device Manager on BOTH machines show identical
results:
Universal Serial Bus controllers
USB Root Hub
USB Root Hub
USB Root Hub
USB Root Hub
USB Root Hub
VIA Rev 5 or later USB Universal Host Controller
VIA Rev 5 or later USB Universal Host Controller
VIA Rev 5 or later USB Universal Host Controller
VIA Rev 5 or later USB Universal Host Controller
VIA Enhanced USB Controller
It bothers me that Device Managers show the same thing, despite the
fact that the two machine have different USB layouts. How can that
be? It is not obvious to me how to relate each Device Manager entry
to specific USB ports. Therefore, I was thinking some utility might
exist that would be more specific in that regard, and might even tell
me what ports are USB1 and what ones are USB2. But maybe they ALL are
now USB2?
-GECKO
K8V SE Deluxe has a VT8237R Southbridge. Some specs are here.
http://www.via.com.tw/en/products/chipsets/southbridge/vt8237/specs.jsp
"Support for 8 USB 2.0/1.1 ports"
So what is the difference between a motherboard with 8 ports and one
with 6 ports ? Two ports aren't wired to anything, and are just
sitting there idle on the chip.
Some points to ponder.
1) What you see in Device Manager is "logic blocks" and not ports.
Ports are not shown.
2) Ports are switchable between operating in a USB 1.1 mode and a USB2 mode.
They support both and are backward compatible. That is accomplished by
having a switch at the port, to either connect the port to a USB 1.1 logic
block or a USB 2.0 logic block.
And that is why you should have looked at PDF page 222 of the spec I pointed
out, as once you see the diagram, it makes a little more sense.
If you want to see what is going on at the port level, you need this.
UVCView first appeared on the Microsoft site, and is part of some SDK.
It was downloadable for a couple years, and then disappeared. I used
to point people to a copy on web.archive.org, but at least one person
had a problem with that copy (the last byte of the file is missing,
but that didn't prevent it from running on my computer). This copy
appears to be intact, and the file information matches the original
I got from Microsoft. (You could always download the web.archive.org
copy, and add 00 hex to the file with a hex editor. But I don't want
to make this harder than it has to be.) You compute the md5sum with a
program called md5sum, and it is handy to have a copy of that sitting
around as well. I use it for verifying the checksum on some Linux
downloads.
ftp://ftp.efo.ru/pub/ftdichip/Utilities/UVCView.x86.exe
File size is 167,232 bytes.
MD5sum is 93244d84d79314898e62d21cecc4ca5e
In this sample screen shot (from a precursor of the current version),
you can see a USB device connect to port 3. The port 3 entry is
part of a Root Hub that has six port entries, and that tells you
the device is running in USB2 mode. If the USB device instead had
appeared in one of the upper entries, where the Root Hub has only
two entries, then you'd know the device was running in USB 1.1 mode.
Note that there is one anomaly with that picture, and one of the
USB 1.1 Root Hubs is missing in the displayed image. It might be
present when the left hand pane scrolls down.
To make sense of the parameters in the right hand screen, you need
to go to usb.org and download a copy of the USB2 spec. You can
also google the parameter names, and get info that way.
Paul