From: Jiri Slaby <jirislaby@gmail.com>
To: Anssi Hannula <anssi.hannula@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
johann deneux <johann.deneux@gmail.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: FF layer restrictions [Was: [PATCH 1/1] Input: add sensable phantom driver]
Date: Wed, 14 Mar 2007 19:15:33 +0100 [thread overview]
Message-ID: <45F83BC5.7020606@gmail.com> (raw)
In-Reply-To: <45F83930.4060401@gmail.com>
Anssi Hannula napsal(a):
> Jiri Slaby wrote:
>> Dmitry Torokhov napsal(a):
>>> On 3/13/07, Jiri Slaby <jirislaby@gmail.com> wrote:
>>>> Why did you remove all Cced people? Anyway I filtered some of them out
>>>>
>>>> johann deneux napsal(a):
>>>>> You are right, the direction in ff_effect is meant to be an angle.
>>>>> A dirty solution would be to use the 16 bits as two 8-bits angles. Or
>>>> That would be a problem as I need 3x 16bits.
>
> Interesting. What kind of device is that? i.e. what is the third
> direction value?
6DOF sensable phantom:
http://www.sensable.com/haptic-phantom-premium-6dof.htm
X,Y,Z,RX,RY,RZ+BUT as inputs
X,Y,Z motors as FF
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
next prev parent reply other threads:[~2007-03-14 18:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 11:36 [PATCH 1/1] Input: add sensable phantom driver Jiri Slaby
2007-03-07 14:47 ` Dmitry Torokhov
2007-03-07 16:38 ` Jiri Slaby
2007-03-07 16:50 ` Greg KH
2007-03-07 16:56 ` Dmitry Torokhov
2007-03-13 16:19 ` Jiri Slaby
[not found] ` <38b3b7c0703131450v2646e63fj2be4b9dda7f928c0@mail.gmail.com>
2007-03-13 22:16 ` FF layer restrictions [Was: [PATCH 1/1] Input: add sensable phantom driver] Jiri Slaby
2007-03-14 15:02 ` Dmitry Torokhov
2007-03-14 16:43 ` Jiri Slaby
2007-03-14 16:45 ` Jiri Slaby
2007-03-14 18:04 ` Anssi Hannula
2007-03-14 18:15 ` Jiri Slaby [this message]
2007-03-14 18:47 ` STenyaK (Bruno González)
2007-03-14 19:12 ` STenyaK (Bruno González)
2007-03-14 19:13 ` Dmitry Torokhov
2007-03-14 19:18 ` STenyaK (Bruno González)
2007-03-15 20:51 ` johann deneux
2007-03-15 21:06 ` STenyaK (Bruno González)
2007-03-21 13:31 ` Jiri Slaby
2007-03-21 13:32 ` Jiri Slaby
2007-03-21 19:02 ` johann deneux
2007-03-21 19:22 ` Dmitry Torokhov
2007-03-21 20:04 ` Jiri Slaby
2007-03-21 22:03 ` johann deneux
2007-03-22 15:50 ` Dmitry Torokhov
2007-03-27 12:20 ` Jiri Slaby
2007-03-27 18:36 ` johann deneux
2007-03-27 20:11 ` Jiri Slaby
2007-03-27 20:43 ` johann deneux
2007-03-27 20:51 ` Jiri Slaby
2007-03-27 21:34 ` johann deneux
2007-03-28 3:08 ` Dmitry Torokhov
2007-03-28 9:28 ` Jiri Slaby
2007-03-28 22:16 ` Jiri Slaby
2007-03-28 22:22 ` Jiri Slaby
2007-03-30 16:46 ` Dmitry Torokhov
2007-03-30 19:11 ` Anssi Hannula
2007-03-15 20:43 ` johann deneux
2007-03-16 16:28 ` Pavel Machek
2007-03-17 7:28 ` johann deneux
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=45F83BC5.7020606@gmail.com \
--to=jirislaby@gmail.com \
--cc=anssi.hannula@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=johann.deneux@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@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).