On Wed, Mar 03, 2004 at 10:45:24PM +0000, James Courtier-Dutton wrote:CONFIG_USB_DEBUG was enabled at the time, but made no difference.
When someone is writing a kernel module that uses the usb core, and one makes a call to the usb core that gets rejected for some reason. e.g. usb core returns -EINVAL. It would be nice if the usb core could printk a kernel message explaining which parameter was invalid.
Heh, but then we would bog down everything with a load of code that the normal, working kernel would not need :)
Have you tried enabling CONFIG_USB_DEBUG?
thanks,
greg k-h
Maybe if these printk's only happened if CONFIG_USB_DEBUG was set, everyone would be happy, with only kernel developers seeing the printk's but normal users not seeing them.
Cheers James
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
