From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: USB hotplug: knowing which interface you are being called for
Date: Wed, 26 Feb 2003 17:04:48 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-104627966713682@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-104627423503358@msgid-missing>
On Wed, Feb 26, 2003 at 04:39:36PM +0100, Duncan Sands wrote:
> Greetings hotpluggers: when a USB device is plugged in (2.5), the
> usb hotplugging scripts are called for each interface. I don't see a
> convenient way to work out the interface number from the info passed
> it, namely the path to the interface in sysfs. Any suggestions?
As discussed on #kernelnewbies irc channel:
basename $DEVPATH
will give the interface number. Hm, you might have to search that
result for a ":" and then use the number after that which is the
interface number.
And I'll go add endpoint info to the sysfs directory too, that should
make your life easier, right?
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
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-02-26 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 15:39 USB hotplug: knowing which interface you are being called for Duncan Sands
2003-02-26 17:04 ` Greg KH [this message]
2003-02-26 20:11 ` Duncan Sands
2003-02-26 22:27 ` Greg KH
2003-02-27 7:49 ` Duncan Sands
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-104627966713682@msgid-missing \
--to=greg@kroah.com \
--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).