From: Xiaofan C. <xia...@gm...> - 2015-03-09 09:22:15
|
On Mon, Mar 9, 2015 at 6:40 AM, Pete Batard <pe...@ak...> wrote: > On 2015.03.06 13:13, Dmitry Fleytman wrote: > >>> 7. I think we're gonna have to solve the confusion of having something >>> like windows_common.h + [winnt_common.h|windows_core.h] + windows_usb.h > >> (...) >>> have a windows_driver.c and windows_filter.c >> >> What if we establish naming by API names, i.e. windows_usb.c with support > > for WinUsb/libusbk becomes windows_winusb.c and UsbDk support stays >> at windows_usbdk.c? > > That sounds much clearer than what I was proposing! > Unless the libusb0/libusbK people are unhappy to see only the WinUSB > name mentioned, I think your proposal is the better solution indeed. I do not see this as a problem myself. In fact, I think WinUSB is the preferred general purpose driver in the future. libusb0.sys does not matter too much for libusb Windows backend since its unique filter capability does not work too well for many device. WinUSB has bridged libusbK's main advantage (isoc transfer) in Windows 8.1 so that libusbK's limited use will probably for those who like the Windows only libusbK API. UsbDk's dynamic driver switching capability is interesting. So I think it may well have some niches as well. To Travis: if you have some objection, please respond. If no response, then I assume you are okay with the proposal. -- Xiaofan |