From: Chris Wright <chrisw@osdl.org>
To: Ruediger Scholz <rscholz@hrzpub.tu-darmstadt.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: irq 9: nobody cared!
Date: Mon, 22 Sep 2003 10:30:28 -0700 [thread overview]
Message-ID: <20030922103028.A18616@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <3F6EBEC7.7050204@hrzpub.tu-darmstadt.de>; from rscholz@hrzpub.tu-darmstadt.de on Mon, Sep 22, 2003 at 11:20:07AM +0200
* Ruediger Scholz (rscholz@hrzpub.tu-darmstadt.de) wrote:
> Hi there!
>
> I own a P4 with SIS 645DX-Chipset, so I tried kernel 2.6.0-test5-mm3 in
> order to get a working IOAPIC mode with the SIS Chipset. When I boot the
<snip>
> If I use the boot param "pci=noacpi" then everything works fine, even sound.
Can you try this patch against 2.6.0-test5-mm3? PCI IRQ routing is
broken in some circumstances with ACPI.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
--- 2.6.0-test5-mm3/drivers/acpi/pci_link.c~acpi_pci_irq_fix 2003-09-22 10:00:16.000000000 -0700
+++ 2.6.0-test5-mm3/drivers/acpi/pci_link.c 2003-09-22 10:10:06.000000000 -0700
@@ -500,15 +500,15 @@ static int acpi_pci_link_allocate(struct
irq = link->irq.active;
} else {
irq = link->irq.possible[0];
- }
- /*
- * Select the best IRQ. This is done in reverse to promote
- * the use of IRQs 9, 10, 11, and >15.
- */
- for (i=(link->irq.possible_count-1); i>0; i--) {
- if (acpi_irq_penalty[irq] > acpi_irq_penalty[link->irq.possible[i]])
- irq = link->irq.possible[i];
+ /*
+ * Select the best IRQ. This is done in reverse to promote
+ * the use of IRQs 9, 10, 11, and >15.
+ */
+ for (i=(link->irq.possible_count-1); i>0; i--) {
+ if (acpi_irq_penalty[irq] > acpi_irq_penalty[link->irq.possible[i]])
+ irq = link->irq.possible[i];
+ }
}
/* Attempt to enable the link device at this IRQ. */
next prev parent reply other threads:[~2003-09-22 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 9:20 Ruediger Scholz
2003-09-22 17:30 ` Chris Wright [this message]
2003-09-22 20:11 ` Ruediger Scholz
2003-09-22 20:56 ` Chris Wright
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=20030922103028.A18616@osdlab.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rscholz@hrzpub.tu-darmstadt.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
all inboxes | Powered by JetHome®