File ahci.c contains the following definitions:
389 /* Marvell */
390 { PCI_VDEVICE(MARVELL, 0x6145), board_ahci_mv }, /* 6145 */
391 { PCI_VDEVICE(MARVELL, 0x6121), board_ahci_mv }, /* 6121 */
392 { PCI_DEVICE(0x1b4b, 0x9123),
393 .class = PCI_CLASS_STORAGE_SATA_AHCI,
394 .class_mask = 0xffffff,
395 .driver_data = board_ahci_yes_fbs }, /* 88se9128 */
396 { PCI_DEVICE(0x1b4b, 0x9125),
397 .driver_data = board_ahci_yes_fbs }, /* 88se9125 */
398 { PCI_DEVICE(0x1b4b, 0x917a),
399 .driver_data = board_ahci_yes_fbs }, /* 88se9172 */
400 { PCI_DEVICE(0x1b4b, 0x9192),
401 .driver_data = board_ahci_yes_fbs }, /* 88se9172 on some Gigabyte */
402 { PCI_DEVICE(0x1b4b, 0x91a3),
403 .driver_data = board_ahci_yes_fbs },
As far as I can tell from reading, 88se9123 and 88se9128 are each numbered to match their names. This suggests replacing one declaration with an incorrect comment by two new declarations:
{ PCI_DEVICE(0x1b4b, 0x9123),
.class = PCI_CLASS_STORAGE_SATA_AHCI,
.class_mask = 0xffffff,
.driver_data = board_ahci_yes_fbs }, /* 88se9123 */
{ PCI_DEVICE(0x1b4b, 0x9128),
.class = PCI_CLASS_STORAGE_SATA_AHCI,
.class_mask = 0xffffff,
.driver_data = board_ahci_yes_fbs }, /* 88se9128 */
A separate question is: Does anyone know if the ahci driver would work with the RocketRaid 644's 88se9128 chip? (For comparison, someone added the RocketRaid 2722's identifiers to the mvsas driver but the driver never recognized my SATA HDDs.)
--
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
