From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001224]: artsd-like style
Date: Sun, 17 Jul 2005 11:10:43 +0200 [thread overview]
Message-ID: <85c1e60a19b110ab178e6d1ca97e4b5b@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1224>
======================================================================
Reported By: Hetfield
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1224
Category: PCI - ens1370
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution:
Kernel Version: 2.6.x
======================================================================
Date Submitted: 07-01-2005 14:49 CEST
Last Modified: 07-17-2005 11:10 CEST
======================================================================
Summary: artsd-like style
Description:
i'd like to know if that's a roadmap to let alsa drivers have a artsd (or
windows) style, i mean, multiple streams at once.
that could be very important for example using skype voip and listening
music at the same time.
======================================================================
----------------------------------------------------------------------
rlrevell - 07-17-05 10:46
----------------------------------------------------------------------
Actually this might be useful, if it's the same problem affecting skype.
What does strace -p PID show you, where PID is the kiax PID?
----------------------------------------------------------------------
Hetfield - 07-17-05 11:10
----------------------------------------------------------------------
rlrevell, for alsa/portaudio:
http://sourceforge.net/forum/forum.php?thread_id=1276778&forum_id=448020
i attached a long log. please check.
however:
cat log|grep dsp
stat64("/dev/dsp697", 0xbfbcb3a0) = -1 ENOENT (No such file or
directory)
stat64("/dev/dsp698", 0xbfbcb3a0) = -1 ENOENT (No such file or
directory)
stat64("/dev/dsp699", 0xbfbcb3a0) = -1 ENOENT (No such file or
directory)
stat64("/dev/dsp700", 0xbfbcb3a0) = -1 ENOENT (No such file or
directory)
stat64("/dev/dsp701", 0xbfbcb3a0) = -1 ENOENT (No such file or
directory)
it's abvoius it keeps searching for free dsp.
(in log you'll find it searches in proc too...)
even if dsp is unused.
Issue History
Date Modified Username Field Change
======================================================================
07-01-05 14:49 Hetfield New Issue
07-01-05 14:49 Hetfield Kernel Version => 2.6.x
07-01-05 20:16 Hetfield Note Added: 0005337
07-01-05 20:33 rlrevell Note Added: 0005338
07-01-05 22:56 Hetfield Note Added: 0005343
07-02-05 18:53 pzad Note Added: 0005356
07-02-05 20:11 Hetfield Note Added: 0005357
07-02-05 21:46 pzad File Added: aoss-fcntl.patch
07-02-05 21:47 pzad Note Added: 0005361
07-03-05 09:25 Hetfield Note Added: 0005370
07-03-05 14:09 pzad Note Added: 0005376
07-03-05 15:57 Hetfield Note Added: 0005378
07-04-05 11:49 pzad File Added: aoss.patch
07-04-05 11:53 pzad Note Added: 0005384
07-04-05 14:02 Hetfield Note Added: 0005385
07-08-05 12:16 tiwai Note Added: 0005417
07-08-05 12:27 Hetfield Note Added: 0005418
07-17-05 10:25 Hetfield Note Added: 0005503
07-17-05 10:29 rlrevell Note Added: 0005504
07-17-05 10:46 rlrevell Note Added: 0005505
07-17-05 11:10 Hetfield Note Added: 0005506
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-07-17 9:10 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 9:10 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-02 17:53 [ALSA - driver 0001224]: artsd-like style bugtrack
2006-01-02 17:47 bugtrack
2005-12-30 23:18 bugtrack
2005-11-01 10:12 bugtrack
2005-09-23 8:18 bugtrack
2005-09-20 19:35 bugtrack
2005-09-20 18:20 bugtrack
2005-09-20 14:02 bugtrack
2005-09-20 13:46 bugtrack
2005-09-20 12:56 bugtrack
2005-09-20 7:19 bugtrack
2005-09-19 19:44 bugtrack
2005-09-18 8:55 bugtrack
2005-09-18 8:28 bugtrack
2005-09-18 8:14 bugtrack
2005-09-18 7:36 bugtrack
2005-09-18 1:26 bugtrack
2005-09-17 20:52 bugtrack
2005-09-17 20:38 bugtrack
2005-09-17 20:05 bugtrack
2005-09-17 19:21 bugtrack
2005-09-17 18:11 bugtrack
2005-09-17 18:10 bugtrack
2005-09-17 17:55 bugtrack
2005-09-17 17:50 bugtrack
2005-09-17 17:46 bugtrack
2005-09-17 17:43 bugtrack
2005-09-17 12:51 bugtrack
2005-09-17 12:05 bugtrack
2005-09-02 18:31 bugtrack
2005-09-02 18:26 bugtrack
2005-09-02 18:24 bugtrack
2005-09-02 18:22 bugtrack
2005-09-02 17:57 bugtrack
2005-08-28 13:56 bugtrack
2005-08-09 22:49 bugtrack
2005-08-01 8:20 bugtrack
2005-07-29 15:43 bugtrack
2005-07-28 20:40 bugtrack
2005-07-24 17:10 bugtrack
2005-07-24 7:55 bugtrack
2005-07-21 17:56 bugtrack
2005-07-21 17:55 bugtrack
2005-07-18 20:08 bugtrack
2005-07-18 7:23 bugtrack
2005-07-18 5:33 bugtrack
2005-07-18 4:04 bugtrack
2005-07-18 1:33 bugtrack
2005-07-17 21:43 bugtrack
2005-07-17 21:28 bugtrack
2005-07-17 20:21 bugtrack
2005-07-17 19:23 bugtrack
2005-07-17 19:14 bugtrack
2005-07-17 18:21 bugtrack
2005-07-17 17:51 bugtrack
2005-07-17 17:50 bugtrack
2005-07-17 17:41 bugtrack
2005-07-17 8:46 bugtrack
2005-07-17 8:29 bugtrack
2005-07-17 8:25 bugtrack
2005-07-08 10:27 bugtrack
2005-07-08 10:16 bugtrack
2005-07-04 12:02 bugtrack
2005-07-04 9:53 bugtrack
2005-07-03 13:57 bugtrack
2005-07-03 12:09 bugtrack
2005-07-03 7:25 bugtrack
2005-07-02 19:47 bugtrack
2005-07-02 18:11 bugtrack
2005-07-02 16:53 bugtrack
2005-07-01 20:57 bugtrack
2005-07-01 18:33 bugtrack
2005-07-01 18:16 bugtrack
2005-07-01 12:49 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=85c1e60a19b110ab178e6d1ca97e4b5b@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