Re: USB hotplug: knowing which interface you are being called for

[Duncan Sands <duncan.sands@math.u-psud.fr>]

> > 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