linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "johann deneux" <johann.deneux@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Dmitry Torokhov <dtor@insightbb.com>,
	stenyak@gmail.com, linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [RFC 1/2] Input: ff, add FF_RAW effect
Date: Thu, 19 Apr 2007 06:25:41 +0200	[thread overview]
Message-ID: <38b3b7c0704182125q1928c5barad21ed603088ab04@mail.gmail.com> (raw)
In-Reply-To: <462688AB.4060707@gmail.com>

On 4/18/07, Jiri Slaby <jirislaby@gmail.com> wrote:
> johann deneux napsal(a):
> > Jiri,
> >
> > Which solution did you chose to implement? From what I remember, we
> > last discussed Dmitry's idea of specifying an axis for an effect, then
> > combine several effects to achieve complex effects.
>
> I think you mean motor instead of axis, because I don't push real axes to
> the devices, but motor's torques...
>

Yes, sorry, I meant motor.

-- 
Johann

  reply	other threads:[~2007-04-19  4:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 20:01 [RFC 1/2] Input: ff, add FF_RAW effect Jiri Slaby
2007-04-17 20:02 ` [RFC 2/2] Input: phantom, add a new driver Jiri Slaby
2007-04-20  6:07   ` Andrew Morton
2007-04-20  9:01     ` Jiri Slaby
2007-04-18 20:00 ` [RFC 1/2] Input: ff, add FF_RAW effect johann deneux
2007-04-18 21:07   ` Jiri Slaby
2007-04-19  4:25     ` johann deneux [this message]
2007-04-19  4:58       ` Dmitry Torokhov
2007-04-19 15:38         ` Jiri Slaby
2007-04-19 16:02           ` Dmitry Torokhov
2007-04-22 12:57             ` Jiri Slaby
2007-04-26 16:02               ` Dmitry Torokhov
2007-04-26 23:24                 ` Jiri Slaby
2007-04-23 19:30             ` Jiri Slaby
2007-04-26 15:58               ` Dmitry Torokhov

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=38b3b7c0704182125q1928c5barad21ed603088ab04@mail.gmail.com \
    --to=johann.deneux@gmail.com \
    --cc=dtor@insightbb.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stenyak@gmail.com \
    /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).