On Sat, Jan 14, 2006 at 02:15:51PM -0800, Brian A. Stumm wrote: > On Sat, 14 Jan 2006, Vojtech Pavlik wrote: > > > On Sat, Jan 14, 2006 at 01:49:41PM -0500, Alan Stern wrote: > > > On Sat, 14 Jan 2006, Brian A. Stumm wrote: > > > > > > > Still no go in 2.6.15 > > > > > > It could be that your device doesn't like sending the initial reports. > > > You can try editing the source file drivers/usb/input/hid-core.c. In the > > > hid_probe() routine, comment out the call to hid_init_reports(). Windows > > > doesn't do this; it's a major difference between the two OSes. > > > > Also Windows does SET_IDLE before GET_REPORT_DESCRIPTOR. I've seen at > > least one device which doesn't like the opposite order (which is how > > Linux does it). > > What else might happen in different order for windows vs linux? Tried both > of these suggestions but to no avail. Also, is usbmouse.c affected by > these tests? I was assuming no and using the usbhid driver. usbmouse.c tries not to talk to the device more than necessary exactly to work in all conditions, so it doesn't set the idle time not ask for the descriptor, assuming boot protocol layout. If usbmouse.c doesn't work, something is wrong in the usb core and/or hcd parts, or the mouse requires these calls to work, which would be hard to believe.
-- Vojtech Pavlik SuSE Labs, SuSE CR ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
