linux-kernel - Re: [PATCH] Input: gtco

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 for Android: free password hash cracker in your pocket

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

Message-ID: <nycvar.YFH.7.76.2101081434550.13752@cbobk.fhfr.pm>
Date:   Fri, 8 Jan 2021 14:35:40 +0100 (CET)
From:   Jiri Kosina <jikos@...nel.org>
To:     Dmitry Torokhov <dmitry.torokhov@...il.com>
cc:     linux-input@...r.kernel.org, Rob Herring <robh@...nel.org>,
        Paul Hollinsky <phollinsky@...technik.com>,
        Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Input: gtco - remove driver

On Thu, 17 Dec 2020, Dmitry Torokhov wrote:

> > > Note that our HID support has greatly improved over the last 10 years,
> > > we may also consider reverting 6f8d9e26e7de ("hid-core.c: Adds all GTCO
> > > CalComp Digitizers and InterWrite School Products to blacklist") and see
> > > if GTCO devices actually work with normal HID drivers.
> > 
> > Sounds like a good plan to me. Perhaps you can do that in a series 
> > together, and stage that for 5.12?
> 
> Sorry, I already zapped the driver in 5.11.
> 
> Unfortunately I do not have this hardware, so while we could remove
> these devices from the blacklist we will have to do that blindly. Please
> let me know if you still want to do that.

We can also wait for the first person to potentially complain (if ever) 
about the driver going away -- that'd mean that the person does actually 
still have that hardware, and we could ask him to test with hid-generic.

Thanks,

-- 
Jiri Kosina
SUSE Labs