From: Dario Pagani <dario.pagani.146@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org, kimi.h.kuparinen@gmail.com
Subject: Re: [PATCH] HID: support for initialization of some Thrustmaster wheels
Date: Sun, 14 Mar 2021 11:48:49 +0100 [thread overview]
Message-ID: <665a7a24-bc18-46e2-dee6-cb08f4a7b973@gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2103081458550.12405@cbobk.fhfr.pm>
Il 08/03/21 15:00, Jiri Kosina ha scritto:
> - I don't think we need to have this in a separate driver, is there a
> substantial reason why it can't be folded into hid-thrustmaster proper?
I didn't add the init code to the hid-tmff as the ff stands for force
feedback and hid-tminit does a completely different job.
However there are no significant reasons to avoid folding the two logics
in a common module hid-tmff or hid-thrustmaster.
> - Looking at what the code actually does, it seems like this could
> completely be done in userspace via libusb as a hook in udev when such
> device is plugged in, can't it?
Yes indeed Kim wrote a python script
(https://github.com/Kimplul/py-tminit) that does the same job via libusb.
One can argue that when the joystick is attached and appears like a
"Thrustmaster FFB Wheel" is, as far as we know, useless as the hid
descriptor is broken for the axis and some features, like changing the
range via LEFT|RIGHT + MODE button, seem to not work at all. So with a
kernel driver built-in one could just plug a supported wheel and have at
least a semi-functional joystick correctly identified by its model name
out of the box without installing anything else on the system. (I say
semi-functional because without force feedback support for the specific
joystick the wheel remains stiff to steer)
next prev parent reply other threads:[~2021-03-14 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 9:00 [PATCH] HID: support for initialization of some Thrustmaster wheels Dario Pagani
2021-03-08 14:00 ` Jiri Kosina
2021-03-14 10:48 ` Dario Pagani [this message]
2021-03-19 13:11 ` Jiri Kosina
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=665a7a24-bc18-46e2-dee6-cb08f4a7b973@gmail.com \
--to=dario.pagani.146@gmail.com \
--cc=jikos@kernel.org \
--cc=kimi.h.kuparinen@gmail.com \
--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).