From: Kay Sievers <kay.sievers@vrfy.org>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: udev regression? lsusb silent (no output) since 2.6.22-rc2 at least
Date: Sun, 27 May 2007 16:10:01 +0200 [thread overview]
Message-ID: <1180275001.3131.28.camel@lov.localdomain> (raw)
In-Reply-To: <20070527092546.GA10912@outpost.ds9a.nl>
On Sun, 2007-05-27 at 11:25 +0200, bert hubert wrote:
> On Sun, May 27, 2007 at 04:42:35AM +0200, Kay Sievers wrote:
> > > Any clues? Please let me know how I can help solve this problem!
> >
> > It works fine for me here. Do you have CONFIG_USB_DEVICE_CLASS=y set?
>
> Ah, I have not. However, this setting was not present in 2.6.21-rc3, from
> which configuration I ran 'make oldconfig'.
>
> Make oldconfig does ask for this feature:
> USB device class-devices (DEPRECATED) (USB_DEVICE_CLASS) [N/y/?] (NEW)
>
> And I chose the default, breaking (my version of) lsusb, on Ubuntu Edgy Eft.
> I enabled USB_DEVICE_CLASS, and lsusb worked again.
>
> Thank you both for your quick answers!
>
> Please consider this patch which clarifies the need for USB_DEVICE_CLASS:
>
> --- ./drivers/usb/core/Kconfig~ 2007-05-27 11:22:22.000000000 +0200
> +++ ./drivers/usb/core/Kconfig 2007-05-27 11:22:22.000000000 +0200
> @@ -54,7 +54,8 @@
> device of the interface and therefore easily accessible from the interface
> event.
>
> - This option provides backward compatibility if needed.
> + This option provides backward compatibility and is required on
> + many distributions to keep lsusb working.
Yeah, a bit more text may be helpful. Many systems still use usbfs and
should work just fine without that option. Adding a udev rule will also
work.
The next version of HAL will depend on that udev rule. We have seen too
many unpredictable event timing problems with the usb_device class, and
will switch to the nodes provided directly by the usb-device instead of
the separate class device. How does that help text sound?
This option provides backward compatibility for systems where
usbfs is not mounted, and no udev rule like this exists:
SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", \
NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"
Thanks,
Kay
next prev parent reply other threads:[~2007-05-27 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 20:18 bert hubert
2007-05-27 2:42 ` Kay Sievers
2007-05-27 9:25 ` bert hubert
2007-05-27 14:10 ` Kay Sievers [this message]
2007-05-27 14:20 ` bert hubert
2007-05-27 14:34 ` Kay Sievers
2007-05-27 14:40 ` bert hubert
2007-05-27 5:37 ` Greg KH
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=1180275001.3131.28.camel@lov.localdomain \
--to=kay.sievers@vrfy.org \
--cc=bert.hubert@netherlabs.nl \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®