linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Stian Jordet <liste@jordet.nu>
Cc: Olaf Hering <olh@suse.de>, Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bogus VIA IRQ fixup in drivers/pci/quirks.c
Date: Tue, 27 Sep 2005 07:42:23 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0509270734340.3308@g5.osdl.org> (raw)
In-Reply-To: <1127831274.433956ea35992@webmail.jordet.nu>



On Tue, 27 Sep 2005, Stian Jordet wrote:
> 
> He wanted me to test 2.6.12-rc2-mm3, which actually disabled irq9 as
> well at boottime. After some debugging, he made this patch, which made
> irq 9 work as normal again for me. Please don't back this patch out,
> without at least re-looking at my system.

Well, looking at your messages, I bet that the appended patch works for 
you, since your irq's are all in the legacy range.

It is also conceptually closer to what the code _used_ to be (it used to
say "if we have an IO-APIC, don't do this", now it says "if this irq is
bound to an IO-APIC, don't do this")

Whether this will matter to Olaf, I don't know, but the old code was 
definitely just writing random bits for the IO-APIC case afaik.

		Linus

---
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -546,7 +546,10 @@ static void quirk_via_irq(struct pci_dev
 {
 	u8 irq, new_irq;
 
-	new_irq = dev->irq & 0xf;
+	new_irq = dev->irq;
+	if (!new_irq || new_irq >= 15)
+		return;
+
 	pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &irq);
 	if (new_irq != irq) {
 		printk(KERN_INFO "PCI: Via IRQ fixup for %s, from %d to %d\n",

  reply	other threads:[~2005-09-27 14:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 18:44 bogus VIA IRQ fixup in drivers/pci/quirks.c Olaf Hering
2005-09-26 21:59 ` Linus Torvalds
2005-09-27  6:09   ` Olaf Hering
2005-09-27 12:29   ` Olaf Hering
2005-09-27 14:27   ` Stian Jordet
2005-09-27 14:42     ` Linus Torvalds [this message]
2005-09-27 21:19       ` Stian Jordet
2005-09-27 21:36         ` Linus Torvalds
2005-09-27 21:48           ` Stian Jordet
2005-09-27 22:58             ` Linus Torvalds
2005-09-28  7:28               ` Matthieu CASTET
2005-09-28 15:32                 ` Matthieu CASTET
2005-09-27 21:52           ` Stian Jordet

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=Pine.LNX.4.58.0509270734340.3308@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@osdl.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liste@jordet.nu \
    --cc=olh@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).