On Mon, May 09, 2011 at 09:36:21AM -0700, Andy Ross wrote: > On 05/09/2011 09:24 AM, Greg KH wrote: > > Ick. > > Yeah, agreed. This at least was something I knew how to do. > > Really, I was half hoping someone would pipe up with a known issue and > an existing fix. :) "Fix the BIOS" :) > I'll see about trying to find the right BIOS people, but I have > minimal visibility there: this is a device that's already in the > market, I'm just chasing MeeGo issues on it. BIOSes can be updated, right? > > At worse case, could we trigger off of known DMI strings for the > > broken machines? > > This sounds good. The code in question is a PCI quirk; is the DMI > info available at that point? I'll investigate. Well the PCI data is there, so DMI is also around, you could trigger off of a known PCI id on the bridge if needed as well. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
