From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000758]: Full duplex is not working in OSS emulation.
Date: Wed, 10 May 2006 14:56:37 +0200 [thread overview]
Message-ID: <d2132ce0a8d992ac765b3b9b783989dd@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=758>
======================================================================
Reported By: croiset
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 758
Category: PCI - RME 96
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Redhat 7.2
Kernel Version: 2.4.7
======================================================================
Date Submitted: 12-29-2004 10:15 CET
Last Modified: 05-10-2006 14:56 CEST
======================================================================
Summary: Full duplex is not working in OSS emulation.
Description:
If I play something with one player, I am unable to record something on the
same device.
The same thing ispossible with the other cards I have.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0000521 Jack + Alsa not working in full duplex,...
======================================================================
----------------------------------------------------------------------
croiset - 05-09-06 15:49
----------------------------------------------------------------------
We put some logs in rme96.c for debugging the problem.
We obtain this :
The function snd_rme96_capture_hw_params returns -EBUSY when we open the
analog capture device when the analog output device is already opened in
play mode because :
rme96->playback_periodsize = 2048
rme96->capture_frlog = 2
params_period_size(params)=2048
then the tsst in line 1052 (alsa 1.0.11) is valid and then returns -EBUSY
If the analog output device is not opened, when we capture, the values are
:
rme96->playback_periodsize = 0
rme96->capture_frlog = 2
params_period_size(params)=2048
then the test is not valid and the device is working.
----------------------------------------------------------------------
tiwai - 05-10-06 14:56
----------------------------------------------------------------------
That makes sense. RME96 requests exactly the same condition for playback
and capture sides.
When you use OSS, each ioctl tries to change one parameter, and at some
stage, it results in an incompatible state. Usually this should be
restricted via hw_constraint settings, but rme96.c has no proper code for
that.
Issue History
Date Modified Username Field Change
======================================================================
12-29-04 10:15 croiset New Issue
12-29-04 10:15 croiset Distribution => Redhat 7.2
12-29-04 10:15 croiset Kernel Version => 2.4.7
12-29-04 14:17 tiwai Note Added: 0002998
12-29-04 14:54 croiset Note Added: 0003000
12-29-04 17:39 tiwai Note Added: 0003004
12-29-04 17:56 croiset Note Added: 0003005
12-29-04 17:59 croiset Note Added: 0003006
12-29-04 18:05 croiset Note Edited: 0003006
12-29-04 18:18 croiset Note Edited: 0003006
01-03-05 16:30 croiset Note Added: 0003067
09-14-05 16:16 jdthood Relationship added related to 0000521
12-30-05 23:08 rlrevell Note Added: 0007278
01-02-06 09:12 croiset Note Added: 0007368
05-09-06 14:09 croiset Note Added: 0009657
05-09-06 15:49 croiset Note Added: 0009659
05-10-06 14:56 tiwai Note Added: 0009717
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-05-10 12:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 12:56 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 14:25 [ALSA - driver 0000758]: Full duplex is not working in OSS emulation bugtrack
2006-05-10 14:22 bugtrack
2006-05-10 14:00 bugtrack
2006-05-10 13:48 bugtrack
2006-05-09 13:49 bugtrack
2006-05-09 12:09 bugtrack
2006-01-02 8:12 bugtrack
2005-12-30 22:08 bugtrack
2005-09-14 14:16 bugtrack
2005-01-03 15:30 bugtrack
2004-12-29 16:59 bugtrack
2004-12-29 16:56 bugtrack
2004-12-29 16:39 bugtrack
2004-12-29 13:54 bugtrack
2004-12-29 13:17 bugtrack
2004-12-29 9:15 bugtrack
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=d2132ce0a8d992ac765b3b9b783989dd@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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