All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: long <tlnguyen@snoqualmie.dp.intel.com>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
	jun.nakajima@intel.com, tom.l.nguyen@intel.com,
	zwane@linuxpower.ca
Subject: Re: MSI fix for buggy PCI/PCI-X hardware
Date: Tue, 9 Sep 2003 14:41:22 -0400	[thread overview]
Message-ID: <20030909184122.GA3635@gtf.org> (raw)
In-Reply-To: <200309091539.h89FdbfK023026@snoqualmie.dp.intel.com>

On Tue, Sep 09, 2003 at 08:39:37AM -0700, long wrote:
> The proposed solution is to provide a new API, named "int 
> disable_msi(struct pci_dev *dev)", to allow IHV's who have 
> shipped PCI/PCI-X hardware that does not work in MSI mode to update 
> their software drivers to request the kernel to switch the 
> interrupt mode from MSI mode back to IRQ pin-assertion mode. 

No need for a new API.  We have drivers/pci/quirk.c where we add PCI
devices with known bugs.  If there is commonality of the bugs across
hardware, we can easily add a common "quirk" which fixes the situation.

Individual drivers shouldn't need to bother with this, really.

As an aside, if you need to blacklist certain _systems_ rather than
certain PCI devices, you should either modify drivers/pci/quirks.c or
arch/i386/kernel/dmi_scan.c.

	Jeff




  reply	other threads:[~2003-09-09 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 15:39 MSI fix for buggy PCI/PCI-X hardware long
2003-09-09 18:41 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-09 22:14 Nakajima, Jun
2003-09-09 22:52 ` Jeff Garzik
2003-09-10 21:31   ` Zwane Mwaikambo
2003-09-10  1:26 Nakajima, Jun

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=20030909184122.GA3635@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=greg@kroah.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tlnguyen@snoqualmie.dp.intel.com \
    --cc=tom.l.nguyen@intel.com \
    --cc=zwane@linuxpower.ca \
    /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.