linux-kernel - Re: FF layer restrictions [Was: [PATCH 1/1] Input: add sensable phantom driver]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Mar 2007 22:51:34 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	johann deneux <johann.deneux@...il.com>
CC:	Dmitry Torokhov <dtor@...ightbb.com>,
	"STenyaK (Bruno González)" 
	<stenyak@...il.com>, Anssi Hannula <anssi.hannula@...il.com>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	linux-input@...ey.karlin.mff.cuni.cz
Subject: Re: FF layer restrictions [Was: [PATCH 1/1] Input: add sensable phantom
 driver]

johann deneux napsal(a):
> On 3/27/07, Jiri Slaby <jirislaby@...il.com> wrote:
>> johann deneux napsal(a):
>> > Are we
>> > misunderstanding eachother maybe? By "vector" I mean a triplet of
>> > numbers, when you say "torques" and "forces vector", do you mean that
>> > each effect is composed of a bunch of torques?
>>
>> Ok, let's make things a little bit clear. I need to put somehow 3 short
>> values (torques -- to tell 3 motors how much to spin around) into the
>> kernel
>> space via ff layer. I computed them using FP in US from forces (3d
>> vector)
>> and the problem is, that I don't know how to transform torques to
>> plane(s)
>> and dir and then back to torques -- this is what I can't figure out,
>> since I
>> have no longer vector -- 3 values for each axis, which says how big is
>> the
>> force in each axis -- but I have values (no axis) specific to each motor.
> 
> I think I'm starting to understand. Looking back at the url you gave,
> it appears your device is some kind of articulated arm, possibly with
> one or more motor(s) at each joint. You are not really dealing with a
> single torque applied at one point in space, but several torques
> applied at several points in space.

Exactly as you write. Sorry for my previous bad definitions.

> For this particular device you have three values, but for other
> devices it could just as well be any other number, right?

Correct.

> A realistic example would be a robot arm with claws, there would be a
> torque for each joint, and some more for the claws.

For instance.

Ok, so how to deal with these devices? Does anybody have some idea? That's
what I was talking about somewhere in the beginning of this thread, the raw
values, because it seems too specific for letting kernel to cope with each
of these devices separately, but there might be a better idea in somebody's
head? But raw is ugly...

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/