At the moment, the 2.6.x USB core is /very/ noisy, giving KERN_WARNING level messages for all failed usbfs bulk transactions (in addition to returning the error), and for all usb transfer timeouts (in addition to returning the error).
Is it noisier than 2.4 in such ways?
This results in two messages to syslog (and often the console) for all bulk transfer timeouts, which seems rather excessive for information which /may/ be useful when attempting to debug things, but which the calling program has every chance to deal with itself.
It also gives KERN_INFO level messages for all connections and disconnections, and while this may have more value then the debugging messages above, it can still get somewhat extensive for cases of heavy hot-plugging.
In both cases the messages are unconditional. Would it be reasonable for these messages to be controlled by some of the various debugging settings?
I'd think most of those should be KERN_DEBUG message, which should already be turned on/off by CONFIG_USB_DEBUG.
- Dave
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
