From: Pavel Machek <pavel@suse.cz>
To: Cory Bell <cory.bell@usa.net>
Cc: Patrick Mochel <mochel@osdl.org>,
linux-kernel@vger.kernel.org,
Andrew Grover <andrew.grover@intel.com>,
John Clemens <john@deater.net>
Subject: Re: IRQ Routing Problem on ALi Chipset Laptop (HP Pavilion N5425)
Date: Sun, 9 Dec 2001 00:04:52 +0100 [thread overview]
Message-ID: <20011209000451.A117@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0112070925280.851-100000@segfault.osdlab.org> <1007760235.10687.0.camel@localhost.localdomain>
In-Reply-To: <1007760235.10687.0.camel@localhost.localdomain>
Hi!
So I investigated a little more, and maestro3 soundcard is also hooked
at irq 11 -- with this *very* cruel hack it works for me (at least
playback).
--- clean/drivers/sound/maestro3.c Thu Oct 11 18:43:30 2001
+++ linux/drivers/sound/maestro3.c Sat Dec 8 23:39:28 2001
@@ -2685,7 +2683,7 @@
}
}
- if(request_irq(card->irq, m3_interrupt, SA_SHIRQ, card_names[card->card_type], card)) {
+ if(request_irq(11 /* card->irq Gross hack */, m3_interrupt, SA_SHIRQ, card_names[card->card_type], card)) {
printk(KERN_ERR PFX "unable to allocate irq %d,\n", card->irq);
Pavel
--
"I do not steal MS software. It is not worth it."
-- Pavel Kankovsky
next prev parent reply other threads:[~2001-12-09 11:10 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 [this message]
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
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=20011209000451.A117@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=andrew.grover@intel.com \
--cc=cory.bell@usa.net \
--cc=john@deater.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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