Linux Sound subsystem development
 help / color / mirror / Atom feed
From: shaleh@clifford.livenet.net
To: linux-sound@vger.kernel.org
Subject: Re: Module vs INTO KERNEL ?
Date: Fri, 11 Jun 1999 16:17:34 +0000	[thread overview]
Message-ID: <marc-linux-sound-92911681507755@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92911616207004@msgid-missing>

> 
> Dear All,
> 
>         First, I compile sound as a module for a while (ethernet, some fs,
>     and almost as a module) but right now, I want to compile all of its that
>     I frequently use into kernel.
>         All of others is fine except sound :(
>         I don't know why, I just change <M> to <*> and specific the IRQ, DMA
>     at Sound section of 'make menuconfig'
> 
>         There's no /dev/mixer, /dev/dsp nothing except /proc/sound.
> 

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.

  reply	other threads:[~1999-06-11 16:17 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 [this message]
1999-06-14  0:29 ` David Luyer

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-92911681507755@msgid-missing \
    --to=shaleh@clifford.livenet.net \
    --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