[usbip-devel] Getting started - Device always Initializing

[David M. <dav...@gm...>]

Hello,

At the moment I have to use a 2.6.38 kernel (for an embedded ARM board), and am using the USBPI drivers found in staging. I have cross compiled the user utils using the following versions, and this aspect seems to work OK, in that I can build, install and run the resulting binaries:
	glib-2.18.4.tar.gz
	sysfsutils-2.1.0.tar.gz
	usbip-0.1.7.tar.gz

The client is a super minimal linux config which has no other HW access other than UART and a Timer. I have added generic USB support (but not the specific USB host controller for the board) and USBIP VHCI to the .config. Also have enabled USB HID devices.

I have tried attaching various HID devices I have laying about:
	* a Logitech wireless mouse/keyboard dongle (enumerates as a USB device with a mouse and kb endpoint) [sorry if I use incorrect usb terminology!]
	* A plain USB Microsoft optical mouse.
Both of these are listed fine by the client, but attempts to attach leave the virtual USB port as "Initialising", and lsusb only shows the LinuxFoundation (virtual?) root hub.

Is this a known problem with the version I have, or an expected side effect if I'm missing USB drivers in the client? Since it lists ok, it seems the server side is working fine.

Additionally - if I attempt to share my phone this way, it initialises OK and the phone appears in lsusb on the client. (I cannot mount it because that kernel does not (yet) have usb-mas storage enabled but thats another matter).

Are there quirks related to HID devices I should be aware of?

Thanks,
David M