From: Tejun Heo <tj@kernel.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Adrian Bunk <bunk@kernel.org>,
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, 28 Nov 2008 11:23:15 +0900 [thread overview]
Message-ID: <492F5613.4090908@kernel.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0811272148490.23969@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Thursday 2008-08-28 22:01, Adrian Bunk wrote:
>> On Thu, Aug 28, 2008 at 09:05:53PM +0200, Tejun Heo wrote:
>>> Hello again,
>>>
>>> So, after all the fuss, here's the state-of-the-art standard-compliant
>>> cloud-computing web-3.0-beta web page for OSS emulation using CUSE.
>>>
>>> http://userweb.kernel.org/~tj/ossp/
>>>
>>> It works pretty well here. :-)
>> Sorry for being destructive, but 6 years after ALSA went into the
>> kernel we are slightly approaching the point where all applications
>> support ALSA.
>
> Unreal Tournament GOTY/99 does not (seem to). And I doubt someone
> is going to fix commercial games. Though being a static binary,
> its use of shared libraries that do the sound device open makes
> aoss a possibility, if that helps. But it does not support ALSA
> natively - and would make a point for CUSE.
The devel version of ossp (not out yet, waiting for CUSE and mmap
support merge) can do all the quakes (even the dreaded quake1 which
even ALSA OSS emulation or native OSS can't do because of strict
sample/freq requirement which modern devices don't support anymore)
and skype-static-oss are working fine. The latency is still a tad bit
high due to PA interaction but everything is mostly in place. I'm
fairly sure UT would work too. Do you know where I can get a demo of
it?
Thanks.
--
tejun
next prev parent reply other threads:[~2008-11-28 2:23 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
2008-09-02 15:25 ` Pavel Machek
2008-11-27 20:59 ` Jan Engelhardt
2008-11-28 2:23 ` Tejun Heo [this message]
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=492F5613.4090908@kernel.org \
--to=tj@kernel.org \
--cc=bunk@kernel.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=jengelh@medozas.de \
--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