Improve desktop interactivity under memory pressure The app sends the audio to these CUSE devices, and the OSS Proxy will forward it to a "slave" (currently there's only one slave implemented, pulseaudio)Ĭode: CUSE (commit) OSS Proxy home and code: ġ.3. From the POV of the applications, these devices are proper character devices and behave exactly the same way, so it can be used as a replacement for the in-kernel ALSA OSS emulation layer. OSS Proxy uses CUSE to implement the OSS interface - /dev/dsp, /dev/adsp and /dev/mixer. ALSA contains OSS emulation, but sadly the emulation is in the kernel, behind the userland multiplexing layer, which means that if your sound card doesn't support multiple audio streams (most modern cards don't), only either one of ALSA or OSS emulation interface would be usable at any given moment. It can be used for many things, for example "proxying" OSS audio from OSS apps through the ALSA userspace layer, or to an audio system which can forward the sound through the network. Recommended LWN article: Character devices in user spaceĬUSE is an extension of FUSE allowing character devices to be implemented in userspace, it has been contributed by Tejun Heo (SUSE) CUSE (character devices in userspace) and OSS Proxy No xHCI hardware has made it onto the market yet, but these patches have been tested under the Fresco Logic host controller prototype.ġ.2. This version Linux adds support for USB 3.0 devices (contributed by Sarah Sharp from Intel) and the hardware that implements the eXtensible Host Controller Interface (xHCI) 0.95 specification.
Other news sources tracking the kernel changes.