linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hiran Chaudhuri <hiran.chaudhuri@gmx.net>
To: linux-input@vger.kernel.org
Subject: Improvement for Joystick and Force Feedback section
Date: Thu, 19 Jan 2023 20:27:56 +0100	[thread overview]
Message-ID: <5bbc7e785a6ca2a58e565dae9394540f6a315193.camel@gmx.net> (raw)

Hello there,

I am neither developer nor committer on the linux kernel. But trying to
figure out the kernel support for my Microsoft Sidewinder Force
Feedback 2 joystick I found two things that might get improved in the
kernel documentation. Maybe someone could update it with below
information:

1)
https://www.kernel.org/doc/html/latest/input/joydev/joystick.html#microsoft-sidewinder-joysticks
The Microsoft Sidewinder Force Feedback 2 joystick is not listed at
all, but after playing around I was able to make it work. So it makes
sense to extend the list with that model.

2) https://www.kernel.org/doc/html/latest/input/ff.html#does-it-work
When trying fftest it is important to use the correct device node
/dev/input/eventXX. Unfortunately I was fiddling for a long time with
the wrong node (it may even change depending on the hot-plugging of the
USB devices).

Therefore first run the command `evtest`, which scans all
/dev/input/event* nodes and will print the devices found. From that
pick the correct file, then run `fftest`.

Also the command `ffcfstress` is a very nice test to verify the
joystick works.

Best regards

Hiran

             reply	other threads:[~2023-01-19 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 19:27 Hiran Chaudhuri [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-16 20:09 Improvement for Joystick and Force Feedback section Hiran Chaudhuri

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=5bbc7e785a6ca2a58e565dae9394540f6a315193.camel@gmx.net \
    --to=hiran.chaudhuri@gmx.net \
    --cc=linux-input@vger.kernel.org \
    /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).