Nicolas Mailhot <[EMAIL PROTECTED]> writes: > Now it turns out I didn't do such a piss-poor of configuring my 2.5 > kernel, since the only option I could find that make a difference > was CONFIG_USB_DEBUG. When I accept flooding my system logs with > obscure usb incantations the system boots:(.
This is something I noticed while tracing down some memory corruption in my device driver. The CONFIG_USB_DEBUG option actually enables additional code paths and not just extra debug messages. Specifically, in the 2.4 tree hcd.c uses CONFIG_USB_DEBUG to set it's own DEBUG macro which is used to do "stuff that drivers shouldn't do, but which shouldn't cause problems in HCDs if they get it wrong." IMO, this should have a separate config option like CONFIG_USB_HARDENING with help text that says it is for developers who want to run their USB code through extra ringers. IMO, either hcd.c or the help text for CONFIG_USB_DEBUG is wrong and one of them needs to be fixed. -- (__) Doug Alcorn - Unix/Linux/Web Developing oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543 |_/ mailto:[EMAIL PROTECTED] http://www.lathi.net ------------------------------------------------------- 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
