From: simon@mungewell.org
To: Anisha Kaul <born.rebel.83@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: fftest: Force feedback doesn't work in native mode
Date: Wed, 18 Jan 2012 11:39:00 -0500 [thread overview]
Message-ID: <2a8f304621a47c9b8468f5aa0ae7f4c5.squirrel@mungewell.org> (raw)
In-Reply-To: <CAM1yFZ8_VEhsY9qe6Rt_8Ojb89CUUMskQdGDv5GomEVGNBDvxQ@mail.gmail.com>
> On 18 January 2012 03:58, <simon@mungewell.org> wrote:
>> Do you have the appropriate FF module built and loading in your kernel,
>> it
>> was recently moved to be enabled with 'LOGIWHEELS_FF' and is supported
>> by
>> the code in 'drivers/hid/hid-lg4ff.c'
>
> And also, I don't have "hid-lg4ff.c" in this
> "linux-dopx:/usr/src/linux-2.6.34-12/drivers/hid" path. I have
> "hid-lg3ff.c" etc.
> Is it responsible for the force feedback not working in the native mode?
> Will I have to compile the kernel or something? :( :(
>
> Ah, or simply download that file and put its name in the respective
> Makefile? Not sure.
If you don't have it then it is probably easiest grabbing a more recent
pre-built kernel from your distribution. I suspect that SuSE has somewhere
for getting 'leading edge' kernels.
'hid-lg4ff' was improved by Michal back in August to include support for
all Logitech wheel and run them in the native mode (to get 900' rotation
etc).
A change log is here:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=history;f=drivers/hid/hid-lg4ff.c;h=6ecc9e2204409c1451e90086a4edd7f0639cdb01;hb=ccb19d263fd1c9e34948e2158c53eacbff369344
Simon
next prev parent reply other threads:[~2012-01-18 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 7:58 fftest: Force feedback doesn't work in native mode Anisha Kaul
2012-01-18 16:39 ` simon [this message]
2012-01-19 6:27 ` Anisha Kaul
2012-01-19 7:29 ` simon
2012-01-19 7:47 ` Anisha Kaul
[not found] ` <747fc1e52c224cb3cc1c4b37c9de9bb7.squirrel@mungewell.org>
2012-01-20 6:29 ` Anisha Kaul
2012-01-20 18:50 ` simon
2012-01-21 8:09 ` Anisha Kaul
2012-01-24 12:38 ` Anisha Kaul
-- strict thread matches above, loose matches on Subject: below --
2012-01-18 7:32 Anisha Kaul
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=2a8f304621a47c9b8468f5aa0ae7f4c5.squirrel@mungewell.org \
--to=simon@mungewell.org \
--cc=born.rebel.83@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).