From: Richard Bolkey <rbolkey@cs.utexas.edu>
To: Anssi Hannula <anssi.hannula@gmail.com>
Cc: johann deneux <johann.deneux@gmail.com>,
linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: Logitech Spring FF
Date: Tue, 10 Apr 2007 00:45:58 -0500 [thread overview]
Message-ID: <461B2496.8010304@cs.utexas.edu> (raw)
In-Reply-To: <4617B392.4010704@gmail.com>
First off, I've never made a patch before, which I guess I better learn,
but for now if anyone wants to add the device_type for the Logitech
Force 3D Pro Joystick to hid-lgff.c, it's { 0x046d, 0xc286, ff_joystick }.
Now for a few follow up questions (this is a whole lot of new stuff, so
bear with me).
1) I'm gathering that Logitech keeps their hid reports secret and
non-standard, or else I'd just be using the HID PID driver? So, were
the values in the reports found in hid_lgff_play discovered through
trial and error? How would I find what the report for FF_SPRING should
look like?
2) Previous question assumes that is where I should implement the effect
since ml->play_effect is referencing that function in ff_memless.c. But
it sounded like Anssi was recommending doing a spring->constant
conversion akin to what looks like a periodic->rumble conversion in
ml_combine_effects?
Thanks,
Rick
next prev parent reply other threads:[~2007-04-10 5:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <461117A0.80905@cs.utexas.edu>
[not found] ` <4615D762.4090206@it.uu.se>
[not found] ` <4616DC56.80301@cs.utexas.edu>
2007-04-07 7:16 ` Logitech Spring FF johann deneux
2007-04-07 15:06 ` Anssi Hannula
2007-04-10 5:45 ` Richard Bolkey [this message]
2007-04-10 6:31 ` Dmitry Torokhov
2007-04-10 9:51 ` johann deneux
2007-04-11 2:55 ` Logitech Spring FF (effect on/off) Richard Bolkey
2007-04-11 3:01 ` Anssi Hannula
2007-05-12 10:22 ` johann deneux
2007-04-10 12:21 ` Logitech Spring FF 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=461B2496.8010304@cs.utexas.edu \
--to=rbolkey@cs.utexas.edu \
--cc=anssi.hannula@gmail.com \
--cc=johann.deneux@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.