From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-media@vger.kernel.org, linux-input@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH update] firedtv: fix remote control with newer Xorg evdev
Date: Mon, 17 Jan 2011 09:00:15 -0800 [thread overview]
Message-ID: <20110117170015.GA15404@core.coreip.homeip.net> (raw)
In-Reply-To: <20110117141758.56af41f5@stein>
On Mon, Jan 17, 2011 at 02:17:58PM +0100, Stefan Richter wrote:
> After a recent update of xf86-input-evdev and xorg-server, I noticed
> that X11 applications did not receive keypresses from the FireDTV
> infrared remote control anymore. Instead, the Xorg log featured lots of
>
> "FireDTV remote control: dropping event due to full queue!"
>
> exclamations. The Linux console did not have an issue with the
> FireDTV's RC though.
>
> The fix is to insert EV_SYN events after the key-down/-up events.
> Dimitry notes that EV_SYN is also necessary between down and up,
> otherwise userspace could combine their state.
>
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Dmitry Torokhov <dtor@mail.ru>
> ---
> drivers/media/dvb/firewire/firedtv-rc.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> Index: b/drivers/media/dvb/firewire/firedtv-rc.c
> ===================================================================
> --- a/drivers/media/dvb/firewire/firedtv-rc.c
> +++ b/drivers/media/dvb/firewire/firedtv-rc.c
> @@ -172,7 +172,8 @@ void fdtv_unregister_rc(struct firedtv *
>
> void fdtv_handle_rc(struct firedtv *fdtv, unsigned int code)
> {
> - u16 *keycode = fdtv->remote_ctrl_dev->keycode;
> + struct input_dev *idev = fdtv->remote_ctrl_dev;
> + u16 *keycode = idev->keycode;
>
> if (code >= 0x0300 && code <= 0x031f)
> code = keycode[code - 0x0300];
> @@ -188,6 +189,8 @@ void fdtv_handle_rc(struct firedtv *fdtv
> return;
> }
>
> - input_report_key(fdtv->remote_ctrl_dev, code, 1);
> - input_report_key(fdtv->remote_ctrl_dev, code, 0);
> + input_report_key(idev, code, 1);
> + input_sync(idev);
> + input_report_key(idev, code, 0);
> + input_sync(idev);
> }
>
>
> --
> Stefan Richter
> -=====-==-== ---= =---=
> http://arcgraph.de/sr/
--
Dmitry
prev parent reply other threads:[~2011-01-17 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 8:39 [PATCH] firedtv: fix remote control with newer Xorg evdev Stefan Richter
2011-01-17 8:17 ` Dmitry Torokhov
2011-01-17 13:17 ` [PATCH update] " Stefan Richter
2011-01-17 17:00 ` Dmitry Torokhov [this message]
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=20110117170015.GA15404@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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).