Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: William <walsac3@liam2.demon.co.uk>
Cc: geeceezee@free.fr, alsa-devel@alsa-project.org
Subject: Re: OSS vs ALSA war :-)
Date: Tue, 10 Aug 2004 13:21:12 -0400	[thread overview]
Message-ID: <1092158472.3290.12.camel@mindpipe> (raw)
In-Reply-To: <200408101716.SAA04883@liam2.demon.co.uk>

On Tue, 2004-08-10 at 13:16, William wrote:
> Lee Revell wrote:
> > GCZ wrote:
> >> Should I refrain from playing UT2004 just because Nvidia's drivers,
> >> which work beautifully, are closed-source? Should I refrain from
> >> playing Quake 3 because ALSA doesn't work with it?
> > 
> > No, this is why ALSA provides OSS emulation, so every legacy app doesn't
> > have to be recoded.
> 
> One big problem is that some parts of ALSA's OSS emulation have been buggy
> for a long time, especially its /dev/sequencer emulation:
> https://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=28
> [First reported August 2002, present since before Alsa 0.9.0]
> 

Heh, the ALSA bug tracker is hosed right now.  It didn't seem to
remember my login, then when I went to sign up for a new account I got:

ALSA bugtracking system
Warning: Cannot modify header information - headers already sent by
(output started at /srv/www/mantisbt-0.18.3/core/html_api.php:139) in
/srv/www/mantisbt-0.18.3/core/gpc_api.php on line 220

Warning: Cannot modify header information - headers already sent by
(output started at /srv/www/mantisbt-0.18.3/core/html_api.php:139) in
/srv/www/mantisbt-0.18.3/core/print_api.php on line 37

Warning: Cannot modify header information - headers already sent by
(output started at /srv/www/mantisbt-0.18.3/core/html_api.php:139) in
/srv/www/mantisbt-0.18.3/core/print_api.php on line 39

Warning: Cannot modify header information - headers already sent by
(output started at /srv/www/mantisbt-0.18.3/core/html_api.php:139) in
/srv/www/mantisbt-0.18.3/core/print_api.php on line 44

If you can access the text of that bug can you send it to me?

Lee




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

  reply	other threads:[~2004-08-10 17:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  6:36 OSS vs ALSA war :-) Peter Zubaj
2004-08-10  7:14 ` GCZ
2004-08-10  7:33   ` Jaroslav Kysela
     [not found]     ` <41187FA1.80905@free.fr>
     [not found]       ` <Pine.LNX.4.58.0408100955090.1779@pnote.perex-int.cz>
2004-08-10 15:34         ` GCZ
2004-08-10 15:15   ` Frank Barknecht
2004-08-10 15:44     ` GCZ
2004-08-10 16:38       ` Lee Revell
2004-08-10 17:07         ` GCZ
2004-08-10 18:29           ` Lee Revell
2004-08-10 17:16         ` William
2004-08-10 17:21           ` Lee Revell [this message]
2004-08-10 20:45           ` Thierry Vignaud
2004-08-13 12:21           ` Clemens Ladisch
2004-08-10 17:40       ` Frank Barknecht
2004-08-10 18:20         ` GCZ
2004-08-10 19:00           ` Frank Barknecht
  -- strict thread matches above, loose matches on Subject: below --
2004-08-11  7:12 Peter Zubaj

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=1092158472.3290.12.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=geeceezee@free.fr \
    --cc=walsac3@liam2.demon.co.uk \
    /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