linux-kernel - [PATCH] PCI: AMD 813x B2 devices do not need quirk

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]

Date:	Thu, 26 Feb 2009 10:46:48 -0800
From:	Greg KH <greg@...ah.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Stefan Assmann <sassmann@...ell.com>,
	Jamie Wellnitz <Jamie.Wellnitz@...lex.com>, stable@...nel.org,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] PCI: AMD 813x B2 devices do not need quirk

From: Stefan Assmann <sassmann@...ell.com>

Turns out that the new AMD 813x devices do not need the
quirk_disable_amd_813x_boot_interrupt quirk to be run on them, if it is,
no interrupts are seen on the PCI-X adapter.

From: Stefan Assmann <sassmann@...ell.com>
Reported-by: Jamie Wellnitz <Jamie.Wellnitz@...lex.com>
Tested-by: Jamie Wellnitz <Jamie.Wellnitz@...lex.com>
Cc: stable <stable@...nel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>

---
 drivers/pci/quirks.c |    3 +++
 1 file changed, 3 insertions(+)

--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -1554,6 +1554,7 @@ DECLARE_PCI_FIXUP_RESUME(PCI_VENDOR_ID_S
  */
 #define AMD_813X_MISC			0x40
 #define AMD_813X_NOIOAMODE		(1<<0)
+#define AMD_813X_REV_B2			0x13
 
 static void quirk_disable_amd_813x_boot_interrupt(struct pci_dev *dev)
 {
@@ -1561,6 +1562,8 @@ static void quirk_disable_amd_813x_boot_
 
 	if (noioapicquirk)
 		return;
+	if (dev->revision == AMD_813X_REV_B2)
+		return;
 
 	pci_read_config_dword(dev, AMD_813X_MISC, &pci_config_dword);
 	pci_config_dword &= ~AMD_813X_NOIOAMODE;
--
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/