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: Tue, 31 May 2005 18:06:33 +0200 [thread overview]
Message-ID: <929afdcc7106894db7460799eb9096e2@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=557>
======================================================================
Reported By: minmax
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 557
Category: CORE OSS - pcm
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Distribution: Debian unstable
Kernel Version: vanilla 2.6.7
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 10-01-2004 16:18 CEST
Last Modified: 05-31-2005 18:06 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
======================================================================
----------------------------------------------------------------------
tiwai - 05-31-05 17:55
----------------------------------------------------------------------
fix5 looks fine to me. Let's commit it and close this issue.
----------------------------------------------------------------------
perex - 05-31-05 18:06
----------------------------------------------------------------------
Ok, the problem seems to be resolved. Reopen if not....
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
05-26-05 17:27 Roger Mach Note Added: 0004738
05-27-05 10:56 perex Note Added: 0004742
05-27-05 11:03 perex File Added: fix2.patch
05-27-05 11:04 perex Note Added: 0004743
05-27-05 15:41 parente Note Added: 0004752
05-30-05 09:51 perex Note Added: 0004798
05-31-05 14:04 parente Note Added: 0004831
05-31-05 15:54 perex Status new => assigned
05-31-05 15:54 perex Assigned To => perex
05-31-05 15:55 perex Note Added: 0004833
05-31-05 16:10 parente Note Added: 0004834
05-31-05 16:38 perex File Added: oss-optr-fix3.patch
05-31-05 16:41 perex Note Added: 0004837
05-31-05 16:55 tiwai Note Added: 0004838
05-31-05 16:56 parente Note Added: 0004839
05-31-05 17:02 parente Note Edited: 0004839
05-31-05 17:13 tiwai Note Added: 0004840
05-31-05 17:13 perex File Added: oss-optr-fix4.patch
05-31-05 17:13 tiwai File Added: pcm-oss-ptr-fix4.diff
05-31-05 17:14 perex Note Added: 0004841
05-31-05 17:18 perex Note Added: 0004842
05-31-05 17:39 tiwai Note Added: 0004843
05-31-05 17:44 parente Note Added: 0004844
05-31-05 17:51 perex File Added: oss-optr-fix5.patch
05-31-05 17:52 perex Note Added: 0004845
05-31-05 17:55 tiwai Note Added: 0004846
05-31-05 18:06 perex Status assigned => resolved
05-31-05 18:06 perex Resolution open => fixed
05-31-05 18:06 perex Note Added: 0004847
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
next reply other threads:[~2005-05-31 16:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 16:06 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 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 22:38 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=929afdcc7106894db7460799eb9096e2@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.