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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200805120024.27230.fox.box@gmail.com>
Date:	Mon, 12 May 2008 00:24:27 +0200
From:	Björn Krombholz <fox.box@...il.com>
To:	linux-pci@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH] PCI: enable nv_msi_ht_cap_quirk for ALi bridges (2.6.24 regression)

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@...il.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)
 {
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/