From: Cory Bell <cory.bell@usa.net>
To: John Clemens <john@deater.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IRQ Routing Problem on ALi Chipset Laptop (HP Pavilion N5425)
Date: 10 Dec 2001 12:56:00 -0800 [thread overview]
Message-ID: <1008017762.17062.16.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0112101016140.15280-100000@pianoman.cluster.toy>
In-Reply-To: <Pine.LNX.4.33.0112101016140.15280-100000@pianoman.cluster.toy>
On Mon, 2001-12-10 at 07:26, John Clemens wrote:
> I've updated my bios on my Pavilion N5430 and guess what is shows on
> the bios boot screen (if you disable the bios splash screen)... Omnibook
> XE3. They are one in the same, at least model number wise. weird,
> considering there are no AMD omnibooks..
The DMI info is suspiciously similar to ours, as well. Same "Board
Version"...
> Good luck.. I emailed HP support, and got the "we're forwarding your
> request to the BIOS people".. and that was 4 months ago.
They never gave you a case number?
> Ohh, and Marcelo accepted the K7/SSE patch for 2.4.17, so no need for that
> patch anymore..
Woohoo!
> I will try the ACPI PCI routing stuff if i get time tonight (don't have
> access to the machine right now).
For me, the new ACPI didn't help (just had the same table, USB on IRQ
9). And, of course, it doesn't actually do the routing, just displays it
(for now).
I'm leaning toward the "Stolen from Kai" patch over the "stolen from
you" patch. Seems a bit less hackish, and IMHO, the "correct" behavior
anyway (honoring the irq mask). Of course, that could bite us on PIR
tables with bad masks. Thoughts?
-Cory
next prev parent reply other threads:[~2001-12-10 21:05 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
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 [this message]
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=1008017762.17062.16.camel@localhost.localdomain \
--to=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