From: David Luyer <luyer@ucs.uwa.edu.au>
To: linux-sound@vger.kernel.org
Subject: Re: Module vs INTO KERNEL ?
Date: Mon, 14 Jun 1999 00:29:14 +0000 [thread overview]
Message-ID: <marc-linux-sound-92931923926223@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92911616207004@msgid-missing>
> Sound is best left as a module. There is no reason to include it and it will
> likely help make your kernel too large to compile. Modules are your friend.
They might be your friend, but they're not mine :P There are many reasons
people might not want to use modules, see many other threads here. And
modules actually take more RAM than building into the kernel if you actually
use them, as well as increasing security issues and having some cost in terms
of TLBs, etc.
Non-modular kernels are your friends.
As to the first question, I'll send the person a copy of my non-modular OPL3SA2
patch.
David.
prev parent reply other threads:[~1999-06-14 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-11 16:03 Module vs INTO KERNEL ? Prasong Aroonruviwat
1999-06-11 16:17 ` shaleh
1999-06-14 0:29 ` David Luyer [this message]
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=marc-linux-sound-92931923926223@msgid-missing \
--to=luyer@ucs.uwa.edu.au \
--cc=linux-sound@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