From nobody Sun Apr 19 12:15:34 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D3B6DC433EF for ; Fri, 1 Jul 2022 11:30:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234882AbiGALaI (ORCPT ); Fri, 1 Jul 2022 07:30:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60582 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231261AbiGALaF (ORCPT ); Fri, 1 Jul 2022 07:30:05 -0400 X-Greylist: delayed 3041 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Fri, 01 Jul 2022 04:30:05 PDT Received: from smarthost06.digicable.hu (smarthost06.digicable.hu [94.21.128.16]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0A074814BF for ; Fri, 1 Jul 2022 04:30:05 -0700 (PDT) Received: from [92.249.128.185] (helo=relay03.digicable.hu) by smarthost06.digicable.hu with esmtp id 1o7E3W-0000jp-GH for ; Fri, 01 Jul 2022 12:39:22 +0200 Received: from [178.164.181.62] (helo=root.otthon) by relay03.digicable.hu with esmtpa id 1o7E3W-0003wA-8a for ; Fri, 01 Jul 2022 12:39:22 +0200 Received: by root.otthon (Postfix, from userid 1000) id 1B2B680CDA38; Fri, 1 Jul 2022 12:39:22 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by root.otthon (Postfix) with ESMTP id 06ABF101FD73D for ; Fri, 1 Jul 2022 12:39:22 +0200 (CEST) Date: Fri, 1 Jul 2022 12:39:21 +0200 (CEST) From: Greg T To: linux-kernel@vger.kernel.org Subject: |Question] iforce Boeder Force Feedback Wheel Message-ID: <495ce212-addc-8ab1-a851-4fd5f6c5c8d9@gmail.com> MIME-Version: 1.0 X-Original: 178.164.181.62 X-Original: 92.249.128.185 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" I'm trying to make a Boeder Force Feedback Wheel work using its serial=20 interface (/dev/ttyS0). 1. As iforce-main.c identifies it as "Unknown I-Force Device=20 [%04x:%04x]", I think those placeholders should be replaced by vendor=20 and product ids, but aren't. 2. Here's a patch to make it recognized: --- drivers/input/joystick/iforce/iforce-main.c.orig 2022-06-14 19:21:30.00= 0000000 +0200 +++ drivers/input/joystick/iforce/iforce-main.c 2022-06-30 18:52:38.0220397= 42 +0200 @@ -50,6 +50,7 @@ { 0x046d, 0xc291, "Logitech WingMan Formula Force", btn_wheel, abs_wheel= , ff_iforce }, { 0x05ef, 0x020a, "AVB Top Shot Pegasus", btn_joystick_avb, abs_avb_peg= asus, ff_iforce }, { 0x05ef, 0x8884, "AVB Mag Turbo Force", btn_wheel, abs_wheel, ff_iforc= e }, + { 0x05ef, 0x8886, "Boeder Force Feedback Wheel", btn_wheel, abs_wheel, f= f_iforce }, { 0x05ef, 0x8888, "AVB Top Shot Force Feedback Racing Wheel", btn_wheel, = abs_wheel, ff_iforce }, //? { 0x061c, 0xc0a4, "ACT LABS Force RS", btn_wheel= , abs_wheel, ff_iforce }, //? { 0x061c, 0xc084, "ACT LABS Force RS", btn_wheel, abs_wheel, ff_iforce= }, 3. There's a problem that the GAS and BRAKE values (in jstest) start=20 from -32767, not 0, and it causes menus in games like RVGL to=20 malfunction and you have to press the pedal halfway while using a=20 menu with keyboard as a really unpleasant workaround. The below patches eliminate that problem, but I'm not sure if it's a=20 kernel or user space problem or just my ignorance. (With its Windows=20 9x driver, by default, both pedals are on the Y-axis, but move away=20 from 0 in the opposite directions.) --- drivers/input/joystick/iforce/iforce-main.c.orig 2022-06-14 19:21:30.00= 0000000 +0200 +++ drivers/input/joystick/iforce/iforce-main.c 2022-07-01 09:49:58.3449700= 61 +0200 @@ -350,7 +351,7 @@ case ABS_THROTTLE: case ABS_GAS: case ABS_BRAKE: - input_set_abs_params(input_dev, t, 0, 255, 0, 0); + input_set_abs_params(input_dev, t, 0, 511, 0, 0); break; =20 case ABS_RUDDER: --- drivers/input/joystick/iforce/iforce-packets.c.orig 2022-06-14 19:21:30= .000000000 +0200 +++ drivers/input/joystick/iforce/iforce-packets.c 2022-07-01 09:58:10.0613= 54919 +0200 @@ -178,8 +178,8 @@ case 0x03: /* wheel position data */ input_report_abs(dev, ABS_WHEEL, (__s16) get_unaligned_le16(data)); - input_report_abs(dev, ABS_GAS, 255 - data[2]); - input_report_abs(dev, ABS_BRAKE, 255 - data[3]); + input_report_abs(dev, ABS_GAS, 510 - data[2]); + input_report_abs(dev, ABS_BRAKE, 510 - data[3]); =20 iforce_report_hats_buttons(iforce, data); =20 4. Force feedback seems to work from fftest (at least some of the=20 functions), but when using ff in RVGL or VDrift, the system freezes=20 and I can't find anything related in journalctl after hard resetting.=20 How should I debug this problem? It's on Fedora release 34. Kernel/iforce source is from=20 https://gitlab.com/cki-project/kernel-ark/-/tree/fedora-5.17/drivers/input/= joystick/iforce and the kernel-devel-5.17.12-100.fc34.x86_64 package.