From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000557]: SNDCTL_DSP_GETOPTR not working correctly in specific situation
Date: Fri, 20 May 2005 00:38:06 +0200 [thread overview]
Message-ID: <bc2829bf18342e793a7596e719460bfb@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=557>
======================================================================
Reported By: minmax
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 557
Category: CORE OSS - pcm
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Distribution: Debian unstable
Kernel Version: vanilla 2.6.7
======================================================================
Date Submitted: 10-01-2004 16:18 CEST
Last Modified: 05-20-2005 00:38 CEST
======================================================================
Summary: SNDCTL_DSP_GETOPTR not working correctly in specific
situation
Description:
When the first few writes to the oss emulation device are done in specific
way, SNDCTL_DSP_GETOPTR returns wrongly huge results in info.bytes
======================================================================
----------------------------------------------------------------------
parente - 05-19-05 15:28
----------------------------------------------------------------------
I'm trying to test this on FC4 test 3 with alsa driver 1.0.9rc3. grep isn't
turning up the original lines reported as causing the problem so maybe
they've been removed. Can someone point me to the file where this
problematic code was originally located?
There's still a clipping problem using alsa with gnome speech. I'd like to
see if it's being caused by this same bug.
----------------------------------------------------------------------
minmax - 05-20-05 00:38
----------------------------------------------------------------------
parente: The code that i posted is an example of WORKAROUND for the bug.
not the code from alsa, but something an application writer can do to get
around of the bug in ALSA. I have not investigated where in ALSA the bug
actually lies.
Issue History
Date Modified Username Field Change
======================================================================
10-01-04 16:18 minmax New Issue
10-01-04 16:18 minmax Distribution => Debian unstable
10-01-04 16:18 minmax Kernel Version => vanilla 2.6.7
10-02-04 10:52 minmax Issue Monitored: minmax
04-09-05 16:09 jdthood Note Added: 0004406
04-09-05 16:22 minmax Note Added: 0004410
05-13-05 15:20 gk4 Note Added: 0004646
05-13-05 15:24 perex Note Added: 0004647
05-13-05 15:26 tiwai Note Added: 0004648
05-13-05 19:35 gk4 Note Added: 0004651
05-13-05 19:38 tiwai Note Added: 0004652
05-13-05 19:48 gk4 Note Added: 0004655
05-15-05 15:50 tiwai Note Added: 0004663
05-16-05 16:08 gk4 Note Added: 0004676
05-19-05 15:28 parente Note Added: 0004693
05-20-05 00:38 minmax Note Added: 0004698
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
next reply other threads:[~2005-05-19 22:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 22:38 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 11:46 [ALSA - driver 0000557]: SNDCTL_DSP_GETOPTR not working correctly in specific situation bugtrack
2005-05-31 16:06 bugtrack
2005-05-31 15:55 bugtrack
2005-05-31 15:53 bugtrack
2005-05-31 15:44 bugtrack
2005-05-31 15:39 bugtrack
2005-05-31 15:18 bugtrack
2005-05-31 15:14 bugtrack
2005-05-31 14:56 bugtrack
2005-05-31 14:55 bugtrack
2005-05-31 14:41 bugtrack
2005-05-31 14:10 bugtrack
2005-05-31 13:55 bugtrack
2005-05-31 13:54 bugtrack
2005-05-31 12:04 bugtrack
2005-05-30 7:51 bugtrack
2005-05-27 13:41 bugtrack
2005-05-27 9:04 bugtrack
2005-05-27 8:56 bugtrack
2005-05-26 15:27 bugtrack
2005-05-19 13:28 bugtrack
2005-05-16 14:08 bugtrack
2005-05-15 13:50 bugtrack
2005-05-13 17:48 bugtrack
2005-05-13 17:38 bugtrack
2005-05-13 17:35 bugtrack
2005-05-13 13:26 bugtrack
2005-05-13 13:24 bugtrack
2005-05-13 13:20 bugtrack
2005-04-09 14:22 bugtrack
2005-04-09 14:09 bugtrack
2004-10-01 14:18 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=bc2829bf18342e793a7596e719460bfb@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 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.