[PATCH] PCI: enable nv_msi_ht_cap_quirk for ALi bridges (2.6.24 regression)

[PATCH] PCI: enable nv_msi_ht_cap_quirk for ALi bridges (2.6.24 regression)

[Björn Krombholz]

This applies the NVidia MSI enabled flag for HT capable devices quirk
to ALi bridges as well.

As described in more detail in
http://bugzilla.kernel.org/show_bug.cgi?id=10667 this is required for
my board which is using an nForce 3 250Gb chipset with an ALi M1695
northbridge.

It fixes a regression introduced in 2.6.24 that made the internal NIC
of the board unusable (MSI initialisation of the NIC but disabled MSI
on the northbridge devices.

Signed-off-by: Björn Krombholz <fox.box@gmail.com>
---

The patch is trivial but Andrew asked me to send it to the list(s). As
this is my first report of this kind, please give me a hint on any
formal mistakes.

--- drivers/pci/quirks.c.orig   2008-05-11 17:16:31.000000000 +0200
+++ drivers/pci/quirks.c        2008-05-11 04:17:38.371510170 +0200
@@ -1815,6 +1815,7 @@ static void __devinit nv_msi_ht_cap_quir
        }
 }
 DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_NVIDIA, PCI_ANY_ID, nv_msi_ht_cap_quirk);
+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AL, PCI_ANY_ID, nv_msi_ht_cap_quirk);

 static void __devinit quirk_msi_intx_disable_bug(struct pci_dev *dev)
 {

Re: [PATCH] PCI: enable nv_msi_ht_cap_quirk for ALi bridges (2.6.24 regression)

[Jesse Barnes]

On Sunday, May 11, 2008 3:24 pm Björn Krombholz wrote:
> This applies the NVidia MSI enabled flag for HT capable devices quirk
> to ALi bridges as well.
>
> As described in more detail in
> http://bugzilla.kernel.org/show_bug.cgi?id=10667 this is required for
> my board which is using an nForce 3 250Gb chipset with an ALi M1695
> northbridge.
>
> It fixes a regression introduced in 2.6.24 that made the internal NIC
> of the board unusable (MSI initialisation of the NIC but disabled MSI
> on the northbridge devices.
>
> Signed-off-by: Björn Krombholz <fox.box@gmail.com>
> ---
>
> The patch is trivial but Andrew asked me to send it to the list(s). As
> this is my first report of this kind, please give me a hint on any
> formal mistakes.

Applied to the 'for-linus' tree.  Thanks.

Jesse