From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: Query about Float Point Operation
Date: Sun, 28 Mar 2010 22:47:09 +0100 [thread overview]
Message-ID: <20100328214709.GA14740@shareable.org> (raw)
In-Reply-To: <tencent_294E932A6E12E0191CF4271B@qq.com>
??? wrote:
> WOW
> My audio codec drivers use float point operation heavily!
> Does that mean that I can ONLY implement it on USER space ?
It's not impossible, but it's quite complicated, not supported
(no need), and architecture-dependent.
Anyway, codecs should be done in userspace. That's how Linux does
software codecs. Only audio output, or passing raw data to an audio
DSP, needs to happen in kernel space.
-- Jamie
next prev parent reply other threads:[~2010-03-28 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 13:41 Query about Float Point Operation 胡杨树
2010-03-28 21:47 ` Jamie Lokier [this message]
2010-03-28 23:34 ` Nicolas Pitre
-- strict thread matches above, loose matches on Subject: below --
2010-03-23 12:57 胡杨树
2010-03-23 13:34 ` Måns Rullgård
2010-03-29 5:22 ` Rajanikanth H.V
2010-03-29 8:11 ` Russell King - ARM Linux
2010-03-29 10:59 ` Martin Guy
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=20100328214709.GA14740@shareable.org \
--to=jamie@shareable.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).