From: Peter <peter@slim-one.de>
To: linux-input <linux-input@vger.kernel.org>
Subject: [Fwd: Re: [PATCH] G25_support]
Date: Tue, 22 Mar 2011 11:20:52 +0100 [thread overview]
Message-ID: <1300789252.5513.46.camel@slim-one-desktop> (raw)
[-- Attachment #1: Type: text/plain, Size: 9 bytes --]
CC vger.
[-- Attachment #2: Forwarded message - Re: [PATCH] G25_support --]
[-- Type: message/rfc822, Size: 10915 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 2165 bytes --]
Hi,
if Michal and Christophe want to test this, they have to set their
G25/DFP into native mode via G25manage
(http://wiki.vdrift.net/Logitech_G25_support). I rewrote the tool so
that only nativemode and range can be set (the original contained
debugging/calibration which isn't really necessary for a device that
calibrates itself when connected) for both the G25/G27 and the DFP. I
attached the rewritten version and proper udev-rules (DFP-rule not
tested but should work fine).
I don't know if that stuff should be integrated into the kernel (at
least the initialization), too. Without that, the wheels only report 2
axis and are limited to somewhat 270 degrees instead of 4 axis and 900
degrees.
As for wine, it needs to be patched, too, else it will feel more like a
steamhammer. I'm already writing with two of the devs, and it seems they
got it fixed.
Regards, Peter
On Tue, 2011-03-22 at 10:40 +0100, Jiri Kosina wrote:
> On Mon, 21 Mar 2011, Simon Wood wrote:
>
> > From: Peter <peter@slim-one.de>
> >
> > Small patch to add support for the G25/G27 by adding USB ID's
> > as suggested by Peter.
> >
> > Boots but otherwise untested as I don't have hardware, .debs for
> > kernel (2.6.38) here if want to test/run Ubuntu/Debian:
> > http://www.mungewell.org/Logitech_Wii_Wheel/
> >
> > Reported-by: Peter <peter@slim-one.de>
> > Signed-off-by: Simon Wood <simon@mungewell.org>
> > ---
> > drivers/hid/hid-lgff.c | 2 ++
> > 1 files changed, 2 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/hid/hid-lgff.c b/drivers/hid/hid-lgff.c
> > index 90d0ef2..f099079 100644
> > --- a/drivers/hid/hid-lgff.c
> > +++ b/drivers/hid/hid-lgff.c
> > @@ -73,6 +73,8 @@ static const struct dev_type devices[] = {
> > { 0x046d, 0xc293, ff_joystick },
> > { 0x046d, 0xc294, ff_wheel },
> > { 0x046d, 0xc295, ff_joystick },
> > + { 0x046d, 0xc298, ff_wheel },
> > + { 0x046d, 0xc299, ff_wheel },
> > { 0x046d, 0xca03, ff_wheel },
> > };
>
> You are right that missing entries in this struct for devices which have
> LG_FF flag set doesn't make too much sense.
>
> Adding Michal and Chritophe to CC, as they should have the HW to test.
>
[-- Attachment #2.1.2: G25manage.zip --]
[-- Type: application/zip, Size: 4749 bytes --]
reply other threads:[~2011-03-22 10:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1300789252.5513.46.camel@slim-one-desktop \
--to=peter@slim-one.de \
--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