From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Sean Young <sean@mess.org>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] ir-keytable: re-add --device option
Date: Mon, 7 Sep 2020 16:58:06 +0200 [thread overview]
Message-ID: <20200907165806.3e236f45@coco.lan> (raw)
In-Reply-To: <20200907144309.GA2767@gofer.mess.org>
Em Mon, 7 Sep 2020 15:43:09 +0100
Sean Young <sean@mess.org> escreveu:
> On Mon, Sep 07, 2020 at 11:36:59AM +0200, Mauro Carvalho Chehab wrote:
> > While --device option doesn't work for enumerating and for RC/LIRC
> > specific control, it is still useful for testing purposes
> > for all kinds of input devices. For example, it can be used to
> > test mouse events:
> >
> > $ ./utils/keytable/ir-keytable -d /dev/input/event4 -t
> > Testing events. Please, press CTRL-C to abort.
> > 1222738.567737: event type EV_REL(0x02): REL_X (0x0000) value=1
> > 1222738.567737: event type EV_SYN(0x00).
> > 1222738.573742: event type EV_REL(0x02): REL_X (0x0000) value=1
> > 1222738.573742: event type EV_SYN(0x00).
> > 1222738.581738: event type EV_REL(0x02): REL_X (0x0000) value=2
> > 1222738.581738: event type EV_REL(0x02): REL_Y (0x0001) value=1
> >
> > So, re-add it, but only on test mode.
>
> Isn't this the same functionality as evtest(1), but not as complete?
>
> https://cgit.freedesktop.org/evtest/
>
> evtest is packaged for Fedora, Debian, and Ubuntu.
No idea. At least on the device I'm testing (Hikey 970), evtest doesn't
produce anything when I move my mouse (checking via ssh):
$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: PixArt Dell MS116 USB Optical Mouse
Select the device event number [0-0]:
While ir-keytable works fine.
Thanks,
Mauro
next prev parent reply other threads:[~2020-09-07 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 9:36 [PATCH] ir-keytable: re-add --device option Mauro Carvalho Chehab
2020-09-07 14:43 ` Sean Young
2020-09-07 14:58 ` Mauro Carvalho Chehab [this message]
2020-09-07 15:01 ` Mauro Carvalho Chehab
2020-09-07 18:27 ` Sean Young
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=20200907165806.3e236f45@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.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).