From: Timur Tabi <timur@freescale.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: underruns and strange code in pcm_rate.c
Date: Fri, 01 Feb 2008 09:18:46 -0600 [thread overview]
Message-ID: <47A33856.9020806@freescale.com> (raw)
In-Reply-To: <s5hodb01zrp.wl%tiwai@suse.de>
Takashi Iwai wrote:
> An ML archive has also a URL :)
> An advantage of ML is that it can involve developers more easily.
I'm not saying that the developers should use BTS instead of ML. I'm saying
that if it really is a bug in ALSA, I'd like to have formal recognition of that.
A entry in BTS would qualify. I strewn-out discussion on a mailing list has
too low of a signal-to-noise ratio to be useful to the PHBs.
> OK, now the question is in which condition this happens...
I'll try to get an exact testcase, but I think it's pretty much always with
"mplayer -ao oss".
> Could you rewrite snd-dummy driver to behave like your driver?
Uh, are you kidding? My driver is an ASoC driver. How am I supposed to make a
dummy driver "behave" like my driver? My driver isn't doing anything unusual.
> As mentionted, it's important to get the environment to reproduce the
> problem reliably independent on hardwares.
I understand that, but I don't see how I can do that.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-02-01 15:18 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 23:48 underruns and strange code in pcm_rate.c (and patch) Stas Sergeev
2007-11-06 11:29 ` Takashi Iwai
2007-11-06 14:47 ` James Courtier-Dutton
2007-11-06 17:14 ` Stas Sergeev
2007-11-07 11:28 ` Takashi Iwai
2007-11-07 10:40 ` Takashi Iwai
2007-11-06 16:10 ` Stas Sergeev
2007-11-07 10:54 ` Takashi Iwai
2007-11-07 17:16 ` underruns and strange code in pcm_rate.c Stas Sergeev
2007-11-07 14:23 ` Takashi Iwai
2007-11-07 18:52 ` Stas Sergeev
2007-11-08 3:36 ` Takashi Iwai
2007-11-08 8:09 ` Stas Sergeev
2007-11-08 5:38 ` Takashi Iwai
2007-11-08 9:05 ` Stas Sergeev
2007-11-08 6:17 ` Takashi Iwai
2007-11-08 18:34 ` Stas Sergeev
2007-11-09 16:20 ` Timur Tabi
2007-11-09 18:17 ` Stas Sergeev
2007-11-09 19:52 ` Timur Tabi
2007-11-09 20:00 ` Stas Sergeev
2007-11-09 20:06 ` Timur Tabi
2007-11-09 20:11 ` Lee Revell
2007-11-09 20:16 ` Timur Tabi
2007-11-09 20:30 ` Lee Revell
2007-11-09 20:33 ` Timur Tabi
2007-11-09 21:37 ` Lee Revell
2007-11-09 22:52 ` Stas Sergeev
2007-11-09 22:53 ` Timur Tabi
2007-11-12 12:12 ` Clemens Ladisch
2007-11-12 15:56 ` Timur Tabi
2008-01-31 20:49 ` Timur Tabi
2008-02-01 12:32 ` Takashi Iwai
2008-02-01 14:46 ` Timur Tabi
2008-02-01 15:07 ` Takashi Iwai
2008-02-01 15:18 ` Timur Tabi [this message]
2008-02-01 15:27 ` Takashi Iwai
2008-02-01 16:00 ` Timur Tabi
2007-11-07 18:40 ` underruns and strange code in pcm_rate.c (and patch) Stas Sergeev
2007-11-08 4:42 ` Takashi Iwai
2007-11-08 8:27 ` Stas Sergeev
2007-11-08 5:54 ` Takashi Iwai
2007-11-08 9:13 ` Stas Sergeev
2007-11-08 6:25 ` Takashi Iwai
2007-11-08 14:10 ` Alexander E. Patrakov
2007-11-06 13:56 ` Stas Sergeev
2007-11-08 20:06 ` Timur Tabi
2007-11-08 22:01 ` Timur Tabi
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=47A33856.9020806@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).