Up through kernel version 2.6.27.9 I have had no problems with
my joystick on the game port. Now with 2.6.28, the game port
is recognized when the gameport and ns558 modules load, but
loading the tmdc module doesn't also automatically load joydev,
and even loading joydev manually doesn't give me a working
joystick. There are no error messages in dmesg, /var/log/messages,
or /var/log/syslog. This is on Slackware 12.1, so I don't think
it's a distro issue. Do I need to do something different than
in the past to make it work, or is there some debug I can turn
on to give more info?
Please CC me.
Thanks,
Andy Johnson
Luling, Louisiana
(cc linux-input)
On Sat, 10 Jan 2009 15:53:40 -0600 "Andrew S. Johnson" <[email protected]> wrote:
> Up through kernel version 2.6.27.9 I have had no problems with
> my joystick on the game port. Now with 2.6.28, the game port
> is recognized when the gameport and ns558 modules load, but
> loading the tmdc module doesn't also automatically load joydev,
> and even loading joydev manually doesn't give me a working
> joystick. There are no error messages in dmesg, /var/log/messages,
> or /var/log/syslog. This is on Slackware 12.1, so I don't think
> it's a distro issue. Do I need to do something different than
> in the past to make it work, or is there some debug I can turn
> on to give more info?
>
If this doesn't get resolved with a few days, please raise a report at
bugzilla.kernel.org, so that we can not fix it in a more organised
fashion, thanks.
Hi Andrew,
On Saturday 10 January 2009 13:53:40 Andrew S. Johnson wrote:
> Up through kernel version 2.6.27.9 I have had no problems with
> my joystick on the game port. Now with 2.6.28, the game port
> is recognized when the gameport and ns558 modules load, but
> loading the tmdc module doesn't also automatically load joydev,
> and even loading joydev manually doesn't give me a working
> joystick. There are no error messages in dmesg, /var/log/messages,
> or /var/log/syslog. This is on Slackware 12.1, so I don't think
> it's a distro issue. Do I need to do something different than
> in the past to make it work, or is there some debug I can turn
> on to give more info?
>
The patch below should help with joysticks attached to gameports;
it should appear in 2.6.30-rc3.
--
Dmitry
Input: gameport - fix attach driver code
The commit 6902c0bead4ce266226fc0c5b3828b850bdc884a that moved
driver registration out of kgameportd thread was incomplete and
did not add the code necessary to actually attach driver to
already registered devices, rectify that.
Signed-off-by: Dmitry Torokhov <[email protected]>
---
drivers/input/gameport/gameport.c | 14 ++++++--------
1 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/drivers/input/gameport/gameport.c
b/drivers/input/gameport/gameport.c
index ebf4be5..2d175b5 100644
--- a/drivers/input/gameport/gameport.c
+++ b/drivers/input/gameport/gameport.c
@@ -50,9 +50,8 @@ static LIST_HEAD(gameport_list);
static struct bus_type gameport_bus;
-static void gameport_add_driver(struct gameport_driver *drv);
static void gameport_add_port(struct gameport *gameport);
-static void gameport_destroy_port(struct gameport *gameport);
+static void gameport_attach_driver(struct gameport_driver *drv);
static void gameport_reconnect_port(struct gameport *gameport);
static void gameport_disconnect_port(struct gameport *gameport);
@@ -230,7 +229,6 @@ static void gameport_find_driver(struct gameport
*gameport)
enum gameport_event_type {
GAMEPORT_REGISTER_PORT,
- GAMEPORT_REGISTER_DRIVER,
GAMEPORT_ATTACH_DRIVER,
};
@@ -374,8 +372,8 @@ static void gameport_handle_event(void)
gameport_add_port(event->object);
break;
- case GAMEPORT_REGISTER_DRIVER:
- gameport_add_driver(event->object);
+ case GAMEPORT_ATTACH_DRIVER:
+ gameport_attach_driver(event->object);
break;
default:
@@ -706,14 +704,14 @@ static int gameport_driver_remove(struct device *dev)
return 0;
}
-static void gameport_add_driver(struct gameport_driver *drv)
+static void gameport_attach_driver(struct gameport_driver *drv)
{
int error;
- error = driver_register(&drv->driver);
+ error = driver_attach(&drv->driver);
if (error)
printk(KERN_ERR
- "gameport: driver_register() failed for %s, error: %d\n",
+ "gameport: driver_attach() failed for %s, error: %d\n",
drv->driver.name, error);
}
--
1.6.0.6
On Monday 20 April 2009 03:04:09 am Dmitry Torokhov wrote:
>
> The patch below should help with joysticks attached to gameports;
> it should appear in 2.6.30-rc3.
>
--patch snipped--
> --
> Dmitry
The TMDC joystick now works under 2.6.30-rc3. I tested it with
Google Earth flight simulator, Extreme Tux Racer, and Super Tux
Kart and it all seems fine.
Thanks for fixing this.
Andy Johnson
Luling, Louisiana