From: Ville Hallivuori <vph@iki.fi>
To: linux-kernel@vger.kernel.org
Subject: Gameport in cmpci (2.4.23)
Date: Sun, 30 Nov 2003 04:00:06 +0200 [thread overview]
Message-ID: <20031130020006.GA1199@vph.iki.fi> (raw)
Has anyone managed to get gameport to work in cmpci driver with 2.4.23
kernel? Upgrade from 2.4.22 broke it for me (using cmpci with CM8738
integrated on Soyo Dragon mother board).
With kernels <2.4.23 one would use ns558 to provide game port (cmpci
only enable joystick support). However in 2.4.23 cmpci provides game
port support directly. This new support does not appear to be working.
The major difference between cmpci and ns558 is that cmpci assumes IO
port 0x200 while ns558 probes quite many ports. In my case the port is
0x201, not 0x200 as hard-coded in the driver.
If 201 is valid port for all chips supported by cmpci, the patch below
should fix the issue:
--- cmpci.c.old Fri Nov 28 20:26:20 2003
+++ cmpci.c Sun Nov 30 03:16:22 2003
@@ -3354,7 +3354,7 @@
#endif
s->iosynth = fmio;
s->iomidi = mpuio;
- s->gameport.io = 0x200;
+ s->gameport.io = 0x201;
s->status = 0;
/* range check */
if (speakers < 2)
If the io port is not fixed, perhaps probing mechanism from ns558
could be copied to cmpci...
As I do not have specs for CM8738 I can not quess how large the IO port
should be. With the above fix game port works, but reserved io port is
8 bytes long (vs 1 byte with ns558). Someone with more familiarity to
CM87738 might wish to change this...
--
[Ville Hallivuori][vph@iki.fi][http://www.iki.fi/vph/]
[ID 8E1AD461][FP16=C9 50 E2 DF 48 F6 33 62 5D 87 47 9D 3F 2B 07 5D]
[ID 58543419][FP20=8731 941D 15AB D4A0 88A0 FC8F B55C F4C4 5854 3419]
[ID 8061C24E][FP20=C722 12DA 841E D811 DBFE 2FB3 174C E291 8061 C24E]
LocalWords: Ville Hallivuori
reply other threads:[~2003-11-30 2:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031130020006.GA1199@vph.iki.fi \
--to=vph@iki.fi \
--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;
as well as URLs for NNTP newsgroup(s).