From: David Brownell <david-b@pacbell.net>
To: Brad Hards <bhards@bigpond.net.au>
Cc: Johannes Erdfelt <johannes@erdfelt.com>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: 2.5.26 hotplug failure
Date: Fri, 20 Sep 2002 19:36:54 -0700 [thread overview]
Message-ID: <3D8BDB46.9020508@pacbell.net> (raw)
In-Reply-To: 200209211025.59114.bhards@bigpond.net.au
>>Personally, I've never used /proc/bus/usb/drivers. I've always just
>>looked at lsmod.
>>
>>Why should this be any different?
>
> Because lsmod only works for drivers that are modular. Real users mix built-in
> and modules.
Wasn't someone -- Rusty? -- working an update to the module framework
so 2.5 would be able to show all kernel modules, not just dynamically
linked ones? And so something like their MODULE_NAME could be used
in static tables as the driver name? Some 2.4 usb drivers disagreed
with themselves on that issue. (Hotplug no longer has the table of
exceptions it once had, it was error prone. But that also means it's
more uncertain about system state than is necessary.)
I'd be more keen to see that issue solved than keep the 'drivers' file.
The question that hotplug wants to answer, for example, is "is this
driver in the kernel". None of the 2.4 solutions for that were very
trouble free.
- Dave
next prev parent reply other threads:[~2002-09-21 2:31 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
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 [this message]
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=3D8BDB46.9020508@pacbell.net \
--to=david-b@pacbell.net \
--cc=bhards@bigpond.net.au \
--cc=greg@kroah.com \
--cc=johannes@erdfelt.com \
--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).