IOCTL_INTERNAL_USB_GET_BUS_INFO fails with USB 3.0

Hi all

We have been shipping a wdm driver for one of our high-speed USB devices for some time but a customer has reported problems connecting to a PC with an Etron USB 3.0 controller.

When connected to a USB2.0 port on the PC, the IOCTL_INTERNAL_USB_GET_BUS_INFO and IOCTL_INTERNAL_USB_GET_CONTROLLER_NAME work as expected, but connect to USB3.0 port and the ioctl returns STATUS_NOT_SUPPORTED. The calls are made during IRP_MN_START_DEVICE for our device.

I appreciate that this could be an issue for Etron but it could also be a problem with our code as I understand that there are now more rigorous checks going on…

Thanks

Sean

xxxxx@deva.co.uk wrote:

We have been shipping a wdm driver for one of our high-speed USB devices for some time but a customer has reported problems connecting to a PC with an Etron USB 3.0 controller.

When connected to a USB2.0 port on the PC, the IOCTL_INTERNAL_USB_GET_BUS_INFO and IOCTL_INTERNAL_USB_GET_CONTROLLER_NAME work as expected, but connect to USB3.0 port and the ioctl returns STATUS_NOT_SUPPORTED. The calls are made during IRP_MN_START_DEVICE for our device.

I appreciate that this could be an issue for Etron but it could also be a problem with our code as I understand that there are now more rigorous checks going on…

USB 3 in Windows is uncharted territory. It is the wild, wild west.
There is no USB 3 support from Microsoft, so when you use USB 3 today,
you are using a complete stack of drivers from the manufacturer. There
is no guarantee that the manufacturer has followed any of the rules
Microsoft established for USB 2.

Several of my clients have simply decided not to support their USB 2
devices on USB 3 until we have support from Microsoft, presumably in
Windows 8.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Thanks Tim

It looks like we’ll need to take a policy decision on this too or we could spend the rest of our lives chasing our tails.

Sean