linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Brad Hards <bhards@bigpond.net.au>
Cc: Duncan Sands <duncan.sands@wanadoo.fr>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.5.26 hotplug failure
Date: Wed, 18 Sep 2002 09:55:32 -0700	[thread overview]
Message-ID: <20020918165532.GA9654@kroah.com> (raw)
In-Reply-To: <200209181715.51314.bhards@bigpond.net.au>

On Wed, Sep 18, 2002 at 05:15:50PM +1000, Brad Hards wrote:
> On Wed, 18 Sep 2002 16:52, Greg KH wrote:
> > On Sun, Sep 15, 2002 at 11:53:41PM +0200, Duncan Sands wrote:
> > > A simple fix is to change the test to [ $COUNT -lt 2 ];
> >
> > Good catch, yes the drivers file disappeared, and until now, almost no
> > one noticed it :)
> I assume that /proc/bus/usb/drivers went to driverfs. Everyone likes the new 
> guy:)

The functionality went there, not the actual file.  The file is obsolete
now :)

> I'd like the file back. We have a lot of debugging advice that asks people to 
> send that particular file to us, and it is very useful. Even if you update 
> the few places that you can find, then you will still have a lot of confusion 
> (well, if you have 2.4, then send this, and if you have 2.6, send this, and 
> if that doesn't exist, and you're on 2.4, mount this filesystem, else mount 
> this filesystem). Ugly, and increases the support workload.
> 
> A symlink will do, assuming both filesystems are mounted. If we only have 
> usbfs, I still want the data.

'ls <wherever_you_mounted_driverfs>/bus/usb/drivers' will now show you
all of the registered USB drivers.  As for what the minor numbers are
for the drivers that happened to use the USB major number, I'm working
on that.

> Please fix this before 2.6.

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.

thanks,

greg k-h

  reply	other threads:[~2002-09-18 16:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  7:50 2.5.26 hotplug failure Duncan Sands
2002-07-18 18:36 ` Greg KH
2002-07-18 19:07   ` Duncan Sands
2002-09-15 21:53   ` Duncan Sands
2002-09-18  6:52     ` Greg KH
2002-09-18  7:15       ` [linux-usb-devel] " Brad Hards
2002-09-18 16:55         ` Greg KH [this message]
2002-09-19  7:37           ` Daniel Phillips
2002-09-19  7:45             ` Daniel Phillips
2002-09-19  7:48             ` Greg KH
2002-09-19  7:55               ` Daniel Phillips
2002-09-19 16:49                 ` Greg KH
2002-09-19 20:56                   ` Brad Hards
2002-09-19 23:06                     ` Greg KH
2002-09-20 20:42                       ` [linux-usb-devel] " David Brownell
2002-09-20 23:11                         ` Greg KH
2002-09-21  2:55                           ` David Brownell
2002-09-21  3:31                             ` Greg KH
2002-09-21  3:58                               ` David Brownell
2002-09-21  5:48                                 ` Greg KH
2002-09-22  1:21                               ` Linus Torvalds
2002-09-24 18:26                                 ` Patrick Mochel
2002-09-24 18:55                                   ` Linus Torvalds
2002-09-24 19:29                                     ` Greg KH
2002-09-24 22:37                                       ` Patrick Mochel
2002-09-20 23:22                         ` Brad Hards
2002-09-20 23:36                           ` Johannes Erdfelt
2002-09-21  0:11                             ` Randy.Dunlap
2002-09-21  0:25                             ` Brad Hards
2002-09-21  2:36                               ` David Brownell
2002-09-20 23:46                           ` Patrick Mochel

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=20020918165532.GA9654@kroah.com \
    --to=greg@kroah.com \
    --cc=bhards@bigpond.net.au \
    --cc=duncan.sands@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).