linux-kernel - usbhid: Changes since 2.6.28 in quirk handling?

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-next>] [day] [month] [year] [list]

Date:	Fri, 13 Mar 2009 08:39:02 -0400
From:	Bill Gribble <grib@...lgribble.com>
To:	linux-kernel@...r.kernel.org
Subject: usbhid:  Changes since 2.6.28 in quirk handling?

Hi, I have been maintaining a patch for a quirky USB device built-in to
a UMPC, the Raon Digital Everun.  Without the patch, the builtin
keyboard, mouse, and touchscreen are useless.  I have never submitted it
for inclusion in the kernel because there are less than 5 people who
have ever even attempted to install Linux on this device, and it's
discontinued.  However, *I* use the thing daily, and its wifi device
(libertas) has continued to get better support in the recent kernels so
I port the patch forward. 

Anyway the patch adds a quirk handler that does a mandatory
initialization step to turn the USB device on at powerup or resume.  In
recent kernels (I moved from 2.6.28, which was reliable, at 2.6.29-rc5,
I believe) this has become unreliable; about half the time the device is
not enabled at boot, and about 1 time in 10 it is disabled when resuming
from suspend-to-RAM. 

I noticed that the structure of the quirk handling code has changed
somewhat; I left my patch using the "old" way of adding an entry to
hid_blacklist in hid-quirks.c.  Is there a document or email trail that
describes the new way of structuring this quirk code?  Any pitfalls to
look out for? 

Thanks,
Bill Gribble

View attachment "everun.patch" of type "text/x-patch" (3078 bytes)