2011/3/15 Emmanuel Blot :
>> It is a feature (obtain device bus number) that already has been
>> requested, and is scheduled to alpha 2 release.
>
> BTW, would it not be easier to release pyusb-1.0.0a1 as pyusb 1.0.0 as
> it seems quite stable now, and add new features such this (useful ;-))
> one
> It is a feature (obtain device bus number) that already has been
> requested, and is scheduled to alpha 2 release.
BTW, would it not be easier to release pyusb-1.0.0a1 as pyusb 1.0.0 as
it seems quite stable now, and add new features such this (useful ;-))
one in a new 1.1.x release?
Cheers,
Ma
2011/3/15 Emmanuel Blot :
>> However, it does not seems that pyusb exposes this information.
>
> Here is a sample patch to enable these entry points with libusb-1.0,
> against pyusb-1.0.0a1
>
> This patch cannot be integrated as is, as I've not checked how to
> implement their equivalent for neithe
> However, it does not seems that pyusb exposes this information.
Here is a sample patch to enable these entry points with libusb-1.0,
against pyusb-1.0.0a1
This patch cannot be integrated as is, as I've not checked how to
implement their equivalent for neither libusb-0.1 nor openusb-x
Using a c
> Is there any way to compare/test whether two usb.core.Device instances
> do actually refer to the same physical device?
Looking at the libusb1.0 interface, it seems that the following entry points
/** \ingroup dev
* Get the number of the bus that a device is connected to.
* \param dev a devi
