Description: there is mismatch between the current USBIP_VERSION under Linux and Windows in the usbip-utils. Linux version is at 0x00000111 for the usbip-utils, while the driver doesn't have any trace left; under Windows, the driver is at 0x000106 (sic) while usbip-utils exposes both 0x000111 (config.h) and 0x000106 (configure.ac).
The usbip-utils and driver both use the same USBIP_VERSION definition, at least for a while, but there was a confusion in its meaning: it should represent a protocol version that doesn't increase unless the protocol is changed).
There is also a LIBUSBIP_VERSION, which seems to still be at 0.1.0 under both OSes.
Clarify how these versions are to be interpreted under Linux.
Mirror them under Windows.
Identify every changse to the protocol under Linux that would need to be ported under Windows to officially move everything on a par with the current protocol version (0x00000111).
Reported by: lcgamboa and Anonymous Date: 2013-03-20 Links: -https://github.com/lcgamboa/USBIP-Virtual-USB-Device/commit/6f42bc5681a89dfa328f227d8c91e172ff5d9c9c
Description: there is mismatch between the current USBIP_VERSION under Linux and Windows in the usbip-utils. Linux version is at 0x00000111 for the usbip-utils, while the driver doesn't have any trace left; under Windows, the driver is at 0x000106 (sic) while usbip-utils exposes both 0x000111 (config.h) and 0x000106 (configure.ac).
The usbip-utils and driver both use the same USBIP_VERSION definition, at least for a while, but there was a confusion in its meaning: it should represent a protocol version that doesn't increase unless the protocol is changed).
There is also a LIBUSBIP_VERSION, which seems to still be at 0.1.0 under both OSes.