From: Peter Hutterer <peter.hutterer@who-t.net>
To: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Documentation: Input: Add uinput documentation
Date: Mon, 27 Mar 2017 11:06:11 +1000 [thread overview]
Message-ID: <20170327010611.GA21915@jelly> (raw)
In-Reply-To: <20170326164821.10928-2-marcos.souza.org@gmail.com>
On Sun, Mar 26, 2017 at 01:48:12PM -0300, Marcos Paulo de Souza wrote:
> Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
> ---
> v2 -> v3:
> Changes in libevdev's description (suggested by Peter)
> Added uinput version check when using the old interface (suggested by Peter)
> Removed section numbers from sections, sphinx creates these indexes
> (suggestion by Jon)
>
> v1 -> v2:
> Changes all over the place, including better descriptions (suggested by Peter)
> Added comments about the need of a sleep call (suggested by Peter)
>
[...]
tested mouse/keyboard - works as expected, thanks. I found it slightly
confusing though that the mouse example wasn't wrapped in main() but still had a
return 0 at the bottom. This code will never change once it's in the doc, so
I'm not sure skipping things is really that useful here.
> +uinput old interface
> +--------------------
> +
> +Before uinput version 5, there wasn't a proper ioctl to setup a virtual device.
> +In this case, the user neesa to fill a different struct and call write o the
> +uinput file descriptor to configure the new uinput device.
> +
> +.. code-block:: c
> +
> + #include <linux/uinput.h>
> +
> + /* emit function is identical to of the first example */
> +
> + struct uinput_user_dev uud;
> + int version;
> +
> + fd = open("/dev/uinput", O_WRONLY | O_NONBLOCK);
> + ioctl(fd, UI_GET_VERSION, &version);
> +
> + if (version < 5) {
this won't work on all kernels. UI_GET_VERSION was added in version 4, on
kernels before you get rc == -1 and errno EINVAL. You can only check
for >= 4. Please make sure the example compiles and works on an older
kernel, otherwise there's no point shipping it.
Cheers,
Peter
> + /*
> + * the ioctls below enables the to be created device to key
> + * events, in this case the space key
> + */
> + ioctl(fd, UI_SET_EVBIT, EV_KEY);
> + ioctl(fd, UI_SET_KEYBIT, KEY_SPACE);
> +
> + memset(&uud, 0, sizeof(uud));
> + snprintf(uud.name, UINPUT_MAX_NAME_SIZE, "uinput old interface");
> + write(fd, &uud, sizeof(uud));
> +
> + ioctl(fd, UI_DEV_CREATE);
> +
> + /*
> + * On UI_DEV_CREATE the kernel creates the device nodes for this device.
> + * Insert a pause so that userspace has time to detect, initialize the
> + * new device, and can start to listen to events from this device
> + */
> + sleep(1);
> +
> + /* key press, report the event, send key release, and report again */
> + emit(EV_KEY, KEY_SPACE, 1);
> + emit(EV_SYN, SYN_REPORT, 0);
> + emit(EV_KEY, KEY_SPACE, 0);
> + emit(EV_SYN, SYN_REPORT, 0);
> +
> + ioctl(fd, UI_DEV_DESTROY);
> + }
> +
> + close(fd);
> +
> + return 0;
> +
> --
> 2.9.3
>
next prev parent reply other threads:[~2017-03-27 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 16:48 [PATCH v3] Adding uinput documentation Marcos Paulo de Souza
2017-03-26 16:48 ` [PATCH v3] Documentation: Input: Add " Marcos Paulo de Souza
2017-03-27 1:06 ` Peter Hutterer [this message]
2017-03-27 2:41 ` Marcos Paulo de Souza
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=20170327010611.GA21915@jelly \
--to=peter.hutterer@who-t.net \
--cc=corbet@lwn.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.souza.org@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