linux-kernel - Re: [PATCH 2/2] i8042: Use new forenorestore quirk to replace old buggy quirk combination

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]

Date: Tue, 2 Jan 2024 15:08:11 +0100
From: Werner Sembach <wse@...edocomputers.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
 Hans de Goede <hdegoede@...hat.com>
Subject: Re: [PATCH 2/2] i8042: Use new forenorestore quirk to replace old
 buggy quirk combination

Hi,

Am 02.01.24 um 14:48 schrieb Werner Sembach:
> The old quirk combination sometimes cause a laggy keyboard after boot. With
> the new quirk the initial issue of an unresponsive keyboard after s3 resume
> is also fixed, but it doesn't have the negative side effect of the
> sometimes laggy keyboard.
>
> Signed-off-by: Werner Sembach <wse@...edocomputers.com>
> Cc: stable@...r.kernel.org

Added Hans to the loop.

As mentioned in the one on one e-Mails with Hans I wrote a new quirk in [Patch 
1/2] and tested it on the device in [Patch 2/2]

At least one more device will follow which has negative side effects with the 
old quirkls, but I currently don't have it at hand for testing.

I wonder if devices where the old quirk combination did not cause issue should 
also be switched to the new quirk, if, after testing, it also fixes the 
unresponsive keyboard issues?

Kind regards,

Werner