microsoft / microsoft/Windows-driver-samples
Using SetupDiEnumDeviceInterfaces instead of symbolic links
Open
request
- Dominant language
- C
- Stars
- 7.8k
- Forks
- 5k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 7
Description
Am I right in thinking that usb/usbview/enum.c now uses 5 different SetupAPI calls to get a device path instead of simply trying several symbolic links to enumerate the interface? if so, I suggest we edit the Readme, as it is confusing: both methods return host controllers and what is in the Readme is not what is in the code.
Which method do you prefer?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.