From: Dave Jones <davej@redhat.com>
To: Aleksey Gorelov <Aleksey_Gorelov@Phoenix.com>
Cc: Giancarlo Formicuccia <giancarlo.formicuccia@gmail.com>,
Greg KH <greg@kroah.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix incorrect Asus k7m irq router detection
Date: Wed, 27 Jul 2005 13:32:22 -0400 [thread overview]
Message-ID: <20050727173222.GD20938@redhat.com> (raw)
In-Reply-To: <0EF82802ABAA22479BC1CE8E2F60E8C33D2D00@scl-exch2k3.phoenix.com>
On Wed, Jul 27, 2005 at 10:10:35AM -0700, Aleksey Gorelov wrote:
> > > static __init int via_router_probe(struct irq_router *r,
> >struct pci_dev *router, u16 device)
> > > {
> > > /* FIXME: We should move some of the quirk fixup stuff here */
> > > +
> > > + if (router->device == PCI_DEVICE_ID_VIA_82C686 &&
> > > + device == PCI_DEVICE_ID_VIA_82C586_0) {
> > > + /* Asus k7m bios wrongly reports 82C686A as
> >586-compatible */
> > > + device = PCI_DEVICE_ID_VIA_82C686;
> > > + }
> > > +
> > > switch(device)
> > > {
> > > case PCI_DEVICE_ID_VIA_82C586_0:
> >
> >If this really is a problem with that board, it should have a DMI entry
> >for that board alone, not for every VIA chipset that uses the
> >586/686 combo,
> >as I'm fairly certain there are some that legitimately use
> >this combination,
> >and the patch above will force them all to be reported as 82C686's.
>
> How can they use it legitimately if 586 & 686 routers are not
> programming register compatible ? Any board which reports that 686 is
> compatible with 586 will have that issue.
Actually now that I've woken up properly, your patch looks ok to me.
For some reason I was thinking we were comparing a north and south
bridge here.
Dave
next parent reply other threads:[~2005-07-27 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0EF82802ABAA22479BC1CE8E2F60E8C33D2D00@scl-exch2k3.phoenix.com>
2005-07-27 17:32 ` Dave Jones [this message]
2005-07-27 8:16 [PATCH] Fix incorrect Asus k7m irq router detection Giancarlo Formicuccia
2005-07-27 16:48 ` Dave Jones
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=20050727173222.GD20938@redhat.com \
--to=davej@redhat.com \
--cc=Aleksey_Gorelov@Phoenix.com \
--cc=akpm@osdl.org \
--cc=giancarlo.formicuccia@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@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