mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: aris@cefetpr.br
To: Micah Dowty <micah@navi.cx>
Cc: aris@cathedrallabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Force feedback support for uinput
Date: Fri, 12 Nov 2004 10:09:12 -0200	[thread overview]
Message-ID: <20041112120852.GA25736@cefetpr.br> (raw)
In-Reply-To: <20041110163751.GA13361@navi.cx>

> Hello,
Hi!

> This patch adds support to uinput for Linux's force feedback interface.
> With these changes, it's possible to write drivers for force feedback
> joysticks and similar devices in userspace. It also adds a way to set
> the physical path of devices created via uinput, and it has a couple
> trivial bugfixes.
nice!

> My solution is to have a special input event, outside the range
> defined by the input system, that uinput sends to the application
> to signal when a callback has been entered. A particular callback
> invocation is identified by a request ID stored in this event.
(snip)
> +/* This is the new event type, used only by uinput.
> + * 'code' is UI_FF_UPLOAD or UI_FF_ERASE, and 'value'
> + * is the unique request ID. This number was picked
> + * arbitrarily, above EV_MAX (since the input system
> + * never sees it) but in the range of a 16-bit int.
> + */
> +#define EV_UINPUT		0x0101
I guess it should be moved to input.h with other types of events.

> +/* To write a force-feedback-capable driver, the upload_effect
> + * and erase_effect callbacks in input_dev must be implemented.
> + * The uinput driver will generate a fake input event when one of
> + * these callbacks are invoked. The userspace code then uses
> + * ioctls to retrieve additional parameters and send the return code.
> + * The callback blocks until this return code is sent.
(snip)
what about moving this long comment to Documentation/input/uinput.txt?

the rest of the patch seems fine to me

thanks,

(p.s.: sorry for the delay and the dup that will follow. my server is
offline due adsl problems and the first answer is stuck there :)

--
Aristeu


  reply	other threads:[~2004-11-12 12:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 16:37 Micah Dowty
2004-11-12 12:09 ` aris [this message]
2004-11-21  8:54   ` Micah Dowty
2004-11-22 10:38     ` Aristeu Sergio Rozanski Filho
2004-11-22 19:47       ` Micah Dowty
2004-11-22 19:55         ` Aristeu Sergio Rozanski Filho

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=20041112120852.GA25736@cefetpr.br \
    --to=aris@cefetpr.br \
    --cc=aris@cathedrallabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=micah@navi.cx \
    /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

Powered by JetHome