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.

I recently was getting -EINVAL returned to some calls I made to usb_submit_urb(), and the only way I tracked down what was wrong, was by adding lots of printk's to the usb core so I could see at which point -EINVAL was being returned. It turned out to be "interval" not being set, but a simple printk message from usb core could have saved me a bit to time tracking this.

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

Reply via email to