[usbip-devel] **Important Windows v.0.2.0.0 Info**

[Dan T. <DT...@na...>]

Just wanted to make all aware of my findings regarding where the source
code resides for the latest v. 0.2.0.0 Windows client.  The binary that
can be downloaded from SourceForge is built from the source code located
here:
http://usbip.svn.sourceforge.net/viewvc/usbip/obsolete/linux/trunk/

 

As per Arjan's email:

"obsolete/linux/trunk/src" is really the most recent windows client
code: I know the name is

awefull, but the intention was to also have the windows client code in
the linux kernel repository. (and as explained this has not happened
yet: it is something I still want to do but have not had time to do
yet).
The "windows/trunk" only contains the windows kernel code and not the
windows client code.
 
The binary that I downloaded (or the one I built from the same source
code) will not work in my environment. As others have reported,

the following errors occur when trying to perform a simple usbip.exe
-list <server_ip>.

 

>usbip -D --list 10.8.1.101

usbip dbg: usbip_network.c: 223 (tcp_connect ) trying 10.8.1.101 port
3240

usbip dbg: usbip_network.c: 243 (tcp_connect ) connected to
10.8.1.101:3240 - 10.8.1.101

usbip err: usbip_network.c: 121 (usbip_recv_op_common) recv op_common,
-1

usbip err:       usbip.c: 216 (query_exported_devices) recv op_common

usbip err:       usbip.c: 288 (show_exported_devices) query

 
Originally, I had thought the source code that was used to build the
latest binary was found here:

http://usbip.svn.sourceforge.net/viewvc/usbip/windows/tag/usbip_windows-
0.2.0.0/
 
But as Arjan has described to me..this is not the latest.  The latest
can be found (as mentioned above) under:
http://usbip.svn.sourceforge.net/viewvc/usbip/obsolete/linux/trunk/.
Since I had a problem with the latest, I built what was found under
http://usbip.svn.sourceforge.net/viewvc/usbip/windows/tag/usbip_windows-
0.2.0.0/ and added my own logic to read the usb.ids file to get vendor,
product, class and interface information displayed. (NOTE: Arjan says
this logic already resides in the latest source under the obsolete path,
but I did not know that at the time).   Hopefully this posting
enlightens others of where to find the source that was used to build the
binary that is available for download.  I was also hoping that others
who have downloaded the latest Windows binary can chime in and say
whether or not it works in their environment.  I have seen a few
postings with the same errors I am getting in my environment - but no
solutions.  My server side is comprised of the USBIP code as it exists
in the Linux v3.1-rc6 branch (which was what I am guessing the latest
available source as of about a week ago).  I did revert the #defines
that broke backward compatibility and I able to use this server code
with all older versions of the Windows client.   One last thing that I
am observing with the code I built from
http://usbip.svn.sourceforge.net/viewvc/usbip/windows/tag/usbip_windows-
0.2.0.0/  is that I am only able to connect 5 USB devices without a
problem Once I connect a 6th device the client hangs when trying to
perform a usbip.exe -list command.  I was hoping the latest Windows
client source would fix this problem...but I can't test it since the
usbip.exe -list command always throws the recv_op_common errors (as
listed above).

 

 



This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.