Linux Sound subsystem development
 help / color / mirror / Atom feed
From: James Moody <jemoody@home.com>
To: linux-sound@vger.kernel.org
Subject: es1371 initialization question
Date: Thu, 22 Mar 2001 23:01:34 +0000	[thread overview]
Message-ID: <marc-linux-sound-98530293217833@msgid-missing> (raw)

Hi all,

I fear I'm missing something trivial. I'm using es1371 in 2.4.2-ac20 as
a module. 

Short question: How can I get it to automatically obtain an IRQ for my
soundcard upon initialization? It doesn't seem to do that automatically.

Long story:

It's an Ensoniq 5880 AudioPCI. ASUS CUSL-2 motherboard. There is no option
in the bios regarding a PNP-aware OS.

I have the following PNP devices that work fine as modules:
-ATI Rage 128
-D-Link 538

By 'work fine' I mean that before loading their respective modules,
lspci -vv shows, for each of them,
	Interrupt: pin A routed to IRQ 0

but during module load I see messages like
PCI: Enabling device 02:09.0 (0004 -> 0007)
PCI: Assigned IRQ 5 for device 02:09.0
PCI: Setting latency timer of device 02:09.0 to 64

and the module loads great, and henceforth lspci -vv shows, e.g.,
	Interrupt: pin A routed to IRQ 5.

Perfect.

This does not work with the sound card. modprobe es1371 fails, saying it
can't find the sound card. Trying to specify "irq=" doesn't help matters
(invalid parm_irq). lspci -vv always reports IRQ 0, so it's obvious that
the IRQ isn't being obtained.


HOWEVER:

I used to use ALSA, and everything worked fine with ALSA's snd-ens1371
module. It prints the requisite

PCI: Enabling device 02:0c.0 (0004 -> 0005)
PCI: Assigned IRQ 10 for device 02:0c.0
PCI: Setting latency timer of device 02:0c.0 to 64

upon loading, and works fine. If, at this point, I unload the alsa modules
and load the standard kernel es1371 module, EVERYTHING IS FINE because
the alsa module already got me an IRQ.

What am I missing? Why won't the es1371 module obtain an IRQ for me?

Thanks a lot for any help,

james
-
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo@vger.kernel.org

                 reply	other threads:[~2001-03-22 23:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-sound-98530293217833@msgid-missing \
    --to=jemoody@home.com \
    --cc=linux-sound@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