From: Brad H. <bh...@bi...> - 2003-07-23 12:34:31
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 23 Jul 2003 19:06 pm, Juergen Veith wrote: > My report descriptor describes a input and a output report with raw data = as > well as a feature report using control transfers. Depending on the number > of anounced endpoints, windows makes the access with interrupt transfer > oder using set/get report request by control transfers. Becouse of > efficiency I currently use 64 byte telegram with Interrupt-In and > Interrupt-out endpoint each. The full speed device has 2 more endpoints > what can work with bulk, but currently I cannot access this by HID. It would probably help to know what the device is. As an absolute minimum,= =20 seeing the HID descriptor (at least the Application) from lsusb or from you= r=20 source code would help. > The main application uses windows API and works well with wine. Up on this > point I did my test with modifying the usbhidioc2 example from www.lvr.com > what is accessing the HID driver for preparsed data. If I plug in the > device to a Linux machine, the enumeration seems to be ok and usbview > displays the device in red color (no driver available -in comparison to > windows, the int-In endpoint is not polled). This point I am quite unsure > what to do and on what level of the host stack will be the best to access > the device that application will work with both, Linux and Win. Is usblib > the right attempt or can somebody recommend to access any of the hid driv= er > interfaces driver for Linux in case of a HID ? libusb can probably do this, but hiddev might be a better bet. Out isn't=20 really good on Linux though - we'd need substantial design information to=20 tell if that is going to be a big problem. See http://www.frogmouth.net/hid-doco/examples/hiddev-misc/dump-events.c fo= r=20 some sample code. Brad =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/HoB7W6pHgIdAuOMRAhMAAJwOA1OjJQ0ljYG682oRS9PpiY+2XQCfadZ/ g5mbrL9CIyRGysnd4rnY3xk=3D =3Dgztw =2D----END PGP SIGNATURE----- |