On Sat, Feb 13, 2010 at 5:02 PM, Jeff Garzik <jeff@xxxxxxxxxx> wrote: >>>> Mike, can you test this out and make sure this resolves the problem for >>>> you? >>> >>> Sigh... we never did hear back from Mike or NVIDIA on this one, did we? >>> I've been watching for a response, and haven't seen one to date. >> >> No, I haven't seen a response. It's pretty apparent it should fix the >> problem based on earlier testing, but it would be nice to find out for >> sure which chipsets this affects. > > Yep, that's my main concern... being overly aggressive and zapping it on > all NVIDIA chipsets, even future ones. I'm thinking if we don't hear any more specifics on the problem from NVIDIA or someone otherwise knowledgeable Real Soon Now we should likely just merge this patch. MCP79 is a fairly new chipset and it's likely a good assumption that the older NVIDIA AHCI chipsets would have the same issue. It's possible that some of the newer chipsets do or will fix the problem, but we can address that at a later date - the auto-activate optimization is pretty minor and not worth breaking things if there's doubt of it working on these controllers.. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
