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: <YNJ6v7DfXUFMO8YA@minibook.localdomain>
Date:   Wed, 23 Jun 2021 03:05:19 +0300
From:   Sergey Larin <cerg2010cerg2010@...l.ru>
To:     Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:     Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre Torgue <alexandre.torgue@...s.st.com>,
        linux-input@...r.kernel.org,
        linux-stm32@...md-mailman.stormreply.com,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Input: stmpe-keypad - add STMPE1801 support

Hello Dmitry,

On Sun, Jun 20, 2021 at 10:30:07PM -0700, Dmitry Torokhov wrote:
> Do we really need to do this swap vs. simply arranging the keymap
> differently for 1801?

Yes I thought about it, but that will break device tree writer's
assumptions of the device so I think it's better to keep the keymap
correct and not make driver's behavior confusing.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ