All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <brice@myri.com>
To: linux-pci@atrey.karlin.mff.cuni.cz
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] Improve MSI detection v3
Date: Tue, 20 Jun 2006 22:31:05 -0400	[thread overview]
Message-ID: <20060621023104.GA16271@myri.com> (raw)

[PATCH 0/6] Improve MSI detection v3

Here's another set of patches to cleanup MSI detection.
There's only blacklisting (cleanup for non-PCI-E chipsets and
addition of HT cap checks).

#1 - Merge existing MSI disabling quirks
#2 - Rename PCI_CAP_ID_HT_IRQCONF to PCI_CAP_ID_HT
#3 - Blacklist PCI-E chipsets depending on Hypertransport MSI capabality
#4 - Factorize common MSI detection code from pci_enable_msi() and msix()
#5 - Stop inheriting bus flags and check root chipset bus flags instead
#6 - Drop pci_msi_quirk

Only #3 brings an important feature. The others are mostly cosmetic.
#1 defines a generic quirk to disable MSI. It will probably end up being
used for lots of MSI-broken chipset.

These patches are against 2.6.17-rc6-mm2.

Brice Goglin

             reply	other threads:[~2006-06-21  2:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21  2:31 Brice Goglin [this message]
2006-06-21  2:31 ` [PATCH 1/6] Merge existing MSI disabling quirks Brice Goglin
2006-06-21  2:32 ` [PATCH 2/6] Rename PCI_CAP_ID_HT_IRQCONF into PCI_CAP_ID_HT Brice Goglin
2006-06-21  2:32 ` [PATCH 3/6] Blacklist PCI-E chipsets depending on Hypertransport MSI capabality Brice Goglin
2006-06-22 13:56   ` [PATCH 3/6 v4] " Brice Goglin
2006-06-21  2:32 ` [PATCH 4/6] Factorize common MSI detection code from pci_enable_msi() and msix() Brice Goglin
2006-06-21  2:32 ` [PATCH 5/6] Stop inheriting bus flags and check root chipset bus flags instead Brice Goglin
2006-06-21  2:33 ` [PATCH 6/6] Drop pci_msi_quirk Brice Goglin

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=20060621023104.GA16271@myri.com \
    --to=brice@myri.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.