Hi, On Sun, Sep 25, 2011 at 8:03 AM, Tejun Heo <htejun@xxxxxxxxx> wrote: > Sure I can do that but it would be better if you can revise your > patch. Please take a look at how different ops are mapped to > different device IDs. You just need to create another variant to be > mapped to the problematic device IDs. OK， I will do it. > >> On Sat, Sep 24, 2011 at 12:28 PM, Heasley, Seth <seth.heasley@xxxxxxxxx> wrote: >> >>Have we successfully localized the problem to SNB? If so, great. >> > >> > No, we haven't. I've reproduced the issue on two newer Intel chipsets. In > IDE mode, ATAPI just isn't working on SATA3 ports. With the provided >> > patch, the issue is resolved. At what cost, I can't say. But if a patch will >> > go in for the 6 Series, we need to apply it to the other platforms as well. I > can provide the DeviceIDs. >> Seth, could you provide the DeviceIDs so that we can make a quirk for them now? >> I have seen someone reported the same problem on the device with >> pci device id of 0x1c01[1]. I have asked them to test the patch but without >> any response, so I had to not include the dev id in the patch. > > Developing partial blacklist w/o knowing what's going on is messy. If > we discover that something wasn't quite what we suspected it was and > had to revise, it'll be tricky to verify whicn ones need to remain. > Alan, can someone from intel verify the issue? Is there an errata we > can look at? thanks, --- Ming Lei -- 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
