From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161313AbXCNPCm (ORCPT ); Wed, 14 Mar 2007 11:02:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161314AbXCNPCm (ORCPT ); Wed, 14 Mar 2007 11:02:42 -0400 Received: from nf-out-0910.google.com ([64.233.182.191]:46793 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161313AbXCNPCj (ORCPT ); Wed, 14 Mar 2007 11:02:39 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pYJ5UOpc3Tcfqxl5hXS+L03KkDWd7kI+vdWoc7CCNC3LJ1g7jdYYa7G2VgckuvgAWfXFa2R9irhs1vkwRNvjqCS5+1Ftu2zJeaSmbsEO7SlZDkSgVvwCKE/04fU1aX6zvpr3iGvASUOjxxLxEMBFGqpbrHvhXNvLt7OKWmaoN9c= Message-ID: Date: Wed, 14 Mar 2007 11:02:37 -0400 From: "Dmitry Torokhov" To: "Jiri Slaby" Subject: Re: FF layer restrictions [Was: [PATCH 1/1] Input: add sensable phantom driver] Cc: "johann deneux" , "Linux kernel mailing list" , linux-input@atrey.karlin.mff.cuni.cz, "Anssi Hannula" In-Reply-To: <45F722CE.9000602@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2460126662758025813@fi.muni.cz> <45EEEAA3.50009@gmail.com> <4af2d03a0703130919nb4893b1ja9ec795dcf4bf53c@mail.gmail.com> <38b3b7c0703131450v2646e63fj2be4b9dda7f928c0@mail.gmail.com> <45F722CE.9000602@gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 3/13/07, Jiri Slaby 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. > > > maybe we should change the API. I don't think there are many > > applications using force feedback yet, so maybe that should be ok? > > > > If we change the API, we should remove the assumption that a device has > > at most two axes to render effects. We could for instance have a > > magnitude argument for each axis which is capable of rendering effects. > > That might be necessary even for more common gaming devices like racing > > wheels: One can think pedals could also be capable of force feedback > > some day, not just the steering wheel. > > I can do that, but in that case, I need to know how people (especially those > input one) want me to do... > Since we have no idea how many programs (if any) are using force feedback interface I would be wary of changing existing effcets and rather add new set of 3D effects. Do we have any idea if there any users of FF out there? -- Dmitry