All of lore.kernel.org
 help / color / mirror / Atom feed
From: Torsten Scheck <torsten.scheck@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: PIIX4 ACPI device - hardwired IRQ9
Date: Tue, 13 Jul 2004 19:34:26 +0200	[thread overview]
Message-ID: <40F41D22.5080603@gmx.de> (raw)

Dear friends:

Please excuse my ignorance: Does the indicated line below have any other 
purpose apart from making me comment it and recompile the kernel to get 
my soundcard working? ;-)

kernel-source-2.4.26/arch/i386/kernel/pci-pc.c
static void __devinit pci_fixup_piix4_acpi(struct pci_dev *d)
         /* PIIX4 ACPI device: hardwired IRQ9 */
  ===>   d->irq = 9;

$ isapnp /etc/isapnp.conf
/etc/isapnp.conf:167 -- Fatal - resource conflict allocating IRQ9
(see pci)
/etc/isapnp.conf:167 -- Fatal - Error occurred executing request
'IRQ 9' --- further action aborted

My soundcard is a Terratec EWS64 XL. I successfully use the 
sam9407-1.0.4 driver after a proper isapnp configuration, i.e. comment 
the hardwired IRQ9 line, compile the kernel, run isapnp.


If there should be really no other purpose I recommend to comment the 
line, so I can use a precompiled kernel from now on. :-)

kernel-source-2.4.26/arch/i386/kernel/pci-pc.c
static void __devinit pci_fixup_piix4_acpi(struct pci_dev *d)
         /* PIIX4 ACPI device: hardwired IRQ9 */
         /* d->irq = 9; */


Or maybe there is some method to deactivate hardwired irqs with boot 
parameters? My first experiments (without a clue about kernel internals) 
using kernel boot parameters like 'acpi=', 'pci=irqmask=0xMMMM' failed, 
though.


Please CC me, if you want me to read your reply asap.

All the best-
Torsten Scheck



             reply	other threads:[~2004-07-16 17:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 17:34 Torsten Scheck [this message]
2004-07-19  5:36 ` PIIX4 ACPI device - hardwired IRQ9 Andrey Panin

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=40F41D22.5080603@gmx.de \
    --to=torsten.scheck@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.