On Tuesday 05 May 2009 04:47:39 pm Sid Boyce wrote:
> To summarise the stuff below posted 15th. July 2007. I had no trouble
> with CH Yoke and Pedals until around kernel 2.6.17 where they were seen
> in dmesg, but the controls didn't work in js_demo, jstest, jscal or
> FlightGear until they were replugged after a reboot. Until today, that
> is, when a patch on the linux-usb list for a CH joystick was adapted for
> the Yoke and Pedals.
> I appied it to vanilla kernel 2.6.30-rc4-git1 and finally they work
> without having to replug them. The patch has been sent to linux-usb and
> should be in the mainline kernel soon and definitely in 2.6.30.
For me the last kernel that was OK with the CH controllers without patches was
2.6.18.
I just hand "applied" this patch along with adding a entries for my CH COMBAT
stick to 2.6.26 and rebooted and my joysticks now all work without having to
replug them after startup.
Thank you Sid for tracking this down. I was not able to locate these patches
on the linux-usb list. Could you provide some links to the other CH Products
joystick patch. I would like to confirm that it will fix the COMBAT Stick.
Hal
> --------------------------Cut---------------------------------------
> --- /usr/src/linux-2.6.30-rc4-git1/drivers/hid/hid-ids.h
> 2009-05-03 15:06:20.458499276 +0100
> +++ /usr/src/linux-2.6.30-rc4-git1a/drivers/hid/hid-ids.h
> 2009-05-05 22:09:14.238300053 +0100
> @@ -113,6 +113,10 @@
> #define USB_VENDOR_ID_BERKSHIRE 0x0c98
> #define USB_DEVICE_ID_BERKSHIRE_PCWD 0x1140
>
> +#define USB_VENDOR_ID_CH 0x068e
> +#define USB_DEVICE_ID_CH_YOKE 0x00ff
> +#define USB_DEVICE_ID_CH_PEDALS 0x00f2
> +
> #define USB_VENDOR_ID_CHERRY 0x046a
> #define USB_DEVICE_ID_CHERRY_CYMOTION 0x0023
>
> --- /usr/src/linux-2.6.30-rc4-git1/drivers/hid/usbhid/hid-quirks.c
> 2009-04-30 05:48:16.000000000 +0100
> +++ /usr/src/linux-2.6.30-rc4-git1a/drivers/hid/usbhid/hid-quirks.c
> 2009-05-05 22:13:16.843355409 +0100
> @@ -50,6 +50,8 @@
> { USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_2PORTKVM,
> HID_QUIRK_NOGET },
> { USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_4PORTKVM,
> HID_QUIRK_NOGET },
> { USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_4PORTKVMC,
> HID_QUIRK_NOGET },
> + { USB_VENDOR_ID_CH, USB_DEVICE_ID_CH_YOKE, HID_QUIRK_NOGET },
> + { USB_VENDOR_ID_CH, USB_DEVICE_ID_CH_PEDALS, HID_QUIRK_NOGET },
> { USB_VENDOR_ID_DMI, USB_DEVICE_ID_DMI_ENC, HID_QUIRK_NOGET },
> { USB_VENDOR_ID_ELO, USB_DEVICE_ID_ELO_TS2700, HID_QUIRK_NOGET },
> { USB_VENDOR_ID_SUN, USB_DEVICE_ID_RARITAN_KVM_DONGLE,
> HID_QUIRK_NOGET },
> -------------------------Cut-------------------------------------------
> Regards
> Sid.
>
> Sid Boyce wrote:
> > Yair Zohar wrote:
> >> Hello,
> >> Does anyone uses CH PRODUCTS PRO PEDALS and YOKE on a linux machine ?
> >> if yes, are there any important installation notes ?
> >> if not, can you recommend on such equipment working well with flight
> >> gear on linux ?
> >> Thanks ahead,
> >> Yair.
> >
> > I have been using them for some years now. The only problem I've had
> > over several kernel 2.6 versions and for over year - After boot up, the
> > buttons and controls do not work.
> > To get them working, I have to unplug them and reinsert them, then
> > everything works OK. This has been the same on both x86 and x86_64
> > architectures, right up to the latest AM2 64x2 box and openSuSE 10.3
> > Alpha5. I reported the problem to the USB development group early on, but
> > got no reply. It seems there is some race condition that prevents them
> > being properly being initialised. I also did not find out which kernel
> > the problem appeared with, it seemed to have been when they changed the
> > input subsystem layer, 2.6.17-ish (???).
> > js_demo and jstest lists them all, but they are inoperative - vaulues
> > being static with control movements.
> > # js_demo
> > Joystick test program.
> > ~~~~~~~~~~~~~~~~~~~~~~
> > Joystick 0: "CH PRODUCTS CH FLIGHT SIM YOKE USB "
> > Joystick 1: "CH PRODUCTS CH PRO PEDALS USB "
> > Joystick 2 not detected
> > Joystick 3 not detected
> > Joystick 4 not detected
> > Joystick 5 not detected
> > Joystick 6 not detected
> > Joystick 7 not detected
> > +--------------------JS.0----------------------+--------------------JS.1-
> >---------------------+
> >
> > | Btns Ax:0 Ax:1 Ax:2 Ax:3 Ax:4 Ax:5 Ax:6 | Btns Ax:0 Ax:1 Ax:2
> >
> > +----------------------------------------------+-------------------------
> >---------------------+
> >
> > | 0000 +0.1 +0.1 -1.0 -1.0 -1.0 +0.0 +0.0 . | 0000 -1.0 -1.0 +0.0 .
> >
> > . . . . |
> >
> > # jstest /dev/input/js0
> > Driver version is 2.1.0.
> > Joystick (CH PRODUCTS CH FLIGHT SIM YOKE USB ) has 7 axes (X, Y, Z, Rx,
> > Ry, Hat0X, Hat0Y)
> > and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2,
> > PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
> > Testing ... (interrupt to exit)
> > Axes: 0: 3715 1: 4053 2:-32767 3:-32767 4:-32767 5: 0 6:
> > 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off
> > 8:off 9:off 10:off 11:off
> >
> > # jstest /dev/input/js1
> > Driver version is 2.1.0.
> > Joystick (CH PRODUCTS CH PRO PEDALS USB ) has 3 axes (X, Y, Z)
> > and 0 buttons ().
> > Testing ... (interrupt to exit)
> > Axes: 0:-32767 1:-32767 2: 675
> >
> > +0.0 +0.0 . | . . . . . . . . . . . | |
> >
> >
> > After replugging, values change with control movements as seen below.
> > # js_demo
> > Joystick test program.
> > ~~~~~~~~~~~~~~~~~~~~~~
> > Joystick 0: "CH PRODUCTS CH FLIGHT SIM YOKE USB "
> > Joystick 1 not detected
> > Joystick 2: "CH PRODUCTS CH PRO PEDALS USB "
> > Joystick 3 not detected
> > Joystick 4 not detected
> > Joystick 5 not detected
> > Joystick 6 not detected
> > Joystick 7 not detected
> > +--------------------JS.0----------------------+--------------------JS.2-
> >---------------------+
> >
> > | Btns Ax:0 Ax:1 Ax:2 Ax:3 Ax:4 Ax:5 Ax:6 | Btns Ax:0 Ax:1 Ax:2
> >
> > +----------------------------------------------+-------------------------
> >---------------------+
> >
> > | 0000 +0.3 +0.2 -1.0 -1.0 -1.0 +0.0 +0.0 . | 0000 -1.0 -1.0 +0.7 .
> >
> > . . . . |
> >
> > Regards
> > Sid.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users
