On Fri, Jan 26, 2007 at 03:13:04PM -0800, Greg KH wrote: > On Fri, Jan 26, 2007 at 02:26:21PM +0100, Oliver Neukum wrote: > > Hi, > > > > this is the newest version of the patch to introduce a blacklist. > > > > - It handles autosuspend oddities and problems with string descriptors > > - It exports the detected quirks through sysfs > > > > It compiles and detects quirky devices. > > Here's a revised patch based on yours. I used the existing structure we > have for describing usb devices, as it can handle any type we want to > throw at it. This also lets us re-use the logic of matching an id to a > device.
But it turns out that we haven't read this info by the time we were calling the quirk table test... Do we think we are going to need to know this kind of information that early in the process, or can we wait until the descriptor is fully read in? I'm believing that we can wait, as we haven't had a problem yet... thanks, greg k-h ------------------------------------------------------------------------- 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
