From: Patrick McFarland <pmcfarland@downeast.net>
To: dtor_core@ameritech.net
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: alsa es1371's joystick functionality broken in 2.6.11-mm4
Date: Tue, 22 Mar 2005 21:19:31 -0500 [thread overview]
Message-ID: <200503222119.55270.pmcfarland@downeast.net> (raw)
In-Reply-To: <d120d50005032205584fd37a94@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Tuesday 22 March 2005 08:58 am, Dmitry Torokhov wrote:
> On Tue, 22 Mar 2005 07:06:07 -0500, Patrick McFarland
> Ok, just so I know where we stand: your gameport/joystick does work in
> plain 2.6.11 but does not in 2.6.11-mm4, correct? When you load the
> module with "joystick_port=1" is there any messages from ens1371 in
> dmesg? Have you tried specifying exact port, like
> "joystick_port=0x200" or "joystick_port=0x218"? Do you see these ports
> reserved in /proc/ioports? What about /sys/bus/gameport/devices/? Do
> you see anything in that directory?
I haven't tested it with 2.6.11 yet... real life showed up, and hasn't gone
away yet. *stab!* I'll be testing it right after I send this email.
With joystick_port=1 there are no messages from the module, I've tried a bunch
of specific ports, and it doesn't work. The ports are not reserved
in /proc/ioports. /sys/bus/gameport/devices is empty.
--
Patrick "Diablo-D3" McFarland || pmcfarland@downeast.net
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-23 2:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 20:57 Patrick McFarland
2005-03-21 0:39 ` Andrew Morton
2005-03-21 2:04 ` Patrick McFarland
2005-03-21 3:21 ` Dmitry Torokhov
2005-03-22 0:58 ` Patrick McFarland
2005-03-22 3:15 ` Dmitry Torokhov
2005-03-22 3:41 ` Patrick McFarland
2005-03-22 3:49 ` Dmitry Torokhov
2005-03-22 12:06 ` Patrick McFarland
2005-03-22 13:58 ` Dmitry Torokhov
2005-03-23 2:19 ` Patrick McFarland [this message]
2005-03-23 4:41 ` Patrick McFarland
2005-03-24 6:00 ` Dmitry Torokhov
2005-03-25 14:28 ` Patrick McFarland
2005-03-27 11:23 ` Patrick McFarland
2005-03-31 4:59 ` Patrick McFarland
2005-04-07 11:17 ` Patrick McFarland
2005-04-07 19:52 ` Ian Pilcher
2005-04-08 1:33 ` Patrick McFarland
2005-04-15 1:18 ` Patrick McFarland
2005-04-15 1:26 ` Lee Revell
2005-04-15 1:41 ` Patrick McFarland
2005-04-20 4:47 ` Patrick McFarland
2005-04-21 1:42 ` Patrick McFarland
2005-04-21 2:12 ` Dmitry Torokhov
2005-04-21 2:21 ` Patrick McFarland
2005-04-21 2:29 ` Dmitry Torokhov
2005-04-21 3:03 ` Patrick McFarland
2005-05-11 14:00 ` Takashi Iwai
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=200503222119.55270.pmcfarland@downeast.net \
--to=pmcfarland@downeast.net \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--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
all inboxes | Powered by JetHome®