[raato]

I got frustrated enough to that last night and did a quick'n dirty hack to joydev driver to convert the 2 axis, hat button shows up to 4 buttons instead.

1st I tested the default driver with jstest and it showed that in my case hat button shows up as axis 4 and 5. Also verified that highest _used_ button number is 11. Then I coded a quick hack to the joysdev driver to replace axis 4 as buttons 12 and 13 and axis 5 as buttons 14 and 15.

My version of joydev.c (had to change extension to .txt to satisfy forum software) attached for brave and daring Linux gamers - remember to check what axis/button values you can use with jstest and the adapt the code to suit you.

Here's a makefile to compile it - spits out joydev.ko which is the loadable driver object

CODE

obj-m += joydev.o

all:
    make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
        
clean:
    make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean

Attached File(s)

•  joydev.txt (14.9K)
  Number of downloads: 218

[Markr]

Thanks! This problem has been pretty frustrating for me.

[raato]

np.

If you need to change the axis/button numbers, all my modifications are in joydev_event function, lines 123 - 163.

To test it you don't even need to unplug the joystick
Just do 'rmmod joydev' to remove the default driver and then 'insmod joydev.ko' to install hacked one.
No reboots, no hassle. I doubt there are many other OS's where you can change HW drivers in the fly

This post has been edited by raato: 26 October 2005 - 09:47 AM

[joshua_]

np.

If you need to change the axis/button numbers, all my modifications are in joydev_event function, lines 123 - 163.

To test it you don't even need to unplug the joystick
Just do 'rmmod joydev' to remove the default driver and then 'insmod joydev.ko' to install hacked one.
No reboots, no hassle. I doubt there are many other OS's where you can change HW drivers in the fly

Hi --

Can you e-mail me a diff against the version in your kernel?

Thanks!

[raato]

here it is (I run 2.6.16 kernel)

CODE

90,92d89
< static int mem_number_1 = 0;
< static int mem_number_2 = 0;
<
119,159c116
<     if (event.type == JS_EVENT_AXIS && event.number > 3 && event.number < 6)
<     {
<         event.type = JS_EVENT_BUTTON;
<         
<         switch (event.number) {
<             case 4:
<                 if (event.value > 0) {
<                   event.value = 1;
<                   event.number = 12;
<                   mem_number_1 = 12;
<                 } else if (event.value < 0) {
<                   event.value = 1;
<                   event.number = 13;
<                   mem_number_1 = 13;
<                 } else {
<                     if (mem_number_1 > 0)
<                         event.number = mem_number_1;
<                     else
<                         event.number = 12;
<                     mem_number_1 = 0;
<                 }
<                 break;
<             case 5:
<                 if (event.value > 0) {
<                   event.value = 1;
<                   event.number = 14;
<                   mem_number_2 = 14;
<                 } else if (event.value < 0) {
<                   event.value = 1;
<                   event.number = 15;
<                   mem_number_2 = 15;
<                 } else {
<                     if (mem_number_2 > 0)
<                         event.number = mem_number_2;
<                     else
<                         event.number = 14;
<                     mem_number_2 = 0;
<                 }
<                 break;
<         }
<     }
---
>

e-mailing it also...

[Doogman]

You know, you really shouldn't have to hack the kernel to use a Flight Yoke with X-Plane.

In Linux, D-Pads (hat switches on yokes) show up as two distinct analog axis, which is really what they are. In Windows, you have some hardware-supplied middleware to help map the hat switches to something useful, but it's doubtful we were ever see something like that for Linux. You shouldn't need it anyway, because the yokes work perfectly in Flight Gear.

All that X-Plane needs is a "Use axis as buttons" feature in the joystick axis setup. If you set a particular axis with that setting, low on the axis is one button, high is another button. Then in the button screen of the joystick section you assign a action to each button as you normally would. Dead simple to use, and a 1000% better than what we have now.

I think even the Windows & Mac users might find this useful, but the Linux users NEED it.

Of course, this is the wrong place for this so I'm going to email the Linux X-Plane guy. Maybe it wouldn't hurt to have a few others email as well, this has to be annoying to everyone with a yoke.

[raato]

You're right. This should be done at application level. I hope Joshua can get this feature in X-Plane.

[egv101]

Well, I'm not sure if I am doing something wrong here, but I get errors when trying to compile the joydev module after applying that diff.

Gentoo Linux
2.6.16
Saitek Cyborg Evo

I have applied the diff to /usr/src/linux/drivers/input/joydev.c and patch returned no errors.

When I try to compile I get this:

CODE

box linux # make modules SUBDIRS=drivers/input
  CC [M]  drivers/input/joydev.o
drivers/input/joydev.c: In function 'joydev_free':
drivers/input/joydev.c:192: warning: implicit declaration of function 'input_class_remove_handle'
drivers/input/joydev.c: In function 'joydev_connect':
drivers/input/joydev.c:456: error: 'struct input_handle' has no member named 'minor_base'
drivers/input/joydev.c:504: warning: implicit declaration of function 'input_class_add_handle'
make[1]: *** [drivers/input/joydev.o] Error 1
make: *** [_module_drivers/input] Error 2

Any idea on how to fix this?

[raato]

That's strange because the patch doesn't have anything to do with those functions and variables - meaning that the file had errors even before applying the patch

Anyway I haven't touched the file in the kernel source tree. I copied it to a safe place, patched the copy and compiled it to an object with a makefile you'll find in the 1st post of this thread.

This post has been edited by raato: 31 January 2007 - 01:06 AM

[egv101]

ok, I have tried this on joydev.c from the linux source and patched with the diff, and on the version you have in the first post....when I run make with that make file all I get is:

CODE

box joystick # make
make: Nothing to be done for `all'.

Can you give it to me step by step how you did this? Either I am doing something wrong, or the source code for 2.6.16 I have is not the same as yours. Either way....I don't see the developers making a correction for this at the app level, so I would like to get this to work if possible.

Thanks for your help

This post has been edited by egv101: 31 January 2007 - 04:56 PM