From: Paul Davis <paul@linuxaudiosystems.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: ALSA Announce <alsa-announce@alsa-project.org>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: 0.9.1 release
Date: Tue, 11 Mar 2003 17:33:20 -0500 [thread overview]
Message-ID: <200303112230.XAA24419@alsa.alsa-project.org> (raw)
In-Reply-To: Your message of "Tue, 11 Mar 2003 23:03:37 +0100." <Pine.LNX.4.44.0303112255040.6200-100000@pnote.perex-int.cz>
> What's left for 1.0: The sequencer instrument layer will be moved
>completely to the user space.
how about moving the entire sequencer into user-space? kernel 2.5
(with POSIX clock support) makes this entirely viable, i think.
the only ugliness i can see is that inter-thread communication is
harder to make totally robust in the face of system/process shutdown
than user<->kernel communication (c.f. JACK).
there is other stuff that needs to be done for 1.0, not necessarily
development. we need GUI tools for many common user operations. we
need *much* better documentation than we have now. i also think that
the firmware-loading-from-file needs to be done too, and we might need
to make more use of tasklets.
--p
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
next prev parent reply other threads:[~2003-03-11 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 22:03 0.9.1 release Jaroslav Kysela
2003-03-11 22:33 ` Paul Davis [this message]
2003-03-13 9:20 ` Takashi Iwai
2003-03-11 23:05 ` Frank Barknecht
2003-03-12 2:54 ` Bob Ham
2003-03-12 12:08 ` Jordi Mallach
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=200303112230.XAA24419@alsa.alsa-project.org \
--to=paul@linuxaudiosystems.com \
--cc=alsa-announce@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.