linux-kernel - Re: usb hid: reset NumLock

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

Message-ID: <Pine.LNX.4.64.0704031128500.3808@jikos.suse.cz>
Date:	Tue, 3 Apr 2007 11:32:35 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Robert Marquardt <marquardt@...emercs.com>
Cc:	Pete Zaitcev <zaitcev@...hat.com>, stuart_hayes@...l.com,
	linux-usb-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: usb hid: reset NumLock

On Tue, 3 Apr 2007, Robert Marquardt wrote:

> > As this quirk is only needed once in the initialization method, we 
> > could probably get rid of it and just put and explicit test for PID 
> > and VID there (with apropriate comment). We can't afford wasting quirk 
> > entries, as we are slowly running out of them.
> Is it a problem of table size or number of table entries? For the number 
> of entries a simple change to PID ranges should help. It would also 
> allow to move Wacom to the blacklist. I have sent a patch for that 
> already, but it was rejected by Greg.

The issue is that 32 bits of the quirk bitmask are going to be taken by 
the quirk entries (so no, it's not related to the size of the table).

Thanks,

-- 
Jiri Kosina
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/