Bochs: Supported USB Devices and Guests

1. Even though it is compliant to have a high-speed HID device, it is quite rare for such a device to be anything but low-speed. Some guests won't even try to use a high-speed HID device...
2. This Device is not support on this speed.
3. This controller is not supported under this Guest.
4. Supported with external/manufacture driver.
5. Function is sporadic. Needs a (Bochs?) fix.
6. Set HANDLE_TOGGLE_CONTROL to zero in usb_common.h
7. Note that all devices plugged into a hub must be used as low- or full-speed only.
8. The Guest can see the Hub, but constantly resets the hub, seeing a down-stream device connection and disconnection each time. I do not know why. Something to investigate.
9. Requires Service Pack 3 to be installed. i.e.: WinXP (Pro?) SP3. Earlier versions do not handoff the device correctly.
10. Win95 must be at least version 4.00.095B and have the XUSBSUPP.ZIP file from here installed.
11. Even with the XUSBSUPP in the previous note, HID is not supported on Win95.
12. Must set USB_HUB_ALWAYS_REPORT = 1. The Win95 driver thinks that a NAK is an error. Also set USB_HUB_VERSION = 0x0100.
13. The Win95 OHCI driver somehow finds an IN after the STATUS OUT in the Control Pipe and won't continue enumerating the device.
      I don't know if this is an error in Bochs or in Win95's driver. I tend to think that there is something with my OHCI code in Bochs,
      since the driver probably works under a real OHCI hardware and Win95, though I haven't checked for sure.
      (* However, Win95 crashes at the same place under QEMU as it does in Bochs, so I am not going to put much more effort into it. *)
14. Our EHCI doesn't perform as expected for this device/controller combination. Most likely Windows just doesn't handle high-speed HID devices. Linux does... :-)
15. The drive will not show up in Explorer until you type 'B:' in the address bar.
16. http://www.tinycorelinux.net/ v14.0
17. "failed to load firmware renesas_usb_fw.mem". Noted here, here, and here. Seems to be a firmware version issue.
18. https://www.slitaz.org/ v5.0 (uname -a returns v3.16.55. Is this the Linux kernel version?)
19. This Guest (Linux kernel version unknown. See note above.) has all kinds of errors with the xHCI, from specifying a speed of 0 or 255, not accepting an 'address device' command correctly, and other issues. I don't know what the reasons are yet, most likely my code since Linux is a well known and used kernel. However, since my code works with the NEC supplied driver on Windows, I really question what is the reason. If the Linux kernel version really is 3.16.55, this might explain why, being an old version. I will investigate.
20. Do you have a suggested Guest and can you confirm or deny support?

1. Windows 2000 and before don't like BMP files with a negative height value. A negative height value is allowed, and simply indicates that the data is stored "upside down" to the normal "upside down". Win2k and before will return an error about the file, making it look like the USB is not working.
2. I feel it necassary to express again, that even though the specification states that an HID device may be high-speed, I don't believe there are any high-speed HID devices lying around and through my research. None of the Windows Guests shown above support a high-speed HID device. Linux however...

Compliance Tests

1. Device does not work with this speed on Windows, which is the Host of the test.
2. Per port only. Global compliance relies on the Host Controller to resume which isn't fully implemented yet.