Re: udev regression? lsusb silent (no output) since 2.6.22-rc2 at least

[Kay Sievers <kay.sievers@vrfy.org>]

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

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