From: Lars Heineken <Lars.Heineken@gmx.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Opening dev/dsp takes very long
Date: Fri, 19 Mar 2004 13:29:44 +0100 [thread overview]
Message-ID: <405AE7B8.6080603@gmx.de> (raw)
In-Reply-To: <4056BF90.2060005@gmx.de>
I really want to resolve this bug, but there has been little help so
far. I haven't got any response from Perex, too. He was asigned to this
bug via alsa bug report...
Please, someone needs to tell me wich modules are connected with the
functions that took so long, so I can check revision of tthe modules to
find the cause of the delay. Additionally, could someone tell me how to
get debug-output from alsa (Kernel 2.6) ?
Regards,
Lars.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-19 12:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 20:01 Opening dev/dsp takes very long Lars Heineken
2004-03-13 20:24 ` Additional info: " Lars Heineken
2004-03-15 10:35 ` Takashi Iwai
2004-03-15 20:22 ` Lars Heineken
2004-03-16 8:19 ` Clemens Ladisch
2004-03-16 8:49 ` Lars Heineken
2004-03-16 19:04 ` Lars Heineken
2004-03-19 12:29 ` Lars Heineken [this message]
2004-03-19 21:58 ` Lars Heineken
2004-03-19 23:56 ` James Courtier-Dutton
2004-03-20 8:20 ` Lars Heineken
2004-03-20 13:24 ` Jaroslav Kysela
2004-03-20 16:09 ` Lars Heineken
2004-03-20 16:11 ` Jaroslav Kysela
2004-03-20 16:59 ` Lars Heineken
2004-03-20 17:13 ` Tommi Sakari Uimonen
2004-03-20 17:12 ` Jaroslav Kysela
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=405AE7B8.6080603@gmx.de \
--to=lars.heineken@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
/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.