On Wed, Jan 13, 2010 at 9:43 AM, Heasley, Seth <seth.heasley@xxxxxxxxx> wrote: >>> * some of lines of Intel chips do not separate AHCI into a separate PCI >>> ID rather legacy IDE interface. When an AHCI interface exists and >>> AHCI/IDE share the same PCI ID, we default to using AHCI. Thus, some of >>> those PCI ID matches in ahci.c's PCI table may not get caught by the >>> generic PCI class match at the end of the table. >>> >>> * the cost carrying redundant PCI IDs seems low, harmless, and >>> potentially helpful. >> >>It is helpful for the specific device IDs to show up in "modinfo ahci" and >>modules.pcimap. >> >>David > > This is the reason I was asked to start adding the AHCI DeviceIDs here. I'm not sure why exactly that is useful - or at least why it's useful enough to be worth the effort of patching the kernel for every new AHCI controller that gets released.. I looked at what the Windows msahci driver is doing, they're not listing any specific device IDs at all, they're just using the class code matching only. (Of course, they don't have to worry about devices in RAID mode, as those have to use vendor-specific drivers..) -- 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
