From: "Michal Malý" <madcatxster@gmail.com>
To: simon@mungewell.org
Cc: Michael Bauer <michael@m-bauer.org>,
linux-input@vger.kernel.org, peter@slim-one.de
Subject: Re: [PATCH] Fix autocentering command in hid-lgff driver
Date: Wed, 29 Jun 2011 23:37:06 +0200 [thread overview]
Message-ID: <10412007.kslt1z6EXa@qosmio-x300> (raw)
In-Reply-To: <b4f74749ffdf35c88a0523a6a5f1a31b.squirrel@host171.canaca.com>
> Can you (someone?) clarify which wheels do not have a command to switch
> into 'native mode' (which causes a USB ID change) and do these wheels use
> a unified brake/acc.?
> Do any wheels have a 'native mode' which stay with the generic USB ID?
To my knowledge all wheels except original Driving Force and Formula Force
have the fallback and native mode. Every Logitech wheel in fallback mode
reports PID 0x294 which is the PID of the original Driving Force wheel. If
DFP/G25/G27/DFGT receives specific command, it simulates reconnect and reports
its "real" PID upon reconnection.
> Wouldn't the device descriptor only be re-written for the new USB ID's in
> 'native' mode.
DF/DFP/FEX hides the separate throttle and brake axes in the original
descriptor so we definitely need to replace it. G25/27 don't need such a hack,
I don't know how about DFGT or Momo, I'll try to find that out.
IMHO we need to replace the descriptor only if the wheel has PID 0x294 and is
either DF or FEX. DFP has PID 0x298 and needs a fixed descriptor too.
> If we force the 'native command' to be issued then we might affect/prevent
> any 'old game' play.
Problem is that not all wheels actually have the native mode as I mentioned
above, but all support separate pedal axes. Unless we somehow read the
anonymous fields reported by the original descriptor, I guess we'll have to
decide whether to have separate or combined pedal axes.
Another (rather hackish) way around this would be a "combined" value in /sys
interface. When set to 1, we'd trigger reconnection (can we do that?) and not
replace the descriptor (or replace it in case of G25/27).
I've given some thought bypassing the ff-memless driver and I don't think it's
necessary. We can patch ff-memless and add support for the missing effects. I
guess that passing the device-specific commands like effect reset, G27 leds and
range setting could be done via /sys interface too.
However that's just a thought...
Michal
next prev parent reply other threads:[~2011-06-29 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 20:42 [PATCH] Fix autocentering command in hid-lgff driver Michal Malý
2011-06-14 21:20 ` simon
2011-06-14 22:26 ` Michal Malý
2011-06-14 23:16 ` simon
2011-06-15 0:03 ` Michal Malý
[not found] ` <4429494.nOUqc25rPl@qosmio-x300>
2011-06-15 21:56 ` Michal Malý
[not found] ` <1908821.jaYXT1Nn2e@qosmio-x300>
[not found] ` <da2b7e45ed001b587d49824944b802b8.squirrel@host171.canaca.com>
[not found] ` <201106262207.23918.michael@m-bauer.org>
2011-06-27 16:15 ` simon
2011-06-27 20:58 ` Michal Malý
2011-06-29 9:28 ` Michael Bauer
2011-06-29 15:23 ` Michael Bauer
2011-06-29 15:50 ` simon
2011-06-29 21:37 ` Michal Malý [this message]
2011-07-05 23:04 ` Michal Malý
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=10412007.kslt1z6EXa@qosmio-x300 \
--to=madcatxster@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=michael@m-bauer.org \
--cc=peter@slim-one.de \
--cc=simon@mungewell.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).