linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roberto Alejandro Espi Munoz <raespi@icid.cu>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
	linux-input <linux-input@vger.kernel.org>
Subject: Re: uinput on headless system ...
Date: Tue, 19 Jan 2016 16:58:58 -0500	[thread overview]
Message-ID: <569EB1A2.5000907@icid.cu> (raw)
In-Reply-To: <20160119213647.GB31589@dtor-ws>

The error is produced when the write operation doesn't return the same 
number of bytes as the one requested to write.  Is there any other way 
of checking a specific error message on files associated with devices?

if (write( uinputDev, &event, sizeof(struct input_event)) != sizeof( 
struct input_event) )
{
     fprintf(stderr, "Error on send_event");
     return -1;
  }

On 01/19/2016 04:36 PM, Dmitry Torokhov wrote:
> On Tue, Jan 19, 2016 at 09:55:00AM -0500, Roberto Alejandro Espi Munoz wrote:
>> Bump ... any other insights or suggestions I could try?
>>
> You can check what error you are getting when trying to open the device
> and that might give you idea.
>
> Thanks.
>



  reply	other threads:[~2016-01-19 21:59 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
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 [this message]
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=569EB1A2.5000907@icid.cu \
    --to=raespi@icid.cu \
    --cc=benjamin.tissoires@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    /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).