From: Lee Revell <rlrevell@joe-job.com>
To: "Budde, Marco" <budde@telos.de>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: RE: kbuild & C++
Date: Wed, 07 Sep 2005 14:52:13 -0400 [thread overview]
Message-ID: <1126119134.13159.82.camel@mindpipe> (raw)
In-Reply-To: <809C13DD6142E74ABE20C65B11A2439809C4BF@www.telos.de>
On Wed, 2005-09-07 at 12:17 +0200, Budde, Marco wrote:
> Well, it is not the first driver I am writing for Linux.
> So yes, I do know, what is part of a Linux driver and
> what is not.
It should be fairly obvious. Windows drivers do all kinds of crap that
just obviously doesn't belong in the kernel, often to implement features
that Windows doesn't have. For example half the Windows sound drivers
do AC3 decoding inside the driver (and half of those lie and say it's a
hardware AC3 decoder).
On Linux we use a simple userspace program called ac3dec for that.
Anything that can reasonably be done in userspace belongs in userspace.
We DON'T do things in the kernel just because it would be slightly
faster or it has an RT constraint or the kernel lacks some feature that
your driver wants or whatever.
Lee
next prev parent reply other threads:[~2005-09-07 18:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 10:17 kbuild & C++ Budde, Marco
2005-09-07 18:52 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-15 12:35 Budde, Marco
2005-09-18 18:41 ` Sam Ravnborg
2005-09-07 12:04 Budde, Marco
2005-09-07 12:58 ` Bernd Petrovitsch
2005-09-07 13:15 ` Nick Piggin
[not found] <4JJOt-77X-9@gated-at.bofh.it>
2005-09-07 12:02 ` Bodo Eggert
2005-09-07 9:13 Budde, Marco
2005-09-07 9:57 ` Valdis.Kletnieks
2005-09-07 10:45 ` Esben Nielsen
2005-09-07 10:00 ` Bernd Petrovitsch
2005-09-06 11:23 Budde, Marco
2005-09-06 11:30 ` Bernd Petrovitsch
2005-09-06 21:08 ` Chris Frey
2005-09-07 6:39 ` Bernd Petrovitsch
2005-09-06 11:38 ` linux-os (Dick Johnson)
2005-09-06 21:20 ` Jesper Juhl
2005-09-06 22:20 ` Esben Nielsen
2005-09-06 22:22 ` Randy.Dunlap
2005-09-06 22:32 ` Jesper Juhl
2005-09-07 2:33 ` Valdis.Kletnieks
2005-09-07 9:21 ` Esben Nielsen
2005-09-07 10:11 ` Valdis.Kletnieks
2005-09-07 10:58 ` Esben Nielsen
2005-09-07 11:44 ` Bernd Petrovitsch
2005-09-06 21:41 ` Sam Ravnborg
2005-09-10 12:29 ` Sam Ravnborg
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=1126119134.13159.82.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=budde@telos.de \
--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