On Monday 04 December 2006 6:23 pm, José A. Cañizo wrote: > Seeing that > you added a module parameter, I assume that there is no easy way of > having the module notice by itself when this must be done; I imagine > there is no way of telling whether they are real or bogus > messages.
YOU can tell ... e.g. by knowing that port has nothing connected, and concluding that such messages must accordingly be bogus. The kernel can't know that, however. > Also, if the problem is in the way the port is connected, > then one cannot just make a list of problematic hardware, right? Collecting a list of bogus hardware designs is problematic, but it'd make sense to have a framework into which that stuff plugs. DMI tables might help; I'd expect such stuff to be coupled to a flakey board design in most cases. But when it's a manufacturing problem, the DMI tables would not help identify flakey boards. - Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
