From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: snd-es1968 (+ snd-cs4236) trouble
Date: Mon, 12 Dec 2005 23:53:20 +0100 [thread overview]
Message-ID: <439DFF60.1020105@keyaccess.nl> (raw)
In-Reply-To: <s5hzmn6y1b1.wl%tiwai@suse.de>
Takashi Iwai wrote:
>>The second I modprobe snd-es1968, snd-cs4236 stops working. If I'm
>>listening to snd-cs4236 at the time I get the last second or so repeated
>>over and over again. Killing the app that was playing via kill -9 works
>>and stops the repeating sound but does not repair things: when I try to
>>use snd-cs4236 again after that, it's still the same -- I only get the
>>first second or so repeated over and over.
>
>
> This sounds like an irq problem. But, still it's weird because cs4236
> is ISA and should be basically intact from PCI driver. One
> possibility is that es1968 has a legacy feature to emulate ISA WSS or
> SB ports, and this conflicts although they are disabled in the driver
> code.
Good point; when you mentioned this I remembered very similar behavior
with old ISA soundcards when there was a DMA channel conflict or
mis-setting.
The ISA CS4236 was using standard DMA 1/0 (playback/record); when I
force it to use channel 3 for playback, the problem is gone. It seems
then the PCI ESS chip grabs DMA1 for the legacy stuf which conflicts
with ISA. Haven't tested capture extensively yet, but it appears that
channel 0 is okay..
Both drivers _can_ be loaded under Windows 98SE, so there's probably a
way to tell the chip to reallyreally not enable the legacy stuff.
More detail: the card's a TerraTec SoundSystem DMX version 1.2, with the
"ESS Canyon-3D" aka ES1970MS-3D (and a Sigmatel STAC9407T) which is
detected by ALSA as a "ESS ES1978 (Maestro-2E)". Probably not a problem...
I see there's no datasheet available specifically for the ES1970, but
I'll try to see if I can find anything in the 1969 or 1978 docs. Please
beat me to it though... :-)
Rene.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-12 22:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 20:13 snd-es1968 (+ snd-cs4236) trouble Rene Herman
2005-12-11 9:08 ` Sergey Vlasov
2005-12-11 15:16 ` Rene Herman
2005-12-12 11:58 ` Takashi Iwai
2005-12-12 22:53 ` Rene Herman [this message]
2005-12-13 7:09 ` Rene Herman
2005-12-13 11:04 ` Takashi Iwai
2005-12-13 20:24 ` Rene Herman
2005-12-14 4:55 ` Rene Herman
2005-12-14 12:00 ` Takashi Iwai
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=439DFF60.1020105@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.