PCI: quirk dma_alias_devfn for HighPoint RocketRaid 642L (Marvell 9235)
PATCH 1/1 PCI: quirk dma_alias_devfn for HighPoint RocketRaid 642L (Marvell 9235)
This vendor has similar boards based on the same Marvell 88SE9235 chipset, but this patch was only tested with the 642L.
Tested on ASUS Sabertooth 990FX (AMD).
If you listen to the vendor support stating:
Dear Customer,
Sorry about that.
Currently all our products' software package don't support IOMMU and we don't have plan to support that.
... you'll think you also wasted your money, but it turns out that you just lost a few hours of your valuable time talking to their support, because the good people from the Internet made their board work, with the regular AHCI driver, and even with IOMMU. Nice!
--- drivers/pci/quirks.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/pci/quirks.c +2 -0
@@ -3380,6 +3380,8 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x91a0,/* https://bugzilla.kernel.org/show_bug.cgi?id=42679#c49 */ DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_MARVELL_EXT ,0x9230 , quirk_dma_func1_alias); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_TTI ,0x0642 , + quirk_dma_func1_alias);/* https://bugs.gentoo.org/show_bug.cgi?id=497630 */ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_JMICRON, PCI_DEVICE_ID_JMICRON_JMB388_ESD,
Signature · 1 line
2.0.0
Quoted 12 lines · Jérôme Carretero
This vendor has similar boards based on the same Marvell 88SE9235 chipset, but this patch was only tested with the 642L.
Tested on ASUS Sabertooth 990FX (AMD).
If you listen to the vendor support stating:
Dear Customer,
Sorry about that.
Currently all our products' software package don't support IOMMU and we don't have plan to support that.
Quoted 7 lines
... you'll think you also wasted your money, but it turns out that you just lost a few hours of your valuable time talking to their support, because the good people from the Internet made their board work, with the regular AHCI driver, and even with IOMMU. Nice!
Signed-off-by Jérôme Carretero <[email protected]>
Quoted 17 lines
--- drivers/pci/quirks.c | 2 ++ 1 file changed, 2 insertions(+)drivers/pci/quirks.c +2
-0@@ -3380,6 +3380,8 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x91a0,/* https://bugzilla.kernel.org/show_bug.cgi?id=42679#c49 */ DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_MARVELL_EXT ,0x9230 , quirk_dma_func1_alias); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_TTI ,0x0642 , + quirk_dma_func1_alias);/* https://bugs.gentoo.org/show_bug.cgi?id=497630 */ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_JMICRON, PCI_DEVICE_ID_JMICRON_JMB388_ESD,
Bjorn Helgaas
maintainerQuoted 12 lines · Jérôme Carretero
This vendor has similar boards based on the same Marvell 88SE9235 chipset, but this patch was only tested with the 642L.
Tested on ASUS Sabertooth 990FX (AMD).
If you listen to the vendor support stating:
Dear Customer,
Sorry about that.
Currently all our products' software package don't support IOMMU and we don't have plan to support that.
Quoted 7 lines
... you'll think you also wasted your money, but it turns out that you just lost a few hours of your valuable time talking to their support, because the good people from the Internet made their board work, with the regular AHCI driver, and even with IOMMU. Nice!
Signed-off-by Jérôme Carretero <[email protected]>
Applied with Alex's ack to pci/iommu for v3.16, thanks!
Note that I only have the PCI parts here. There are several IOMMU patches required in addition, and I haven't heard the fate of those.
Quoted 25 lines
--- drivers/pci/quirks.c | 2 ++ 1 file changed, 2 insertions(+)drivers/pci/quirks.c +2
-0@@ -3380,6 +3380,8 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x91a0,/* https://bugzilla.kernel.org/show_bug.cgi?id=42679#c49 */ DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_MARVELL_EXT ,0x9230 , quirk_dma_func1_alias); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_TTI ,0x0642 , + quirk_dma_func1_alias);/* https://bugs.gentoo.org/show_bug.cgi?id=497630 */ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_JMICRON, PCI_DEVICE_ID_JMICRON_JMB388_ESD,Signature · 7 lines
2.0.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/