From: Peter Hutterer <peter.hutterer@who-t.net>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH] macintosh: move mac_hid driver to input/mouse.
Date: Fri, 9 Jun 2017 09:07:52 +1000 [thread overview]
Message-ID: <20170608230752.GA4254@jelly> (raw)
In-Reply-To: <20170608151842.71b59dad@kitsune.suse.cz>
On Thu, Jun 08, 2017 at 03:18:42PM +0200, Michal Suchánek wrote:
> This is what evtest reports about my keyboard:
>
> Select the device event number [0-12]: 2
> Input driver version is 1.0.1
> Input device ID: bus 0x3 vendor 0x413c product 0x2107 version 0x111
> Input device name: "DELL Dell USB Entry Keyboard"
> Supported events:
> Event type 0 (EV_SYN)
> Event type 1 (EV_KEY)
> Event code 1 (KEY_ESC)
> Event code 2 (KEY_1)
> Event code 3 (KEY_2)
> Event code 4 (KEY_3)
> ...
> Event code 193 (KEY_F23)
> Event code 194 (KEY_F24)
> Event code 240 (KEY_UNKNOWN)
> Event code 272 (BTN_LEFT)
> Event code 273 (BTN_RIGHT)
> Event code 274 (BTN_MIDDLE)
> Event type 4 (EV_MSC)
> Event code 4 (MSC_SCAN)
> Event type 17 (EV_LED)
> Event code 0 (LED_NUML) state 1
> Event code 1 (LED_CAPSL) state 0
> Event code 2 (LED_SCROLLL) state 0
> Event code 3 (LED_COMPOSE) state 0
> Event code 4 (LED_KANA) state 0
> Key repeat handling:
> Repeat type 20 (EV_REP)
> Repeat code 0 (REP_DELAY)
> Value 250
> Repeat code 1 (REP_PERIOD)
> Value 33
> Properties:
looks like it's not tagged as ID_INPUT_MOUSE by the default udev rules
because for that we need x/y axes (either relative for real mice or absolute
ones for the VMWare USB mouse). This keyboard only has buttons though. So it
gets ID_INPUT_KEYBOARD for the keys, but no ID_INPUT_MOUSE.
Google isn't overly forthcoming on "DELL Dell USB Entry Keyboard" but the
few pictures I can find all point to a keyboard that doesn't have any
physical mouse buttons at all. Does yours have buttons? Can you post a
picture of it somewhere?
Cheers,
Peter
next prev parent reply other threads:[~2017-06-08 23:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 19:14 [PATCH] macintosh: move mac_hid driver to input/mouse Michal Suchanek
2017-05-10 0:43 ` Dmitry Torokhov
2017-05-10 10:44 ` Michal Suchánek
2017-05-28 9:47 ` Michal Suchanek
2017-05-28 13:26 ` Bastien Nocera
2017-05-28 17:55 ` Dmitry Torokhov
2017-05-29 18:03 ` Michal Suchánek
2017-05-30 5:06 ` Dmitry Torokhov
2017-05-30 9:34 ` Michal Suchánek
2017-05-30 10:33 ` Benjamin Tissoires
2017-05-30 11:32 ` Michal Suchánek
2017-05-30 12:02 ` Benjamin Tissoires
2017-05-30 12:56 ` Michal Suchánek
2017-05-31 4:26 ` Peter Hutterer
2017-06-07 12:29 ` Michal Suchánek
2017-06-07 16:53 ` Michal Suchánek
2017-06-07 17:16 ` Dmitry Torokhov
2017-06-07 19:17 ` Michal Suchánek
2017-06-07 19:17 ` Michal Suchánek
2017-06-07 23:13 ` Peter Hutterer
2017-06-08 13:18 ` Michal Suchánek
2017-06-08 13:18 ` Michal Suchánek
2017-06-08 23:07 ` Peter Hutterer [this message]
2017-06-08 23:18 ` Dmitry Torokhov
2017-06-08 23:18 ` Dmitry Torokhov
2017-06-09 11:39 ` Michal Suchánek
2017-06-09 11:39 ` Michal Suchánek
2017-06-10 2:00 ` Peter Hutterer
2017-06-12 11:40 ` Michal Suchánek
2017-06-12 11:40 ` Michal Suchánek
2017-06-12 13:27 ` Michal Suchánek
2017-06-12 13:27 ` Michal Suchánek
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=20170608230752.GA4254@jelly \
--to=peter.hutterer@who-t.net \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.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 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.