From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] hotplug usb.rc changes
Date: Sun, 08 Jun 2003 19:11:47 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105517171214624@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105500525713006@msgid-missing>
Olaf Hering wrote:
> We could improve things alot if /proc/bus/usb/devices had a better
> design :(
Well, that was a first version. Nobody's really done
much with that kernel code other than fix bugs.
> It is updated dynamically, reading it can take an unknown amount of time
> and it triggers bus traffic. You can not do
> grep -Eq '^I: .* Driver=\(none\)$' /proc/bus/usb/devices
No, but you could open every /proc/bus/usb/BBB/DDD file,
read its descriptors, and then ask each interface what
driver bound to it ... the answer may be "none".
If indeed /proc/bus/usb is available ... which hotplug
has never assumed.
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-06-08 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 16:56 [PATCH] hotplug usb.rc changes Olaf Hering
2003-06-07 17:51 ` Olaf Hering
2003-06-07 20:28 ` Wout Mertens
2003-06-08 5:42 ` Olaf Hering
2003-06-08 19:11 ` David Brownell [this message]
2003-06-10 21:30 ` Olaf Hering
2003-06-11 0:19 ` David Brownell
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=marc-linux-hotplug-105517171214624@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).