From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bill Fink <billfink@mindspring.com>
Cc: <linuxppc-dev@lists.linuxppc.org>,
<yellowdog-general@lists.terrasoftsolutions.com>
Subject: Re: dmasound audio patch
Date: Mon, 8 Apr 2002 19:45:24 +0100 [thread overview]
Message-ID: <20020408184524.14156@smtp.wanadoo.fr> (raw)
In-Reply-To: <20020408152350.5fe654da.billfink@mindspring.com>
>I halfway understand the reasoning but I don't really agree with it.
>I don't see any significant problem with doing the byte swapping in
>the kernel. From an engineering standpoint, it seems to make more
>sense to me to do this common function once in the kernel driver rather
>than redoing it over and over in every audio app, and keep getting bit
>by the same endianness problem over and over again. Linus and the PC
>world don't have to worry about it, but us PPC types keep getting a
>delay in usable audio apps as a result.
>
>Oh well, I know I'm tilting at windmills here. :-)
No, here you are hitting the lack of proper audio architecture
in linux ;)
It's not the kernel work, definitely, to do any munging on samples
even if it is as simple as byteswap. It's the role of a userland
based process to do mixing & format conversion. I hope alsa will
finally provide something around those lines.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-08 18:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 21:23 dmasound audio patch Bill Fink
2002-04-08 10:30 ` Michel Dänzer
2002-04-08 12:41 ` Bill Fink
2002-04-08 12:50 ` Michel Dänzer
2002-04-08 14:14 ` Bill Fink
2002-04-08 13:22 ` Bill Fink
2002-04-08 11:49 ` Benjamin Herrenschmidt
2002-04-08 19:23 ` Bill Fink
2002-04-08 18:45 ` Benjamin Herrenschmidt [this message]
2002-04-09 1:52 ` Bill Fink
2002-04-09 2:24 ` jeffk
2002-04-09 7:18 ` Ethan Benson
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 3:36 Bill Fink
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=20020408184524.14156@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=billfink@mindspring.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=yellowdog-general@lists.terrasoftsolutions.com \
/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;
as well as URLs for NNTP newsgroup(s).