On 2012.09.24 20:31, Greg KH wrote:
No one delivered any such "fix", all I got was a bunch of bug reports
this morning from the distros saying that usbutils was suddenly broken.
That shows that libusbx is really the problem here, and that maybe I
shouldn't depend on it anymore.
Could you please have a look at the release note that was posted on this
list? We did our best to ensure the possibility of breakage featured
prominently.
The full content of the post is replicated below.
Regards,
/Pete
On 2012.09.20 22:42, Pete Batard wrote:> Hi,
>
> It with pleasure that I would like to announce the release of libusbx
> 1.0.13. This version brings the following notable changes:
>
> * [MAJOR] Fix a typo in the API with struct libusb_config_descriptor
> where MaxPower was used instead of bMaxPower, as per the specs.
> If your application was accessing the MaxPower attribute, and you
> need to maintain compatibility with libusb or older versions, please see
> APPENDIX A below.
> * Fix broken support for the 0.1 -> 1.0 libusb-compat layer
> * Fix unwanted cancellation of pending timeouts as well as major timeout
> related bugs
> * Fix handling of HID and composite devices on Windows
> * Introduce LIBUSBX_API_VERSION macro
> * Add Cypress FX/FX2 firmware upload sample, based on fxload from
> http://linux-hotplug.sourceforge.net
> * Add libusb0 (libusb-win32) and libusbK driver support on Windows.
> Note that while the drivers allow it, isochronous transfers are not
> supported yet in libusbx. Also not supported yet is the use of
> libusb-win32 filter drivers on composite interfaces
> * Add support for the new get_capabilities ioctl on Linux and avoid
> unnecessary splitting of bulk transfers
> * Improve support for newer Intel and Renesas USB 3.0 controllers on
> Windows
> * Harmonize the device number for root hubs across platforms
> * Other bug fixes and improvements
>
> Release archives can be obtained from:
> https://sourceforge.net/projects/libusbx/files/releases/1.0.13/
>
> For more information, please visit: http://libusbx.org
>
> Regards,
>
> /Pete
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> APPENDIX A - Maintaining code compatibility with versions of libusb and
> libusbx that use MaxPower:
>
> If you must to maintain compatibility with versions of the library that
> aren't using the bMaxPower attribute in struct libusb_config_descriptor
> the recommended way is to use the new LIBUSBX_API_VERSION macro with an
> #ifdef.
>
> For instance, if your code was written as follows:
>
> if (dev->config[0].MaxPower < 250)
>
> Then you should modify it to have:
>
> #if defined(LIBUSBX_API_VERSION) && (LIBUSBX_API_VERSION >= 0x01000100)
> if (dev->config[0].bMaxPower < 250)
> #else
> if (dev->config[0].MaxPower < 250)
> #endif
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
