On Thu, Sep 6, 2012 at 6:26 AM, Pete Batard <p...@akeo.ie> wrote:
> OK, IMO, the best way to address that last issue we have with libusb0 as
> composite device is by modifying the libusb0 inf file to create a Device
> Interface GUID during installation.
>
> In this case, this is really a one liner change in libwdi:
> --- "a/D:\\libwdi\\libwdi\\libusb0.inf.in"
> +++ "b/D:\\libwdi\\libwdi\\libusb0.inf.in"
>   [libusb_add_reg_hw]
>   HKR,,SurpriseRemovalOK,0x00010001,1
> +HKR,,DeviceInterfaceGUIDs,0x00010000,%DeviceGUID%

Yes this indeed solved the problem with libusb0.sys
with regard to composite device.
>
> And now for some additional notes:
>
> Note 1: Unlike what is the case for the Class GUID, libwdi creates the
> Device Interface GUID on the fly (kind of makes sense if you want the
> interface GUID to be unique)
>
> Note 2: As long as you use the default composite parent Windows driver,
> you can very much access composite interface #2 with libusbx even if
> interface #1 has no driver, or a proprietary/non libusbx compatible one.
> It's only when WinUSB is in charge of the parent composite device that
> you have to claim #1 before you can claim #2.

It is good to be put in the doc.

> Note 3: Not having a Device Interface GUID is only an issue for
> composite devices. For anything that's not composite, it doesn't matter
> if the inf has one or not. I'll try to add a note about this in the
> Windows backend limitations.

It is also good to put this in the doc.



-- 
Xiaofan

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

Reply via email to