From: Pavel Machek <pavel@suse.cz>
To: Cory Bell <cory.bell@usa.net>
Cc: John Clemens <john@deater.net>, linux-kernel@vger.kernel.org
Subject: Re: IRQ Routing Problem on ALi Chipset Laptop (HP Pavilion N5425)
Date: Fri, 7 Dec 2001 21:33:13 +0100 [thread overview]
Message-ID: <20011207213313.A176@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0112060938340.32381-100000@pianoman.cluster.toy> <1007685691.6675.1.camel@localhost.localdomain>
In-Reply-To: <1007685691.6675.1.camel@localhost.localdomain>
Hi!
> > You are absolutely correct :) I did the same thing a few weeks ago (when i
> > was really working on it), and traced the lspci -vvxxx output and
> > interpreted everything linux was saying about it. I was looking at it
> > from the acpect of maybe just changing the PCI router in config space as
> > well as the PCI irq from user space without requiring kernel changes at
> > all. The reason why I didn't try that was because i chickened out and
> > didn't know wether changing the PIRQ table woudl a) work or b) permanently
> > screw up my machine. This may still be the "correct way" however...
>
> Well, the *actual* PIRQ table is supposed to be static, according to the
> spec. I don't see the $PIR signature anywhere in the ROM, so it may be
> generated on boot. As for changing the IRQ router PCI config space, the
> last patch is doing that already - r->set is just calling pirq_ali_set,
> which fiddles the bit in question.
>
> Could you try a new patch? Works fine for me...
>
> --- linux/arch/i386/kernel/pci-irq.c.dist Sun Nov 4 09:31:58 2001
> +++ linux/arch/i386/kernel/pci-irq.c Thu Dec 6 15:09:54 2001
> @@ -157,6 +157,13 @@
> {
> static unsigned char irqmap[16] = { 0, 9, 3, 10, 4, 5, 7, 6, 1, 11, 0, 12, 0, 14, 0, 15 };
>
> + if ( pirq == 0x59 &&
> + irqmap[read_config_nybble(router, 0x48, pirq-1)] == 9) {
> + write_config_nybble(router, 0x48, pirq-1, 9);
> + pci_write_config_byte(dev, PCI_INTERRUPT_LINE, 11);
> + dev->irq = 11;
> + DBG(" GROSS HP/ALi Hack Enabled!!");
> + }
> return irqmap[read_config_nybble(router, 0x48, pirq-1)];
> }
Hey, this gross hack fixed USB on HP OmniBook xe3. Good! (Perhaps you
know what interrupt is right for maestro3, also on omnibook? ;-).
Pavel
--
"I do not steal MS software. It is not worth it."
-- Pavel Kankovsky
next prev parent reply other threads:[~2001-12-08 21:03 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 [this message]
2001-12-09 5:37 ` Cory Bell
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=20011207213313.A176@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=cory.bell@usa.net \
--cc=john@deater.net \
--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