From: Anssi Hannula <anssi.hannula@gmail.com>
To: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
Cc: linux-input@vger.kernel.org
Subject: Re: How to use force feedback correctly?
Date: Tue, 17 Mar 2009 15:15:47 +0200 [thread overview]
Message-ID: <49BFA283.6000307@gmail.com> (raw)
In-Reply-To: <200903161142.12123.alexander.stein@informatik.tu-chemnitz.de>
Alexander Stein wrote:
> Hello,
Hi!
> I've read the documentation about force feedback in
> Documentation/input/ff.txt. But I'm rather unsure how to use it actually. So
> far I understood this you have to use /dev/input/eventX to access your ff-
> device. But normally only root has read and write access to this device files,
> while a joystick is used normally using /dev/input/jsX which can be used by a
> non-root user.
>
> So my actual question is: How can I use force feedback of a joystick without
> setting global read/write permissions to /dev/input/eventX?
The distribution should configure joystick eventX devices to
either have global read/write access, or read/write access for one group
(which the user is in), or have it chown the device to logged-in user,
depending on distribution conventions.
One can identify joystick devices from other eventX devices with udev
variable ENV{ID_CLASS}="joystick", or with existence of
"/dev/input/by-path/*-event-joystick", which is a symlink to the eventX
device.
On Mandriva Linux, permissions are granted to logged-in user with
pam_console / ConsoleKit, with /dev/input/by-path/*-event-joystick.
> Or may I even be
> able to use force feedback using /dev/input/jsX?
Nope.
> Other thing: Is it possible that on line 52 in Documentation/input/ff.txt the
> declaration of the features array is wrong?
>> #52 unsigned long features[1 + FF_MAX/sizeof(unsigned long)];
> IMO it has to be declared like this:
>> unsigned long features[1 + FF_MAX/ (8 * sizeof(unsigned long))];
> Which creates actually a Bit array, not an Byte array.
Right, seems to be wrong.
--
Anssi Hannula
next prev parent reply other threads:[~2009-03-17 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 10:42 How to use force feedback correctly? Alexander Stein
2009-03-17 13:15 ` Anssi Hannula [this message]
2009-03-18 7:03 ` Dmitriy Geels
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=49BFA283.6000307@gmail.com \
--to=anssi.hannula@gmail.com \
--cc=alexander.stein@informatik.tu-chemnitz.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;
as well as URLs for NNTP newsgroup(s).