public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cory Bell <cory.bell@usa.net>
To: Pavel Machek <pavel@suse.cz>
Cc: John Clemens <john@deater.net>,
	Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
	linux-kernel@vger.kernel.org
Subject: Re: IRQ Routing Problem on ALi Chipset Laptop (HP Pavilion N5425)
Date: 08 Dec 2001 21:37:31 -0800	[thread overview]
Message-ID: <1007876254.17062.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20011207213313.A176@elf.ucw.cz>
In-Reply-To: <Pine.LNX.4.33.0112060938340.32381-100000@pianoman.cluster.toy> <1007685691.6675.1.camel@localhost.localdomain>  <20011207213313.A176@elf.ucw.cz>

On Fri, 2001-12-07 at 12:33, Pavel Machek wrote:

> Hey, this gross hack fixed USB on HP OmniBook xe3. Good! (Perhaps you
> know what interrupt is right for maestro3, also on omnibook? ;-).

On my Pavilion (and the other 5400's as far as I can tell), maestro's on
irq 5. Wanna send me a "dump_pirq" and a "lspci -vvvxxx"? Could you try
the patch below (inspired by/stolen from Kai Germaschewski)? Also, the
newest acpi patch will print out the acpi irq routing table - might have
your info. You can tell if the patch below had any effect because it
will say it ASSIGNED IRQ XX instead of FOUND.

I believe the Omnibook XEs and the Pavilion N5400's are very similar
hardware. Several of the drivers I've seen on HP's website appear to
apply to both. If you want to help get the BIOS updated (the root cause,
IMHO), please call HP support and reference case number 1429683616 (that
9 may be a 4 - my handwriting is horrible). That's the case I logged
with thim about the broken PIR table (USB irq showing 9; being 11) and
failure to enable sse on athlon 4/duron/xp chips.

Thanks for the info!

-Cory

The "honor the irq mask" approach (works on my machine):
--- /home/cbell/linux-2.4/arch/i386/kernel/pci-irq.c	Fri Dec  7 01:51:41 2001
+++ /home/cbell/linux-2.4-test/arch/i386/kernel/pci-irq.c	Sat Dec  8 21:04:37 2001
@@ -581,6 +581,7 @@
 	 * reported by the device if possible.
 	 */
 	newirq = dev->irq;
+	if (!((1 << newirq) & mask)) newirq = 0;
 	if (!newirq && assign) {
 		for (i = 0; i < 16; i++) {
 			if (!(mask & (1 << i)))
@@ -599,7 +600,7 @@
 		irq = pirq & 0xf;
 		DBG(" -> hardcoded IRQ %d\n", irq);
 		msg = "Hardcoded";
-	} else if (r->get && (irq = r->get(pirq_router_dev, dev, pirq))) {
+	} else if (r->get && (irq = r->get(pirq_router_dev, dev, pirq) && ((1 << irq) & mask))) {
 		DBG(" -> got IRQ %d\n", irq);
 		msg = "Found";
 	} else if (newirq && r->set && (dev->class >> 8) != PCI_CLASS_DISPLAY_VGA) {
@@ -633,7 +634,7 @@
 			continue;
 		if (info->irq[pin].link == pirq) {
 			/* We refuse to override the dev->irq information. Give a warning! */
-		    	if (dev2->irq && dev2->irq != irq) {
+		    	if (dev2->irq && dev2->irq != irq && ((1 << dev2->irq) & mask)) {
 		    		printk(KERN_INFO "IRQ routing conflict for %s, have irq %d, want irq %d\n",
 				       dev2->slot_name, dev2->irq, irq);
 		    		continue;


  reply	other threads:[~2001-12-09  5:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05  5:16 IRQ Routing Problem on ALi Chipset Laptop (HP Pavilion N5425) Cory Bell
2001-12-05  5:58 ` John Clemens
2001-12-05  8:40   ` Cory Bell
2001-12-05 16:41     ` John Clemens
2001-12-05 16:54       ` Daniel Gryniewicz
2001-12-05 18:48         ` James Cassidy
2001-12-05 19:43           ` Daniel Gryniewicz
2001-12-06  7:00       ` Cory Bell
2001-12-06 15:11         ` John Clemens
2001-12-07  0:41           ` Cory Bell
2001-12-07  1:03             ` Randy.Dunlap
2001-12-07  1:27               ` Cory Bell
2001-12-07 16:24                 ` rddunlap
2001-12-07 17:35                 ` Patrick Mochel
2001-12-07 21:23                   ` Cory Bell
2001-12-07 21:48                     ` Daniel Gryniewicz
2001-12-07 22:32                       ` Cory Bell
2001-12-08 22:38                     ` Pavel Machek
2001-12-08 23:04                     ` Pavel Machek
2001-12-09 20:02                       ` Cory Bell
2001-12-10 10:49                         ` Pavel Machek
2001-12-19 21:53                         ` Pavel Machek
2001-12-20 21:48                           ` Kai Germaschewski
2001-12-20 22:40                             ` Pavel Machek
2001-12-20 23:58                               ` Kai Germaschewski
2001-12-07 20:33             ` Pavel Machek
2001-12-09  5:37               ` Cory Bell [this message]
2001-12-09 13:13                 ` Pavel Machek
2001-12-10 15:26                   ` John Clemens
2001-12-10 16:04                     ` Pavel Machek
2001-12-10 17:53                       ` John Clemens
2001-12-11  1:53                         ` Cory Bell
2001-12-11  9:45                           ` Pavel Machek
2001-12-10 18:32                     ` Pavel Machek
2001-12-10 20:56                     ` Cory Bell
2001-12-10 11:03                 ` Pavel Machek
2001-12-10 16:01                 ` Pavel Machek
2001-12-10 21:24                   ` Cory Bell
2001-12-11 10:02                     ` Pavel Machek
2001-12-11 10:14                 ` Pavel Machek
2001-12-11 15:19                   ` Cory Bell
2001-12-11 15:36                     ` Pavel Machek
2001-12-11 17:08                       ` Cory Bell
  -- strict thread matches above, loose matches on Subject: below --
2001-12-07 18:13 Grover, Andrew

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=1007876254.17062.0.camel@localhost.localdomain \
    --to=cory.bell@usa.net \
    --cc=john@deater.net \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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