David> I'm not sure that if the HID driver were to pass a null David> buffer pointer, it would be caught anywhere.
OK, I'll try to find some time to trace the I/O MMU calls to see if something isn't kosher at that level. Is there a good way of getting a relatively high-level of tracing in the USB subsystem that would some me what's going on between the HID and the core USB level?
Most of that story is just submitting and completing URBs.
I'd either try changing the spots in drivers/usb/core/hcd.c marked as appropriate for generic MONITOR_URB hooks (printk if it's your HID device, maybe), or manually turn on whatever HCD-specific hooks exist (maybe use a VERBOSE message level).
Such a thing wasn't possible in 2.4 since there were too many different bizarre (and sometimes buggy) ways for URBs to return to the usb device drivers and get implicitly resubmitted.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
