From: Adrian Bunk <bunk@fs.tum.de>
To: vojtech@suse.cz
Cc: linux-kernel@vger.kernel.org
Subject: [patch] Re: compile problem: es1371+gamepad
Date: Mon, 17 Dec 2001 22:00:23 +0100 (CET) [thread overview]
Message-ID: <Pine.NEB.4.43.0112172152410.24574-100000@mimas.fachschaften.tu-muenchen.de> (raw)
In-Reply-To: <Pine.NEB.4.43.0112172057360.24574-100000@mimas.fachschaften.tu-muenchen.de>
The patch below should hadle this problem better.
I've found another problem:
When I do completely disable "Input core support" after it was compiled
into the kernel and I go to the "Sound" menu the implicite change that
CONFIG_INPUT_GAMEPORT is automatically turned off wasn't done. It seems I
need to either go to the "Joysticks" menu or to quit "make menuconfig" to
get the wanted effect in the "Sound" submenu. Is this a bug or a known
limitation of "make menuconfig"?
--- drivers/sound/Config.in.old Mon Dec 17 21:25:24 2001
+++ drivers/sound/Config.in Mon Dec 17 21:47:04 2001
@@ -34,9 +34,21 @@
dep_mbool ' Creative SBLive! MIDI' CONFIG_MIDI_EMU10K1 $CONFIG_SOUND_EMU10K1 $CONFIG_EXPERIMENTAL
dep_tristate ' Crystal SoundFusion (CS4280/461x)' CONFIG_SOUND_FUSION $CONFIG_SOUND
dep_tristate ' Crystal Sound CS4281' CONFIG_SOUND_CS4281 $CONFIG_SOUND
-dep_tristate ' Ensoniq AudioPCI (ES1370)' CONFIG_SOUND_ES1370 $CONFIG_SOUND $CONFIG_PCI
-dep_tristate ' Creative Ensoniq AudioPCI 97 (ES1371)' CONFIG_SOUND_ES1371 $CONFIG_SOUND $CONFIG_PCI
-dep_tristate ' ESS Technology Solo1' CONFIG_SOUND_ESSSOLO1 $CONFIG_SOUND
+if [ "$CONFIG_INPUT_GAMEPORT" = "y" ]; then
+ dep_tristate ' Ensoniq AudioPCI (ES1370)' CONFIG_SOUND_ES1370 $CONFIG_SOUND $CONFIG_PCI
+else
+ comment ' Compiled-in Game port support needed for Ensoniq AudioPCI (ES1370)'
+fi
+if [ "$CONFIG_INPUT_GAMEPORT" = "y" ]; then
+ dep_tristate ' Creative Ensoniq AudioPCI 97 (ES1371)' CONFIG_SOUND_ES1371 $CONFIG_SOUND $CONFIG_PCI
+else
+ comment ' Compiled-in Game port support needed for Creative Ensoniq AudioPCI 97 (ES1371)'
+fi
+if [ "$CONFIG_INPUT_GAMEPORT" = "y" ]; then
+ dep_tristate ' ESS Technology Solo1' CONFIG_SOUND_ESSSOLO1 $CONFIG_SOUND
+else
+ comment ' Compiled-in Game port support needed for ESS Technology Solo1'
+fi
dep_tristate ' ESS Maestro, Maestro2, Maestro2E driver' CONFIG_SOUND_MAESTRO $CONFIG_SOUND
dep_tristate ' ESS Maestro3/Allegro driver (EXPERIMENTAL)' CONFIG_SOUND_MAESTRO3 $CONFIG_SOUND $CONFIG_PCI $CONFIG_EXPERIMENTAL
dep_tristate ' Intel ICH (i8xx) audio support' CONFIG_SOUND_ICH $CONFIG_PCI
@@ -44,7 +56,11 @@
dep_tristate ' IT8172G Sound' CONFIG_SOUND_IT8172 $CONFIG_SOUND
fi
dep_tristate ' RME Hammerfall (RME96XX) support' CONFIG_SOUND_RME96XX $CONFIG_SOUND $CONFIG_PCI $CONFIG_EXPERIMENTAL
-dep_tristate ' S3 SonicVibes' CONFIG_SOUND_SONICVIBES $CONFIG_SOUND
+if [ "$CONFIG_INPUT_GAMEPORT" = "y" ]; then
+ dep_tristate ' S3 SonicVibes' CONFIG_SOUND_SONICVIBES $CONFIG_SOUND
+else
+ comment ' Compiled-in Game port support needed for S3 SonicVibes'
+fi
if [ "$CONFIG_VISWS" = "y" ]; then
dep_tristate ' SGI Visual Workstation Sound' CONFIG_SOUND_VWSND $CONFIG_SOUND
fi
@@ -204,13 +220,3 @@
fi
dep_tristate ' TV card (bt848) mixer support' CONFIG_SOUND_TVMIXER $CONFIG_SOUND $CONFIG_I2C
-
-# A cross directory dependence. The sound modules will need gameport.o compiled in,
-# but it resides in the drivers/char/joystick directory. This define_tristate takes
-# care of that. --Vojtech
-
-if [ "$CONFIG_INPUT_GAMEPORT" != "n" ]; then
- if [ "$CONFIG_SOUND_ESSSOLO1" = "y" -o "$CONFIG_SOUND_ES1370" = "y" -o "$CONFIG_SOUND_ES1371" = "y" -o "$CONFIG_SOUND_SONICVIBES" = "y" ]; then
- define_tristate CONFIG_INPUT_GAMEPORT y
- fi
-fi
cu
Adrian
--
Get my GPG key: finger bunk@debian.org | gpg --import
Fingerprint: B29C E71E FE19 6755 5C8A 84D4 99FC EA98 4F12 B400
next prev parent reply other threads:[~2001-12-17 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 19:43 compile problem: es1371+gamepad Simon Roscic
2001-12-17 20:07 ` Adrian Bunk
2001-12-17 20:26 ` Adrian Bunk
2001-12-17 21:00 ` Adrian Bunk [this message]
2001-12-17 21:02 ` [patch] " Vojtech Pavlik
2001-12-18 10:17 ` Adrian Bunk
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=Pine.NEB.4.43.0112172152410.24574-100000@mimas.fachschaften.tu-muenchen.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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).