linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Dan <overridex@punkass.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6: joydev is too eager claiming input devices
Date: Thu, 25 Sep 2003 00:12:46 -0500	[thread overview]
Message-ID: <200309250012.48522.dtor_core@ameritech.net> (raw)
In-Reply-To: <1064459037.19555.3.camel@nazgul.overridex.net>

On Wednesday 24 September 2003 10:03 pm, Dan wrote:
> This patch seems to have broken my Logitech Wingman Action usb gamepad,
> it shows as connected but isn't claimed by joydev... another joystick I
> have (saitek cyborg usb gold) works fine, and the logitech worked in
> previous 2.5/6.x kernels so I'm guessing this patch is to blame, I'm on
> 2.6.0-test5-mm1, is there any info from the joystick I can provide you
> with to fix it?  I'm not sure where to look, thanks -Dan
>

Could you please try the following patch (it is incremental against the 
previous one and should apply to the -mm)

--- 2.6.0-test4/drivers/input/joydev.c	2003-09-25 00:06:52.000000000 -0500
+++ linux-2.6.0-test4/drivers/input/joydev.c	2003-09-25 00:02:17.000000000 -0500
@@ -499,7 +499,28 @@
 		.evbit = { BIT(EV_ABS) },
 		.absbit = { BIT(ABS_RX), BIT(ABS_RY) },
 	}, /* magellan and some others report only MISC buttons but we can identify 
-	      them by using special axis auch as RX/RY, ABS_WHEEL or ABS_THROTTLE */
+	      them by using special axis auch as RX/RY, HATnX/HATnY, ABS_WHEEL or 
+	      ABS_THROTTLE */
+	{
+		.flags = INPUT_DEVICE_ID_MATCH_EVBIT | INPUT_DEVICE_ID_MATCH_ABSBIT,
+		.evbit = { BIT(EV_ABS) },
+		.absbit = { BIT(ABS_HAT0X), BIT(ABS_HAT0Y) },
+	},
+	{
+		.flags = INPUT_DEVICE_ID_MATCH_EVBIT | INPUT_DEVICE_ID_MATCH_ABSBIT,
+		.evbit = { BIT(EV_ABS) },
+		.absbit = { BIT(ABS_HAT1X), BIT(ABS_HAT1Y) },
+	},
+	{
+		.flags = INPUT_DEVICE_ID_MATCH_EVBIT | INPUT_DEVICE_ID_MATCH_ABSBIT,
+		.evbit = { BIT(EV_ABS) },
+		.absbit = { BIT(ABS_HAT2X), BIT(ABS_HAT2Y) },
+	},
+	{
+		.flags = INPUT_DEVICE_ID_MATCH_EVBIT | INPUT_DEVICE_ID_MATCH_ABSBIT,
+		.evbit = { BIT(EV_ABS) },
+		.absbit = { BIT(ABS_HAT3X), BIT(ABS_HAT3Y) },
+	},
 	{
 		.flags = INPUT_DEVICE_ID_MATCH_EVBIT | INPUT_DEVICE_ID_MATCH_ABSBIT,
 		.evbit = { BIT(EV_ABS) },

  parent reply	other threads:[~2003-09-25  5:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25  3:03 [PATCH] 2.6: joydev is too eager claiming input devices Dan
2003-09-25  3:54 ` Dmitry Torokhov
2003-09-25  4:31   ` Dan
2003-09-25  5:12 ` Dmitry Torokhov [this message]
2003-09-25  6:29   ` Andrew Morton
2003-10-01  8:10     ` Dan
2003-10-01 17:27       ` Vojtech Pavlik
2003-10-02  1:51         ` Dan
  -- strict thread matches above, loose matches on Subject: below --
2003-09-03  5:50 Dmitry Torokhov

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=200309250012.48522.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=overridex@punkass.com \
    /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).