From: Rene Herman <rene.herman@keyaccess.nl>
To: Bob Tracy <rct@frus.com>
Cc: ALSA devel <alsa-devel@alsa-project.org>,
Michael Cree <mcree@orcon.net.nz>, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-alpha@vger.kernel.org
Subject: Re: [regression] 2.6.25-rc4 snd-es18xx broken on Alpha
Date: Mon, 10 Mar 2008 17:56:49 +0100 [thread overview]
Message-ID: <47D56851.2000509@keyaccess.nl> (raw)
In-Reply-To: <20080310162130.AFFD3DBA2@gherkin.frus.com>
On 10-03-08 17:21, Bob Tracy wrote:
> Rene Herman wrote:
>>> Bob Tracy wrote:
>>>> Supposedly with the ES1888, dma1 is for capture, dma2 is for playback.
>>>> dma2 == 5 is a 16-bit channel, yes? That could explain much...
>> It is, but what would it explain? You're only having playback problems, right?
>
> dma2 is for playback, I'm having playback problems, dma2 == 5 is a
> a 16-bit channel, and 16-bit DMA is an issue with the es18xx driver
> (according to the comment near the top of the file).
Yes, never mind, misread.
>> Can it be forced to use dma2=0 (an 8-bit channel, and the usual capture
>> channel on es18xx)? However, that might not be the issue anyway:
>
> I'll try a few things like dma2 == dma1, and setting dma2 to an 8-bit
> channel, but I think the various configuration parameters are hard-wired
> on the Alpha (not PnP).
Settable through BIOS perhaps? But anyways, if it used to work, it should
work and I really suspect it's just a matter of a broken OSS emulation on
alpha anyways. In fact, I fairly distinctly remember this being an issue not
too long ago but google is coming up empty...
Takashi? Wasn't there an OSS emulation on Alpha thing a while ago?
>> This sounds very suspiciously like a difference with playing through the
>> native ALSA interface and the OSS emulaion. Could you and/or Bob confirm
>> that sox is using the OSS emulation and not ALSA natively?
>>
>> I could very well imagine the ALSA OSS emulation being broken on Alpha. I
>> doubt any of teh developers has an Alpha. And if aplay works correctly this
>> seems very likely.
>
> I'll see if I can verify whether it's a native ALSA vs. OSS emulation
> issue.
>
> The local version of sox (Debian 12.7.9-1) contains a library dependency
> on libasound.so.2, and a "strings" on the binary yields "ALSA_0.9.0rc4"
> as well as several ALSA error message strings. However, output by
> default goes to /dev/dsp (major 14, minor 3), which is definitely OSS.
That's an expected string and very likely doesn't mean you have a 0.9.0-rc4
alsa-lib installed. "strings [ ... ] | grep ^ALSA_" probably shows a few
later versions as well. But if the problem's the (kernel) OSS emulation then
userspace dopesn't matter anyway.
You seem to have sox installed, so try
$ sox foo.wav -t alsa default
and
$ sox foo.wav -t ossdsp /dev/dsp
to have it play through the ALSA and OSS interfaces, respectively.
Rene.
next prev parent reply other threads:[~2008-03-10 16:56 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 3:58 [regression] 2.6.25-rc4 snd-es18xx broken on Alpha Bob Tracy
2008-03-09 15:34 ` Ivan Kokshaysky
2008-03-09 23:57 ` Bob Tracy
2008-03-10 7:34 ` Michael Cree
2008-03-10 15:17 ` Rene Herman
2008-03-10 15:21 ` Rene Herman
2008-03-10 16:21 ` Bob Tracy
2008-03-10 16:56 ` Rene Herman [this message]
2008-03-10 17:14 ` Takashi Iwai
2008-03-10 19:29 ` [alsa-devel] " Rene Herman
2008-03-10 22:22 ` Bob Tracy
2008-03-10 22:33 ` Rene Herman
2008-03-11 14:07 ` [alsa-devel] " Bob Tracy
2008-03-11 15:17 ` Rene Herman
2008-03-11 18:08 ` Bob Tracy
2008-03-11 20:00 ` [alsa-devel] " Michael Cree
2008-03-11 20:34 ` Bob Tracy
2008-03-12 14:40 ` Bob Tracy
2008-03-12 19:34 ` Rene Herman
2008-03-12 20:31 ` [alsa-devel] " Bob Tracy
2008-03-12 21:12 ` Rene Herman
2008-03-13 4:24 ` Bob Tracy
2008-03-17 22:00 ` Rene Herman
2008-03-18 3:24 ` [alsa-devel] " Bob Tracy
2008-03-18 3:54 ` Michael Cree
2008-03-23 10:40 ` Michael Cree
2008-03-24 18:15 ` Rene Herman
2008-03-24 23:56 ` Michael Cree
2008-03-25 0:29 ` [alsa-devel] " Rene Herman
2008-03-25 1:22 ` Michael Cree
2008-03-25 2:22 ` Rene Herman
2008-03-30 5:18 ` Bob Tracy
2008-03-30 10:02 ` Michael Cree
2008-03-30 9:13 ` [alsa-devel] " Michael Cree
2008-03-25 2:46 ` Rene Herman
2008-03-30 21:07 ` Bob Tracy
2008-03-30 21:11 ` Michael Cree
2008-03-30 21:18 ` Bob Tracy
2008-03-30 4:24 ` Bob Tracy
2008-03-30 22:09 ` [alsa-devel] " Bob Tracy
2008-03-14 13:13 ` Bob Tracy
2008-03-15 1:18 ` Tyson Whitehead
2008-03-17 22:04 ` Rene Herman
2008-03-18 13:55 ` Tyson Whitehead
2008-03-18 22:57 ` Rene Herman
[not found] ` <s5hskypnwp8.wl%tiwai@suse.de>
2008-03-18 14:16 ` Tyson Whitehead
2008-03-29 6:42 ` Bob Tracy
2008-03-29 12:09 ` [alsa-devel] " Rene Herman
2008-03-30 16:14 ` Ivan Kokshaysky
2008-03-30 21:17 ` Michael Cree
2008-03-30 20:24 ` [alsa-devel] " Bob Tracy
2008-03-12 22:48 ` Rafael J. Wysocki
2008-03-23 9:48 ` Michael Cree
2008-03-11 5:36 ` Bob Tracy
2008-03-10 15:08 ` Rene Herman
-- strict thread matches above, loose matches on Subject: below --
2008-03-14 23:33 Bob Tracy
2008-04-01 19:07 [alsa-devel] " Rene Herman
2008-04-01 20:32 ` Bob Tracy
2008-04-01 20:26 [alsa-devel] " Bob Tracy
2008-04-01 21:02 ` Michael Cree
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=47D56851.2000509@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcree@orcon.net.nz \
--cc=rct@frus.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).