lkml.org 
[lkml]   [2018]   [Jan]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Dell Vostro 3360 multimedia keys
On Sat, Jan 27, 2018 at 6:05 AM, Pali Rohár <pali.rohar@gmail.com> wrote:
> On Tuesday 21 November 2017 19:58:24 Oleksandr Natalenko wrote:
>>
>> Just to note what I did. Here is my custom /etc/udev/hwdb.d/90-dell-
>> vostro-3360.hwdb:
>>
>> ===
>> evdev:atkbd:dmi:bvnDellInc.:bvrA18:bd09/25/2013:svnDellInc.:pnVostro3360:pvr:rvnDellInc.:rn0F5DWF:rvrA00:cvnDellInc.:ct8:cvr0.1:
>> KEYBOARD_KEY_60=prog4
>> ===
>>
>> Here is how this key press is being detected by evtest via atkbd:
>>
>> ===
>> Event: time 1511289883.083968, type 4 (EV_MSC), code 4 (MSC_SCAN), value 60
>> Event: time 1511289883.083968, type 1 (EV_KEY), code 203 (KEY_PROG4), value 2
>> Event: time 1511289883.083968, -------------- SYN_REPORT ------------
>> ===
>
> So, it is working fine and there is no problem in kernel.
>
>> But xev shows nothing when I press this key. Am I doing something wrong?
>
> This is bug in X Server or so. You would need to remap keycode to
> something different as a workaround for X Server.

No, I do not think so. Value 2 means that the key is repeated, most
likely because the firmware did not bother to generate a "release"
event for this key. You also need to adjust "force_release" but
changing your hwdb entry slightly:

KEYBOARD_KEY_60=!prog4

(note ! before the keycode name).

X implements its own autorepeat handling and ignores kernel key events
with value of 2.

Thanks.

--
Dmitry

\
 
 \ /
  Last update: 2018-01-28 05:39    [W:0.044 / U:0.224 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site