Hello, Jon. Jon Masters wrote: >> Dunno much about sb600 but ahci and pata_atiixp are probably using >> separate IO regions && separate PCI functions. > > Yeah. I actually thought about this whole issue a bit more recently - > things like SATA/PATA interference when you've got a part that emulates > legacy functionality so can appear as two different kinds of device - > since I don't think my brain was really bothering to listen before. > Words were going in, but it chose to ignore what was being said. Dunno about the history. Oh well, as long as the problem gets fixed. > Only thing that comes to mind is in-driver logic/driver loading ordering > hack combinations. At least if you've got loadable modules, you've got a > fighting chance of fixing this kind of situation - built-in and you need > to fight with whatever ordering exists in the array of init functions. Not sure whether it applies to sb600 directly but libata policy for this type of situation is.. * always prefer the native / more capable (read ahci) interface over emulated SFF interface. * program the device and update PCI header using a PCI quirk such that module loading order or BIOS setting doesn't affect which driver gets attached. Note that if the controller needs to programmed in specific way, the quirk also needs to be called during resume. In this case, the function for SFF interface can simply be disabled. Please take a look at the JMB quirk in drivers/pci/quirks.c in the latest libata-dev#upstream tree for details. Thanks. -- tejun - 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
