Linked by Thom Holwerda on Fri 30th Apr 2010 18:41 UTC, submitted by diegocg
Linux Via LWN: "Lennart Poettering has put up a lengthy post describing the 'systemd' project, which is creating a new init system. The whole thing is an interesting discussion of how system initialization should work. Upstart maintainer Scott James Remnant has posted a response to the announcement."
Permalink for comment 422865
To read all comments associated with this story, please click here.
RE[3]: Poedring
by obi_oni on Wed 5th May 2010 23:58 UTC in reply to "RE[2]: Poedring"
Member since:

OSS4? So... you're advocating doing floating point in kernel space? Because that's what's implied with in-kernel mixing and floating point audio formats.

ALSA might have a difficult API - but from what I understand it's just good at exposing the hardware (features) that are there.

And how does OSS4 deal with user-space audio drivers like for Firewire Audio, or Bluetooth A2DP? How should it do in-kernel mixing for those?

Pulseaudio pushes the stack more - it deals with dynamic latency requests and power management and lots of other things. Things up and down the stack often made wrong assumptions, and got away with it because no software ever pushed it hard. If anything, pulseaudio forced them to confront this, and improve the quality across the board (similar to how NetworkManager forced the wireless network drivers to improve).

What you're advocating is ripping out ALSA and pushing OSS4 in the kernel upstream, right? And then you'd hope to adapt the layers above it so they have similar features than what we have now. All the while hoping that when OSS4 is pushed harder, no evolution or redesign is needed to support certain features.

You don't think this process would cause at least as much or - more likely - even more pain as what we've been through with Pulseaudio?

I don't believe so.

Reply Parent Score: 1