Hello, I have written in the past in regards to a simulating a mouse using a PXA255 board and the GadgetFS kernel functionality. I have successfully modified the usb.c example to fake a Windows host into thinking the PXA is a Logitech mouse with LRM buttons and pointing functionality.
My question lies in the mouse wheel. Upon searching usb.org and google, I have found that the mouse wheel functionality is described to the host in the report descriptor by adding 0x09, 0x38 to define the wheel and then define that an additional packet with this data will be added after the X and Y location data (making for a 4 byte total packet - the first being button status, then X, Y, wheel data) . However, when I include the byte of wheel information, the functionality of the simulation as a whole is completely disabled. If I define the report to have 3 bytes and a null fourth byte, the simulation works perfectly. Does anyone have any insight into what the problem may be? The gadget driver is still correctly writing the bytes to the fd when the wheel byte is included, so I don't believe this is a gadget debug issue. Or if anyone knows the bit by bit byte description for a Logitech optical wheel mouse, could you forward that on? My only thought is that perhaps the data is in the wrong format, so while it is being correctly written to the fd, the host is interpreting it incorrectly. Also, if anyone has any experience with simulating the wheel functionality in general, that may be of help, I'd appreciate it! Thanks, Colleen ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
