Colin Zou - Sun Microsystems writes: > Seems to me that there lack of some background introduction for WUSB. I > just wrote a blog about WUSB association, it is offering the background > info to this issue. Please take a look at: > http://blogs.sun.com/colin/entry/association_the_difference_between_usb
I see. Actually, it sounds to me like this new "CC" feature would be useful for regular wired USB as well. For wired USB, a common problem is that the device is identified by its attachment point on the system. If you plug the device into a different port, it becomes a different device, and the system (as I understand it) has to "guess" whether it's really the same one. That works somewhat well for self-identifying things like disks that have serial numbers and perhaps a saved mount point, but much less well otherwise. I'd very much like to have device identity down below this level, and the CC feature sounds ideal for doing that. Why is it designed to be wireless only? > And, to be clear, the implementation for supporting WUSB on Solaris > comform to the existing usba(7D) framework on Solaris and also devfsadm > framework. WUSB device enumeration is the same as USB on Solaris. The > difference is "Association" which is a new concept for wireless USB > only. It is discussed in detail in the above link. It implies a bit of an oddity, though. In order for enumeration to follow "assocation," this means that the association daemon (wusbd) must somehow learn about and communicate with a device that has not yet been enumerated. That itself sounds _like_ an enumeration, identification, and attachment sequence. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
