From: simon@mungewell.org
To: linux-input@vger.kernel.org
Subject: Multiple clients reading from /dev/input/eventX
Date: Fri, 19 Oct 2012 11:49:29 -0400 [thread overview]
Message-ID: <e6193392fbe49d7236b39e3b17b8fa81.squirrel@mungewell.org> (raw)
Hi all,
I'm trying to track down a problem with SDL missing events from a gaming
wheel. It looks like it's not seeing a 'section' of events and this
results in an axis from the wheel/joystick being stuck on.
If I simultaneously use evtest to monitor the same /dev/input/eventX I see
all the events in evtest, but not in SDL.
I suspect that some scheduling (or other business) is causing SDL not to
check the file handle, and as a result the input system is
dropping/resyncing the interface.
Can anyone here confirm the behaviour under the situation that one client
is busy? What is the maximum time it can be 'away' or what is the size of
the inline buffer?
Many thanks,
Simon.
next reply other threads:[~2012-10-19 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 15:49 simon [this message]
2012-10-19 22:32 ` Multiple clients reading from /dev/input/eventX Dmitry Torokhov
2012-10-24 4:26 ` simon
2012-10-24 5:07 ` 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=e6193392fbe49d7236b39e3b17b8fa81.squirrel@mungewell.org \
--to=simon@mungewell.org \
--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).