Re: 2.5.26 hotplug failure
Greg KH (firstname.lastname@example.org)
Thu, 19 Sep 2002 09:49:24 -0700
On Thu, Sep 19, 2002 at 09:55:57AM +0200, Daniel Phillips wrote:
> On Thursday 19 September 2002 09:48, Greg KH wrote:
> > On Thu, Sep 19, 2002 at 09:37:07AM +0200, Daniel Phillips wrote:
> > > On Wednesday 18 September 2002 18:55, Greg KH wrote:
> > > > Sorry, but I'm not going to put the file back. I understand your
> > > > concerns. We should have some kind of program (lsdev like) that shows
> > > > the system information present at that moment in time. It will be able
> > > > to provide what the /proc/bus/usb/drivers file showed in the past.
> > >
> > > How about calling it /proc/bus/usb/drivers?
> > Please go back and read what I wrote above what you snipped out and then
> > explain how this would be possible.
> I don't get it. What's the problem? Not that I'm advocating that proc have
> functionality that can be done perfectly well in user space, but I fail to
> see why you couldn't do it in proc if you wanted to.
First of all, /proc/bus/usb/* is not a proc filesystem, usbfs is mounted
in that location :)
The main reason is this information is no longer available to the USB
core. It isn't keeping a list of registered drivers anymore, only the
driver core is. So there's no way that usbfs can get to that
information. As the info is available in driverfs, duplication of it in
usbfs would be bloat.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/