public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Weber <weber@nyc.rr.com>
To: linux-kernel@vger.kernel.org
Cc: Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: Linux 2.5.4 Sound Driver Problem
Date: Mon, 11 Feb 2002 14:58:28 -0500	[thread overview]
Message-ID: <3C682264.7060707@nyc.rr.com> (raw)
In-Reply-To: <fa.c0t1afv.1f02hrj@ifi.uio.no> <fa.jvah72v.1h34cqd@ifi.uio.no>

> Try to do this. Open drivers/sound/Config.in, and find YMFPCI
> tristate, then delete $CONFIG_SOUND_OSS from that line.
> Edit .config, and remove CONFIG_SOUND_OSS. Rerun make oldconfig,
> when prompted for CONFIG_SOUND_OSS, say N. This should work.

if [ "$CONFIG_SOUND_OSS" = "y" -o "$CONFIG_SOUND_OSS" = "m" ]; then
    bool '      Verbose initialisation' CONFIG_SOUND_TRACEINIT
    bool '      Persistent DMA buffers' CONFIG_SOUND_DMAP

The YMFPCI option was in the body of the above if statement, so I had
to move it out of there to be able to enable it without enabling 
CONFIG_SOUND_OSS.  I hope this is what you meant.

> 
> I use monolithic kernels on 2.4, but on 2.5 it is officially
> discouraged, so I gave up on it.

To what granularity?  I use the hardware as a rule of thumb: if the
the hardware supported is fixed, then I put it in the kernel.
Should I compile everything as modules?

However, I did hear something about everything being a module in 2.6
because the kernel will eventually use initramfs or something...

Anyway, this is a different thread.  But I would like to hear your rule 
of thumb for when you compile things as a module...


> I do not see ANYTHING in 2.5.4 Makefiles that depended on
> CONFIG_SOUND_GAMEPORT. This option only works to restric
> some configurations choices, but it does not control any
> compilations. Seems like a deadwood to me. Just kill it too.

I kill it but make oldconfig enables it right back :).
I'll look through Config.in in a bit.


       reply	other threads:[~2002-02-11 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.c0t1afv.1f02hrj@ifi.uio.no>
     [not found] ` <fa.jvah72v.1h34cqd@ifi.uio.no>
2002-02-11 19:58   ` John Weber [this message]
2002-02-11 20:42     ` Linux 2.5.4 Sound Driver Problem John Weber
     [not found] <mailman.1013448601.14957.linux-kernel2news@redhat.com>
2002-02-11 17:46 ` Pete Zaitcev
2002-02-11 18:12   ` Alan Cox
2002-02-11 18:13     ` John Weber
2002-02-11 18:27       ` Pete Zaitcev
2002-02-11 18:48         ` John Weber
     [not found]         ` <3C6816EC.2040406@nyc.rr.com>
2002-02-11 19:21           ` Pete Zaitcev
2002-02-11 17:27 John Weber

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=3C682264.7060707@nyc.rr.com \
    --to=weber@nyc.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.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