All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Roberto Alejandro Espi Munoz <raespi@icid.cu>,
	linux-input <linux-input@vger.kernel.org>
Subject: Re: uinput on headless system ...
Date: Thu, 14 Jan 2016 06:08:53 +0100	[thread overview]
Message-ID: <CAN+gG=FirVq_MrXDkFe8K=7TEVzif9MSHvov4SyZE1M_Z5N=8g@mail.gmail.com> (raw)
In-Reply-To: <20160113222151.GE39593@dtor-ws>

Hi Roberto,

On Wed, Jan 13, 2016 at 11:21 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> Hi Roberto,
>
> On Wed, Jan 13, 2016 at 09:19:39AM -0500, Roberto Alejandro Espi Munoz wrote:
>> Hello ... I've been searching around the web for a specific mailing
>> list for the uinput driver but couldn't find any.  I managed to
>> create an example app that injects keyboard events to the running
>> linux kernel succesfully when I have a keyboard attached to the
>> computer.  However if I run it on a keyboardless machine, like a
>> standalone motherboard, the uinput device fails to open.
>
> uinput driver does not depend on presence of a physical keyboard. I'd
> start looking whether uinput module is enabled on your headless box and
> if it is a module verify that it is loaded.
>

As Dmitry said, uinput is independent of any attached hardware.
You might want to see how we managed to create new devices through
uinput by looking at libevdev[1] (see libevdev/libevdev-uinput.c).

You might actually also want to use libevdev instead of manually doing
the ioctls and processing of all the small things :)

Cheers,
Benjamin

[1] http://www.freedesktop.org/wiki/Software/libevdev/

  reply	other threads:[~2016-01-14  5:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 14:19 uinput on headless system Roberto Alejandro Espi Munoz
2016-01-13 22:21 ` Dmitry Torokhov
2016-01-14  5:08   ` Benjamin Tissoires [this message]
2016-01-14 14:05     ` Roberto Alejandro Espi Munoz
2016-01-14 14:27       ` Benjamin Tissoires
2016-01-14 15:16         ` Roberto Alejandro Espi Munoz
2016-01-19 14:55           ` Roberto Alejandro Espi Munoz
2016-01-19 21:36             ` Dmitry Torokhov
2016-01-19 21:58               ` Roberto Alejandro Espi Munoz
2016-01-19 22:56                 ` 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='CAN+gG=FirVq_MrXDkFe8K=7TEVzif9MSHvov4SyZE1M_Z5N=8g@mail.gmail.com' \
    --to=benjamin.tissoires@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=raespi@icid.cu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.