mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: simon@mungewell.org
To: simon@mungewell.org
Cc: "Paul Sbarra" <sbarra.paul@gmail.com>,
	jkosina@suse.cz, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] hid: Add report descriptor for Logitech Driving Force wheel
Date: Sat, 2 Feb 2013 22:27:29 -0500	[thread overview]
Message-ID: <b81b48451e27b8f5c3ecdc121d749f59.squirrel@www.mungewell.org> (raw)
In-Reply-To: <eda86cfd7fd3f5878ef00e3e8a9de1c6.squirrel@www.mungewell.org>


> Hi Paul,
> I'm not following as to why you are patching the descriptor for the DFP,
> my understanding is that this is fully supported at the moment (as
> USB_DEVICE_ID_LOGITECH_DFP_WHEEL in the line after your patch).

Ah... you said 'Driving Force'.. not 'Driving Force Pro', but given the
confusing naming schemes I think I can be excused :-)
http://en.wikipedia.org/wiki/Gran_Turismo_official_steering_wheel#Model_comparison


However I do remember that there's a quirk with the logitech wheels that
they all pretend to be the same device, but some can be sent a magic
command which makes them disconnect and re-connect with a different USB ID
and with the larger steering range.

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=drivers/hid/hid-lg4ff.c;h=d7947c701f3063ac6c3683c29d3eca333b7ca1b0;hb=8b31849a113a8868eb2de692be5c9ecadae93ac9#l549


So in summary we need to be careful with "046d:c294 Logitech, Inc. Driving
Force"

Personally I have a Driving Force Pro, Driving Force Wireless and a G27
which all start with reporting this ID.

So a couple of questions:
1) Are you sure you have a "Driving Force"?
2) Does the ForceFeedback work for you?

Just for reference we moved the FF for the logitech wheels to hid-lg4ff
back in Aug 2011, I'm not sure which mainline kernel that was...

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=history;f=drivers/hid/hid-lg4ff.c;h=d7947c701f3063ac6c3683c29d3eca333b7ca1b0;hb=8b31849a113a8868eb2de692be5c9ecadae93ac9

Simon


      reply	other threads:[~2013-02-03  3:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-02 20:45 Paul Sbarra
2013-02-02 20:45 ` [PATCH 2/3] hid: Split accel, brake " Paul Sbarra
2013-02-02 20:45 ` [PATCH 3/3] hid: Calibrate Logitech Driving Force axes Paul Sbarra
     [not found]   ` <CAGf+dShLdE8hPYdfKw417hYyiox8cqCL3Jm6OQ3P4HfnE63CPw@mail.gmail.com>
2013-02-04  1:03     ` simon
2013-02-03  0:30 ` [PATCH 1/3] hid: Add report descriptor for Logitech Driving Force wheel simon
2013-02-03  3:27   ` simon [this message]

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=b81b48451e27b8f5c3ecdc121d749f59.squirrel@www.mungewell.org \
    --to=simon@mungewell.org \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbarra.paul@gmail.com \
    /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

all inboxes | Powered by JetHome®