From: Dmitriy Geels <dmitriy.geels@gmail.com>
To: Anssi Hannula <anssi.hannula@gmail.com>
Cc: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>,
linux-input@vger.kernel.org
Subject: Re: How to use force feedback correctly?
Date: Wed, 18 Mar 2009 10:03:01 +0300 [thread overview]
Message-ID: <78f5d6bf0903180003i7504f4c7r36c0554f65c82cb2@mail.gmail.com> (raw)
In-Reply-To: <49BFA283.6000307@gmail.com>
2009/3/17 Anssi Hannula <anssi.hannula@gmail.com>:
>> 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.
Created bug report for ubuntu jaunty. https://bugs.launchpad.net/bugs/344673
This wasn't a problem for ubuntu, because kernels prior to 2.6.28 were
missing force feedback support for hid devices.
You can make this rule yourself, here is a good manual:
http://www.reactivated.net/writing_udev_rules.html
Or just wait, I will make this rule and post it to bug report.
prev parent reply other threads:[~2009-03-18 7:03 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
2009-03-18 7:03 ` Dmitriy Geels [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=78f5d6bf0903180003i7504f4c7r36c0554f65c82cb2@mail.gmail.com \
--to=dmitriy.geels@gmail.com \
--cc=alexander.stein@informatik.tu-chemnitz.de \
--cc=anssi.hannula@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).