public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Dependency bug? Alsa es1370 needs joystick support
Date: Wed, 01 Oct 2003 21:17:58 +0200	[thread overview]
Message-ID: <3F7B2866.4000204@g-house.de> (raw)
In-Reply-To: <slrnbniia2.p62.erik@bender.home.hensema.net>

Erik Hensema wrote:
> Hello,
> 
> I lost sound support after the upgrade from -test4 to -test6; I've been
> told on IRC that this could be due to a dependency of the sounddriver on
> joystick support. This indeed seems to be the case.
> 
> I'm using the (Creative) Ensoniq AudioPCI 1370 driver.

Hi,

same here with es1371. but when i look into the -test6 patch, i see this:

------------------
  config SND_ENS1371
         tristate "(Creative) Ensoniq AudioPCI 1371/1373"
-       depends on SND && SOUND_GAMEPORT
+       depends on SND && GAMEPORT
         help
           Say 'Y' or 'M' to include support for Ensoniq AudioPCI 
ES1371\ and
           Sound Blaster PCI 64 or 128 soundcards.
------------------


but i did not notice that SND_ENS1371 ever depended from SOUND_GAMEPORT.
(i have no joystick, but still listen to music :-))

so, a rather trivial fix would be:

http://www.nerdbynature.de/bits/snd/Kconfig.nogameport.patch

(for SND_ENS1371 only, but should probably do for similiar cards)

oh, as Malte (TM) pointed out, this is tested for i386 only :-)

cheers,
Christian.

-- 
BOFH excuse #29:

It works the way the Wang did, what's the problem


  reply	other threads:[~2003-10-01 19:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30  9:13 Dependency bug? Alsa es1370 needs joystick support Erik Hensema
2003-10-01 19:17 ` Christian Kujau [this message]
2003-10-02 17:03 ` SND_ENS1371 needs GAMEPORT ? Christian Kujau

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=3F7B2866.4000204@g-house.de \
    --to=evil@g-house.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