From: Tejun Heo <tj@kernel.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Miklos Szeredi <miklos@szeredi.hu>,
Takashi Iwai <tiwai@suse.de>,
fuse-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] OSS Proxy using CUSE
Date: Fri, 29 Aug 2008 10:28:23 +0200 [thread overview]
Message-ID: <48B7B327.3060306@kernel.org> (raw)
In-Reply-To: <20080829082129.GF16462@cs181140183.pp.htv.fi>
Hello,
Adrian Bunk wrote:
>> Yeah, that's why I agree it's a bit too late but still better late than
>> never. There are just some programs, be it commercial or ancient, which
>> don't work quite as well as it could. Requiring update to ALSA took
>> painfully long years and we're still not in the clear yet. Now should
>> we ask people to update to PA?
>> ...
>
> Doesn't PA already emulate ALSA?
There's an ALSA plugin which connects to PA. It works pretty well most
of the time although there are some odd ones which break. Skype didn't
work too well a few months ago. Dunno how it works these days tho and
it's likely that the next iteration of popular audio apps will do PA
directly.
>> ossp is simply a better way to support /dev/dsp on modern systems and
>> bulk of it lives in userland (and I hope this can be the case for future
>> deprecations too). If for nothing else, it'll enable us to do away with
>> three different emulations at the very least. I mean we can't of course
>> do away with padsp and then some still only work with aoss and then we
>> need in-kernel ALSA OSS emulation as the final fallback when both fail.
>> It's a big mess and ossp can basically OSS emulation as good as
>> in-kernel ALSA OSS w/ muxing.
>
> The in-kernel OSS emulation also support OSS MIDI.
Yeah, and adding midi support to ossp won't add one line of code to the
kernel. :-)
Thanks.
--
tejun
next prev parent reply other threads:[~2008-08-29 8:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 19:05 [ANNOUNCE] OSS Proxy using CUSE Tejun Heo
2008-08-28 20:01 ` Adrian Bunk
2008-08-28 22:18 ` Greg KH
2008-08-28 23:05 ` H. Peter Anvin
2008-08-28 23:14 ` Greg KH
2008-08-28 23:38 ` H. Peter Anvin
2008-08-28 23:32 ` Alan Cox
2008-08-29 1:33 ` Tejun Heo
2008-08-29 6:50 ` Adrian Bunk
2008-08-29 7:26 ` Tejun Heo
2008-08-29 8:09 ` Miklos Szeredi
2008-08-29 8:21 ` Adrian Bunk
2008-08-29 8:28 ` Tejun Heo [this message]
2008-09-02 15:25 ` Pavel Machek
2008-11-27 20:59 ` Jan Engelhardt
2008-11-28 2:23 ` Tejun Heo
2008-11-28 11:35 ` Jan Engelhardt
2008-11-28 12:02 ` Tejun Heo
2008-11-28 12:56 ` Jan Engelhardt
2008-08-29 10:40 ` Takashi Iwai
2008-08-29 10:47 ` Tejun Heo
2009-04-14 2:46 ` [ANNOUNCE] OSS Proxy 1.2 " Tejun Heo
2009-04-22 19:58 ` Miklos Szeredi
2009-04-22 23:59 ` Tejun Heo
2009-06-20 6:13 ` Tejun Heo
2009-06-20 6:37 ` Tejun Heo
2009-04-28 16:01 ` Miklos Szeredi
2009-04-28 16:42 ` Takashi Iwai
2009-04-28 17:17 ` Miklos Szeredi
2009-04-28 19:32 ` Takashi Iwai
2009-04-28 20:12 ` Miklos Szeredi
2009-04-28 21:34 ` Takashi Iwai
2009-04-29 7:13 ` Miklos Szeredi
2009-04-28 23:35 ` Tejun Heo
2009-04-29 7:20 ` Miklos Szeredi
2009-04-29 7:46 ` Tejun Heo
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=48B7B327.3060306@kernel.org \
--to=tj@kernel.org \
--cc=bunk@kernel.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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