From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: USB hotplug: knowing which interface you are being called for
Date: Thu, 27 Feb 2003 07:49:45 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-104633248210890@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-104627423503358@msgid-missing>
> > Hi Greg, thanks for looking into this. You are right about the ":" of
> > course. It would be nice to have all the info about the interface present
> > in the sysfs directory (yes, including the interface number!), i.e. the
> > same info as in struct usb_interface. This creates some kind of equality
> > between probe methods and hotplugging scripts - and why not supply the
> > info if it exists?
>
> Ok, I just did that:
> http://linuxusb.bkbits.net:8080/usb-2.5/patch@1.1415
Great! I will test.
> > For the endpoints, I guess you are going to have to deal with alternate
> > interface settings as well. I can see two methods: (1) a subdirectory
> > for each alt setting, containing endpoints, (2) endpoints indexed by alt
> > setting and endpoint number.
>
> Yeah, the endpoints aren't going to be as simple, I'll have to think
> about them for a bit.
>
> > By the way, how are different configurations dealt with in the sysfs
> > tree?
>
> They really aren't supported well at all, see Oliver's patch a while ago
> on linux-usb-devel that added better support to the core first.
I guess they could be added as independent devices, with the
USB code enforcing mutually exclusive access.
Anyway, thanks a lot,
Duncan.
-------------------------------------------------------
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
prev parent reply other threads:[~2003-02-27 7:49 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
2003-02-26 20:11 ` Duncan Sands
2003-02-26 22:27 ` Greg KH
2003-02-27 7:49 ` Duncan Sands [this message]
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-104633248210890@msgid-missing \
--to=duncan.sands@math.u-psud.fr \
--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).