From: Zach Brown <zab@zabbo.net>
To: J Sloan <jjs@toyota.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Thomas Hood <jdthood@mail.com>,
linux-kernel@vger.kernel.org
Subject: Re: CS423x audio driver updates for testing
Date: Thu, 15 Nov 2001 18:18:01 -0500 [thread overview]
Message-ID: <20011115181801.N6462@erasmus.off.net> (raw)
In-Reply-To: <E164QJM-0000y2-00@the-village.bc.nu> <3BF40D3C.8D3F0369@lexus.com>
In-Reply-To: <3BF40D3C.8D3F0369@lexus.com>; from jjs@toyota.com on Thu, Nov 15, 2001 at 10:45:16AM -0800
> I seem to remember, folks intererested in gaming and
> mulitmedia apps had done some latency profiling and
> found that the alsa drivers were a source of really bad
> latency - am I imagining all this or does it ring a bell
> with someone?
Thats the sort of thing that can be fixed as ALSA is merged, I would
hope.
ALSA is much, much, closer to a nice kernel sound driver setup than the
current OSS code base. It has problems, yes, but a good attack during
2.5 should iron out the worst of it. There just needs to be an
understanding up front that the ALSA as initially merged may see
significant changes to get rid of some of the 'non-kernel friendly'
code. (in-kernel mixing, some interesting naming, over-abstraction in
places, gratuitious wrapping of kernel functions.. all should be
candidates for early removal, IMHO)
but, really, I spend next to 0 time on sound stuff these tdays, so take
all of this with about 7 tons of salt.
- z
next prev parent reply other threads:[~2001-11-15 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 13:55 CS423x audio driver updates for testing Thomas Hood
2001-11-15 17:28 ` Alan Cox
2001-11-15 18:45 ` J Sloan
2001-11-15 23:18 ` Zach Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-15 10:17 Alan Cox
2001-11-27 18:34 ` Rob Landley
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=20011115181801.N6462@erasmus.off.net \
--to=zab@zabbo.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jdthood@mail.com \
--cc=jjs@toyota.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox