From: Greg KH <greg@kroah.com>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: Jose Alberto Reguero <jareguero@telefonica.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Problem with atl1 and msi in kernel 2.6.22-rc3
Date: Wed, 30 May 2007 15:07:39 -0700 [thread overview]
Message-ID: <20070530220739.GA26408@kroah.com> (raw)
In-Reply-To: <20070530064711.570162f1@osprey.hogchain.net>
On Wed, May 30, 2007 at 06:47:11AM -0500, Jay Cliburn wrote:
> On Wed, 30 May 2007 02:00:25 +0200
> Jose Alberto Reguero <jareguero@telefonica.net> wrote:
>
> > I have problems with a M2V motherboard and atl1 driver with msi and
> > kernel 2.6.22-rc3. With kernel 2.6.21 I had no problems.
> > I must add in drivers/pci/quirks.c (line 1723):
> >
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RS480,
> > quirk_disable_msi);
> > +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_VIA, 0xe238,
> > quirk_disable_msi);
> >
> > to disable msi in the atl1.
>
> See http://bugzilla.kernel.org/show_bug.cgi?id=8472.
>
> A more general solution is to disable MSI for the VIA VT3351 (used by
> the Asus M2V). I attempted to do this in the -stable tree with
> http://lkml.org/lkml/2007/5/26/167, but it was shot down because the
> patch isn't upstream yet.
>
> Unfortunately, I can't submit it upstream because the enabling
> patch hasn't yet been applied upstream by the PCI maintainer. My
> request for info on the status of the patch went unanswered.
> http://lkml.org/lkml/2007/5/19/74
Sorry, I'm catching up on PCI stuff right now (am traveling in Tokyo
right now, gotta love jet lag...)
thanks for your patience.
greg k-h
next prev parent reply other threads:[~2007-05-30 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705300200.25412.jareguero@telefonica.net>
2007-05-30 11:47 ` Jay Cliburn
2007-05-30 22:07 ` Greg KH [this message]
2007-05-31 1:13 ` Jay Cliburn
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=20070530220739.GA26408@kroah.com \
--to=greg@kroah.com \
--cc=jacliburn@bellsouth.net \
--cc=jareguero@telefonica.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®