linux-kernel - Re: Kernel 2.6.22-rc3 breaks USB: Unable to get HID descriptor (error sending control message: Operation not permitted)

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]

Date:	Sun, 3 Jun 2007 08:40:11 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Kay Sievers <kay.sievers@...y.org>
cc:	Jiri Kosina <jikos@...os.cz>, linux-kernel@...r.kernel.org
Subject: Re: Kernel 2.6.22-rc3 breaks USB: Unable to get HID descriptor (error
 sending control message: Operation not permitted)



On Sun, 3 Jun 2007, Kay Sievers wrote:

> On 6/3/07, Justin Piszcz <jpiszcz@...idpixels.com> wrote:
>> On Sun, 3 Jun 2007, Jiri Kosina wrote:
>> 
>> > On Sun, 3 Jun 2007, Justin Piszcz wrote:
>> >
>> >>> Thanks. Does by any chance reverting the commit
>> >>> 9f8b17e643fe6aa505629658445849397bda4e4f improve the situation?
>> >> I have not played around with git/etc enough to back it out, if you have 
>> a
>> >> patch that applies on top of 2.6.22-rc3 that backs it out I can give it 
>> a try.
>> >
>> > Please try this
>> 
>> [[ .. snip .. ]]
>> 
>> The patch was successful and now my USB device is working again!
>
> Please set:
> CONFIG_USB_DEVICE_CLASS=y
> there should be no patch needed. The option already defaults to yes in
> the latest kernel.
>
> Thanks,
> Kay
>

   USB device class-devices (DEPRECATED) (USB_DEVICE_CLASS) [N/y/?] (NEW) y

Why is it deprecated if (nut/usb/etc fails) when its not used?  Does nut 
or udev have to play catch-up to adhere to the new kernel changes?

Compiling with this option and testing now.


-
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/