linux-kernel - Re: Dell Vostro 3360 multimedia keys

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAKdAkRQa1tZXMxg=8WX4kfFk_p+5kDakVRJDyB_r4ri3qG5eCg@mail.gmail.com>
Date:   Sat, 27 Jan 2018 20:39:15 -0800
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
To:     Pali Rohár <pali.rohar@...il.com>
Cc:     Oleksandr Natalenko <oleksandr@...alenko.name>,
        Mario Limonciello <mario_limonciello@...l.com>,
        Platform Driver <platform-driver-x86@...r.kernel.org>,
        lkml <linux-kernel@...r.kernel.org>,
        Matthew Garrett <mjg59@...f.ucam.org>,
        Darren Hart <dvhart@...radead.org>,
        Andy Shevchenko <andy@...radead.org>
Subject: Re: Dell Vostro 3360 multimedia keys

On Sat, Jan 27, 2018 at 6:05 AM, Pali Rohár <pali.rohar@...il.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