From: Kay Sievers <kay.sievers@vrfy.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Jiri Kosina <jikos@jikos.cz>, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.22-rc3 breaks USB: Unable to get HID descriptor (error sending control message: Operation not permitted)
Date: Sun, 03 Jun 2007 18:51:21 +0200 [thread overview]
Message-ID: <1180889481.7793.20.camel@lov.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0706030837480.3790@p34.internal.lan>
On Sun, 2007-06-03 at 08:40 -0400, Justin Piszcz wrote:
> On Sun, 3 Jun 2007, Kay Sievers wrote:
>
> > On 6/3/07, Justin Piszcz <jpiszcz@lucidpixels.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.
> 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?
The usb_device class was created to replace the /proc usbfs device nodes
which can't handle access-control-lists for logged-in users.
The device nodes worked fine, but plugging into the device events to
trigger userspace device handling created a bunch of problems with the
event timing. We have several open bugs, that can't be fixed properly
with using the usb_device-devices.
We changed the driver core to allow us to export device nodes directly
by bus-devices, instead of forcing us to create artificial devices like
the usb_device-class, just to export device nodes to userspace. If
systems set CONFIG_USB_DEVICE_CLASS=n (which defaults to yes now), one
new udev rule is needed, to replace the functionality of the
usb_device-class devices. Also the next version of HAL (which is where
nut receives the events from) will depend on the new device nodes, and
will not longer use usb_device devices. No changes to nut should be
needed.
Thanks,
Kay
next prev parent reply other threads:[~2007-06-03 16:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 22:43 Kernel 2.6.22-rc3 breaks USB: Unable to get HID descriptor (error sending control message: Operation not permitted) Justin Piszcz
2007-06-03 9:49 ` Jiri Kosina
2007-06-03 10:36 ` Justin Piszcz
2007-06-03 10:54 ` Oliver Neukum
2007-06-03 12:29 ` Justin Piszcz
2007-06-03 11:00 ` Jiri Kosina
2007-06-03 11:16 ` Justin Piszcz
2007-06-03 11:22 ` Jiri Kosina
2007-06-03 11:52 ` Justin Piszcz
2007-06-03 12:35 ` Kay Sievers
2007-06-03 12:40 ` Justin Piszcz
2007-06-03 12:44 ` Justin Piszcz
2007-06-03 16:51 ` Kay Sievers [this message]
2007-06-03 9:55 ` Jiri Kosina
2007-06-03 10:48 ` [linux-usb-devel] " Oliver Neukum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1180889481.7793.20.camel@lov.localdomain \
--to=kay.sievers@vrfy.org \
--cc=jikos@jikos.cz \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox