From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Jaroslav Kysela <perex@suse.cz>,
"alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>
Subject: Re: fatal oops in current CVS confirmed
Date: Tue, 11 Mar 2003 11:12:51 +0100 [thread overview]
Message-ID: <s5hvfyq2ov0.wl@alsa2.suse.de> (raw)
In-Reply-To: <E18sO2D-0003sB-00@sc8-sf-list1.sourceforge.net>
At Mon, 10 Mar 2003 09:17:08 -0500,
Paul Davis wrote:
>
> >oops, sorry. the bug had lived more than two months, so i wonder why
> >this wasn't reported at all...
>
> [ ... ]
>
> >yes, and please remember that 0.9.0-final is not the final for ALSA.
> >we'll be able to release the fixed version ASAP.
> >
> >i guess you won't expect that, for example, the 2.6.0 kernel is
> >so perfect that all components work without any bugs :)
>
> oh sure. i mean, i've known for more than 1 year that the PCM output
> on the cs4231 driver doesn't work anymore (at least not for the
> tropez+), but that's not going to get fixed any time soon, i
> suspect. someone has to get 0.5 installed, add some code to print all
> the registers, and then figure out why 0.9 doesn't do the right thing.
>
> i wonder who that will be :)
i wonder, too :)
but this can't be the reason to postpone the 0.9.0-final tarball.
not all people don't like cvs or rc/beta versions to try, and such a
situation is surely one of the reason to have made such a bug hidden
for long time more than one year.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-03-11 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 13:53 fatal oops in current CVS confirmed Paul Davis
2003-03-10 0:06 ` Jaroslav Kysela
2003-03-10 13:56 ` Takashi Iwai
2003-03-10 14:17 ` Paul Davis
2003-03-11 10:12 ` Takashi Iwai [this message]
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=s5hvfyq2ov0.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.com \
--cc=perex@suse.cz \
/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