So either we should add accessor functions for configurations and
altsettings, or we remove the accessor for interfaces and verify that the
data structures are correct at the time they are created. I lean toward
the latter, although it might end up being too hard to deal with really messed-up descriptors.
In terms of a clean API, I'd prefer the latter; USB is clearly designed to treat interface numbers (and altsetting numbers) as array indices. But I don't prefer it enough to fix config.c myself, or audit the drivers ... :)
We don't need config accessors though; no driver should be using anything except the current config, unless maybe it's trying to decide whether to change configs, in which case it needs to be smart enough to walk the array itself.
- Dave
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
