Intel rejection of Ubuntu’s Mir patch forces Canonical to go own way

Post by oakwhiz » Tue, Sep 17, 2013, 4:08 PM UTC

marshray wrote: post #96

Daishiman wrote: post #71

Earlier quoted context omitted.

Resources that require low-latency low-level access cannot be multiplexes easily

Why couldn't the kernel perform simple mixing of the audio streams with just as low latency as something like JACK?

I've heard that you can get PulseAudio to connect to JACK, which in turn connects to ALSA. The idea here is that latency-sensitive applications that use routing will connect to JACK, while applications that connect to PulseAudio (like Skype, Firefox, etc.) don't care about latency. However I haven't been able to get this to work properly (why isn't this set up as the default on any of the distros I've tried this on?)

Post by wmf » Tue, Sep 17, 2013, 8:37 PM UTC

nitrogen wrote: post #94

Cogito wrote: post #81

Earlier quoted context omitted.

== Backstory == The X Window System (known as X11 - 11th version) is currently the predominant way for Linux users to use a graphical interface, specifically a windowed interface. It is old and was designed for a purpose that doesn't match current usage nor technology. For this reason, a number of projects have risen to replace X11. 'Wayland' is the best supported of these projects, whilst 'Mir' is similar but has mu…

Does anyone know if Intel could just expose an API that is entirely agnostic of the display server, so Wayland, Mir, XMir, or some random other project could all use the same interface and get full functionality?

I thought that API was KMS/DRM, but maybe it's not enough.

Re: Intel rejection of Ubuntu’s Mir patch forces Canonical to go own way

Re: Intel rejection of Ubuntu’s Mir patch forces Canonical to go own way