Subject: RE: [linux-audio-dev] Plan 9 /dev multiplexing (was: JACK 0.71.1 released)
From: Brad Arant (barant_AT_barant.com)
Date: Sat May 10 2003 - 22:35:18 EEST
Hey Gang -
Plan9 has been around for years and even though it proposes some new
architectures I think some are already outdated and not widely adopted. I am
not aware of any issues being resolved in the area of audio and hardware
specific issues.
-----Original Message-----
From: linux-audio-dev-admin_AT_music.columbia.edu
[mailto:linux-audio-dev-admin_AT_music.columbia.edu]On Behalf Of Ivica
Bukvic
Sent: Saturday, May 10, 2003 11:07 AM
To: linux-audio-dev_AT_music.columbia.edu
Cc: alsa-devel_AT_lists.sourceforge.net
Subject: [linux-audio-dev] Plan 9 /dev multiplexing (was: JACK 0.71.1
released)
Hey guys, the other day I got a chance to speak to a buddy of mine who
is a cpu/OS guru and he was telling me how the author of original Unix
(whose name I can't recall) made this "new" OS called Plan 9 (currently
owned by Bell labs) that essentially fixes all of the shortcomings in
Unix, one of them being multiplexing the /dev stuff on the kernel level.
This would mean that driver implementation API would not need to do
software down-mixing when all that would be done in kernel-space. Seems
that the preliminary results are rather impressive (but probably not
sample accurate, hence we would still need jack for pro stuff). Yet, I
am wondering whether Kernel people should know about this and whether
such overhaul would be doable in the 2.6 or later revisions of Linux
kernel.
Any thoughts?
Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico
> -----Original Message-----
> From: linux-audio-dev-admin_AT_music.columbia.edu
[mailto:linux-audio-dev-
> admin_AT_music.columbia.edu] On Behalf Of Taybin
> Sent: Saturday, May 10, 2003 10:30 AM
> To: jackit-devel; laa; lad; lau
> Subject: [linux-audio-dev] JACK 0.71.1 released
>
> JACK 0.71.1
>
> JACK is a low-latency audio server, written primarily for the
GNU/Linux
> operating system. It can connect a number of different applications to
> an audio device, as well as allowing them to share audio between
> themselves. Its clients can run in their own processes (ie. as normal
> applications), or can they can run within the JACK server (ie. as a
> "plugin").
>
> JACK is different from other audio server efforts in that it has been
> designed from the ground up to be suitable for professional audio
work.
> This means that it focuses on two key areas: synchronous execution of
> all clients, and low latency operation.
>
> **CHANGES**
>
> * fltk macros/detection from bob ham
> * tmpdir configure-time patch from jesse chappell
> * socket error handling change (with additional graph sort!)
> from stephane letz
> * xrun init patch from gunter geiger
>
> Taybin Rutkin
This archive was generated by hypermail 2b28 : Sat May 10 2003 - 22:45:09 EEST