Re: Cleaning up the USBHID's blacklist.

2007-08-01 Thread Jiri Kosina
On Tue, 31 Jul 2007, Chr wrote: > But I have one (final?) question. Since I am sometimes stuck to 80x25 > console... > can we alphabetically sort the blacklist by the Vendor (the first > field), instead of the quirk field(last field)? Or is there a > technical/theoretical reason behind it? I

Re: Cleaning up the USBHID's blacklist.

2007-08-01 Thread Jiri Kosina
On Tue, 31 Jul 2007, Chr wrote: But I have one (final?) question. Since I am sometimes stuck to 80x25 console... can we alphabetically sort the blacklist by the Vendor (the first field), instead of the quirk field(last field)? Or is there a technical/theoretical reason behind it? I find

Cleaning up the USBHID's blacklist.

2007-07-31 Thread Chr
On Tuesday, 31. July 2007, Jiri Kosina wrote: > On Mon, 30 Jul 2007, Chr wrote: > > > Ok, found it " hid_blacklist is alphabetically sorted blacklist by quirk > > type. " But is there a Order for the bitfields? e.g > > shouldn't: hid-quriks.c (line 439, 440) > > { USB_VENDOR_ID_APPLE,

Cleaning up the USBHID's blacklist.

2007-07-31 Thread Chr
On Tuesday, 31. July 2007, Jiri Kosina wrote: On Mon, 30 Jul 2007, Chr wrote: Ok, found it hid_blacklist is alphabetically sorted blacklist by quirk type. But is there a Order for the bitfields? e.g shouldn't: hid-quriks.c (line 439, 440) { USB_VENDOR_ID_APPLE,