On Tue, Sep 16, 2003 at 02:24:07PM -0700, David Brownell wrote: > Greg KH wrote: > >On Tue, Sep 16, 2003 at 07:53:45PM +0100, Daniel Drake wrote: > > > >No, for different reasons, the authors of these files did not want debug > >messages to be tied to CONFIG_USB_DEBUG. Traditionally CONFIG_USB_DEBUG > >only enabled debugging in the USB core code, although it looks like a > >few other drivers do tie their debugging messages to this setting > >(konicawc.c, usbnet.c, usbtest.c, and the usb-skeleton.c driver.) > > > >So I'm not going to take that part of the patch. > > I'd be interested in seeing some more standard hook for that then; > maybe a CONFIG_USB_DRIVER_DEBUG to enable logging extra low-volume > diagnostics when interesting faults are detected? > > We get better troubleshooting information from users when getting > it is just a build option, no apply-editor-to-source steps needed.
You get even more when you turn it into a load option, like all of the usb-serial drivers have. "modprobe foo debug=1" is much easier to tell people to do than to rebuild their distro kernel :) thanks, greg k-h ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
