public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: David Findlay <david_j_findlay@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug: Joystick Driver doesn't talk to CMPCI gameports`
Date: Sat, 22 Sep 2001 11:28:09 +0200	[thread overview]
Message-ID: <20010922112809.A2366@suse.cz> (raw)
In-Reply-To: <200109220514.f8M5EevF002295@ADSL-Server.davsoft.com.au>
In-Reply-To: <200109220514.f8M5EevF002295@ADSL-Server.davsoft.com.au>; from david_j_findlay@yahoo.com.au on Sat, Sep 22, 2001 at 03:13:14PM +1000

On Sat, Sep 22, 2001 at 03:13:14PM +1000, David Findlay wrote:
> I have a C-Media 8738 card built into my motherboard. The sound works fine.
> 
> I use these command as from the joystick documentation:
> 
> modprobe cmpci joystick=1
> modprobe joydev
> modprobe analog
> 
> I am using DevFS and kernel 2.4.9. Nothing appears in /dev/input where js0 
> should actually appear when I insmod the analog joystick. The results of 
> lsmod after doing those commands:
> 
> Workshop:/dev/input# lsmod
> Module                  Size  Used by
> analog                  6960   0  (unused)
> gameport                1808   0  [analog]
> cmpci                  28416   0
> 
> It appears that instead of using the cmpci gameport, it is using the gameport 
> driver or something. Could someone please help me either get it going if 
> there's a workaround, or otherwise tell me what code to look at to fix it? 
> Thanks,
> 
> David
> 
> P.S. I'm not subscribed so please CC your response to me Thanks,

The cmpci driver still doesn't register a gameport, you need the ns558
module as well.

-- 
Vojtech Pavlik
SuSE Labs

      reply	other threads:[~2001-09-22  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-22  5:13 Bug: Joystick Driver doesn't talk to CMPCI gameports` David Findlay
2001-09-22  9:28 ` Vojtech Pavlik [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=20010922112809.A2366@suse.cz \
    --to=vojtech@suse.cz \
    --cc=david_j_findlay@yahoo.com.au \
    --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