public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Björn Krombholz" <fox.box@gmail.com>
To: linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] PCI: enable nv_msi_ht_cap_quirk for ALi bridges (2.6.24 regression)
Date: Mon, 12 May 2008 00:24:27 +0200	[thread overview]
Message-ID: <200805120024.27230.fox.box@gmail.com> (raw)

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)
 {

             reply	other threads:[~2008-05-11 22:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-11 22:24 Björn Krombholz [this message]
2008-05-13  0:24 ` [PATCH] PCI: enable nv_msi_ht_cap_quirk for ALi bridges (2.6.24 regression) Jesse Barnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200805120024.27230.fox.box@gmail.com \
    --to=fox.box@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox