From: jury gerold <gjury@grips.com>
To: Will Newton <will@misconception.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ES1371 driver in kernel 2.4.2
Date: Fri, 09 Mar 2001 16:30:27 +0100 [thread overview]
Message-ID: <3AA8F713.367A5FFD@grips.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0103082255560.11750-100000@dogfox.localdomain>
I am facing the same trouble but in my case
the parallel printer driver complains about a possible
interrupt sharing problem because i run it on interrupt 7.
The alsa driver however works pretty well with this chip for me.
The sound chip does not generate any interrupts on its own line.
So it does not sound at all.
Maybe i can find something by comparing the alsa driver chip initialisation
with the 2.4.2 driver.
It feels strange having the card generating a completely different interrupt
than the one assigned to it.
Anyone with an idea ?
Gerold
Will Newton wrote:
>
> I am still having problems with this driver.
>
> When loading the driver I get:
>
> es1371: version v0.27 time 00:47:56 Mar 7 2001
> es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x08
> PCI: Found IRQ 10 for device 00:0b.0
> es1371: found es1371 rev 8 at io 0xa400 irq 10
> es1371: features: joystick 0x0
> ac97_codec: AC97 codec, id: 0x0000:0x0000 (Unknown)
> spurious 8259A interrupt: IRQ7.
>
> This last line seems strange as /proc/interrupts does not list IRQ7:
>
> 0: 2515137 XT-PIC timer
> 1: 18752 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 4: 2438600 XT-PIC serial
> 5: 0 XT-PIC bttv
> 8: 1 XT-PIC rtc
> 10: 0 XT-PIC es1371
> 12: 310926 XT-PIC PS/2 Mouse
> 14: 137157 XT-PIC ide0
> 15: 35714 XT-PIC ide1
> NMI: 0
> ERR: 1
>
> The chip is actually a Cirrus Logic CS4297A.
prev parent reply other threads:[~2001-03-09 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 22:59 ES1371 driver in kernel 2.4.2 Will Newton
2001-03-09 15:30 ` jury gerold [this message]
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=3AA8F713.367A5FFD@grips.com \
--to=gjury@grips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=will@misconception.org.uk \
/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