device filtering support

[Xiaofan Chen]

On Sat, Feb 4, 2012 at 10:11 PM, Pete Batard <pete at akeo.ie> wrote:
> On 2012.02.04 01:25, Xiaofan Chen wrote:
>> Take note libusbK.dll supports libusb0.sys, libusbK.sys and
>> WinUSB.sys. Therefore using libusbK.dll covers most of the
>> driver used and only the HID is an exception.
>>
>> However, Pete indicated that he would like to keep the
>> standalone WinUSB backend, so that will keep a lot of
>> duplicate codes inside the Windows backend.
>
> Please do not distort the facts according to the point you are trying to
> make. As I have now told both you and Travis twice, the issue with forcing
> all users to go through libusbK always for WinUSB accesses is as follows:
> - It makes it mandatory to have libusbK installed along with libusbx on
> Windows
> - We very much have existing commercial users that rely on libusb-1.0/WinUSB
> and who created a custom installer (one that doesn't use libwdi) to install
> WinUSB. We can't exactly go back an tell them:
>
> "- Well, you will have to spend time modifying your installer and make it
> install the libsubK library along WinUSB...
> - Why? Will I see any benefit from doing that?
> - Not really. But it's just _slightly_ easier for us to do it that way..."
>

Actually I am just stating a fact and I have no strong opinion of using
libusb.dll and libusbK.dll along with libusbx Windows backend. In fact,
I am fine with Graeme's existing approach of directly talking to libusb0.sys
and I am certainly fine if you choose that approach and directly talk to
libusbK.sys as well. In that case, no extra alls are needed for libusbx.


-- 
Xiaofan