http://bugs.winehq.org/show_bug.cgi?id=58326
Bug ID: 58326 Summary: SetupDiGetClassDevs does not enumerate USB devices Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs@winehq.org Reporter: mail@3v1n0.net Distribution: ---
Created attachment 78694 --> http://bugs.winehq.org/attachment.cgi?id=78694 Example device enumerator
In order to enumerate the USB devices in the system, a window application is expected (https://github.com/microsoft/Windows-driver-samples/blob/main/usb/usbview/en...) to use SetupDiGetClassDevs with the `GUID_DEVINTERFACE_USB_DEVICE` GUID, however this returns nothing in WINE.
Running a simpler example (attached) of the enumerator that extends to all the device types, I get in fact:
``` Device info is 0x7ffffe8d4760 Device info Date is 1 {4D36E96E-E325-11CE-BFC1-08002BE10318} Device desc name is Generic Non-PnP Monitor Device driver name is {4D36E96E-E325-11CE-BFC1-08002BE10318}\0000 Failed at 186 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0003 Failed at 186 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0002 Failed at 186 Device info Date is 1 {4D36E968-E325-11CE-BFC1-08002BE10318} Device desc name is Wine Adapter Device driver name is {4D36E968-E325-11CE-BFC1-08002BE10318}\0000 Failed at 186 Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318} Device desc name is Wine HID bus driver Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0000 Failed at 186 Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318} Device desc name is Wine USB bus driver Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0001 Failed at 186 Device info Date is 1 {00000000-0000-0000-0000-000000000000} Failed at 159 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID compatible device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0000 Failed at 186 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID compatible device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0001 Failed at 186 Device info Date is 0 {00000000-0000-0000-0000-000000000000} ```
While under a windows VM the same code also returns (for example):
Device info Date is 1 {CA3E7AB9-B4C3-4AE6-8251-579EF933890F} Device desc name is USB Video Device Device driver name is {ca3e7ab9-b4c3-4ae6-8251-579ef933890f}\0001
As per this it's not possible to find out the device ID that it could be used via `WinUsb_Initialize(deviceHandle, &winusbHandle)` (even though this doesn't seem to work even passing an hardcoded path).
http://bugs.winehq.org/show_bug.cgi?id=58326
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, hardware, source, | |testcase
--- Comment #1 from Ken Sharp imwellcushtymelike@gmail.com --- What version of Wine are you using?
http://bugs.winehq.org/show_bug.cgi?id=58326
--- Comment #2 from Marco Trevisan (TreviƱo) mail@3v1n0.net --- (In reply to Ken Sharp from comment #1)
What version of Wine are you using?
That's been tested with wine-9 and older
http://bugs.winehq.org/show_bug.cgi?id=58326
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com Component|setupapi |usb
--- Comment #3 from Zeb Figura z.figura12@gmail.com --- What is your end goal?