public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Giancarlo Formicuccia <giancarlo.formicuccia@gmail.com>
Cc: Greg KH <greg@kroah.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org,
	Aleksey Gorelov <Aleksey_Gorelov@phoenix.com>
Subject: Re: [PATCH] Fix incorrect Asus k7m irq router detection
Date: Wed, 27 Jul 2005 12:48:33 -0400	[thread overview]
Message-ID: <20050727164833.GB20938@redhat.com> (raw)
In-Reply-To: <200507271016.30447.giancarlo.formicuccia@gmail.com>

On Wed, Jul 27, 2005 at 10:16:30AM +0200, Giancarlo Formicuccia wrote:

 > this patch:
 > http://marc.theaimsgroup.com/?l=bk-commits-head&m=111955644929114&w=2
 > uncovered a k7m bios bug, where the VT82C686A router is reported as
 > being "586-compatible". The two chips have different pirq mapping, so
 > this leads to "irq routing conflict" on many pci devices.
 > 
 > The suggested fix was discussed with Aleksey Gorelov, who helped me
 > to identify the problem as a probable bios bug.
 > 
 > Patch for 2.6.13-git4.
 > 
 > Signed-off-by: Giancarlo Formicuccia <giancarlo.formicuccia@gmail.com>
 > 
 > --- linux-2.6.13-rc3-git4/arch/i386/pci/irq.c.org	2005-07-27 08:58:05.000000000 +0200
 > +++ linux-2.6.13-rc3-git4/arch/i386/pci/irq.c	2005-07-27 08:59:29.000000000 +0200
 > @@ -550,6 +550,13 @@
 >  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.

		Dave

  reply	other threads:[~2005-07-27 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27  8:16 [PATCH] Fix incorrect Asus k7m irq router detection Giancarlo Formicuccia
2005-07-27 16:48 ` Dave Jones [this message]
     [not found] <0EF82802ABAA22479BC1CE8E2F60E8C33D2D00@scl-exch2k3.phoenix.com>
2005-07-27 17:32 ` 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=20050727164833.GB20938@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