Status of "USB device support in wine"

[Uwe Bonnes]

Hallo,

I tried to run Alexander Morozov's patches against wine-git with libusb and
ftd2x devices.

Two remarks:
- The files from ftp://ftp.etersoft.ru/pub/people/amorozov/usb/current/ miss 
 lines in configure.ac to trigger the Makefile generation for usbd.sys and
usbhub.sys.
- The HardwareID in the registry is the end of the Registry key
http://msdn.microsoft.com/en-us/library/dd568018.aspx You can use the string
itself in the win registry. This helps, if you don't have the devices
installed on a windows machine available.

Both dll/drivers pair (libusb0.dll/libusb0.sys and ftd2xx.dll/ftdibus.sys)
work an a lot devices and so must scan the bus for matching devices. I
didn't get wine with the patches to do anything sensible in that case.

Alexander, could you perhaps have a look (ftd2xx at
http://www.ftdichip.com/Drivers/D2XX.htm and libusb-win32 at sourceforge)

Thanks

[Alexander Morozov]

> - The files from ftp://ftp.etersoft.ru/pub/people/amorozov/usb/current/ miss
>
> lines in configure.ac to trigger the Makefile generation for usbd.sys and
> usbhub.sys.

The part which is generated by tools/make_makefiles is not included in these patches.
> Both dll/drivers pair (libusb0.dll/libusb0.sys and ftd2xx.dll/ftdibus.sys)
> work an a lot devices and so must scan the bus for matching devices. I
> didn't get wine with the patches to do anything sensible in that case.

As I understand drivers should not scan bus. They are loaded for devices with appropriate
VID and PID. On Windows should modify inf-file (see Device Driver Installation on
libusb-win32.sourceforge.net). On WINE with USB patches should add appropriate registry
entries.