Please reply on the list in the future, so that others may benefit from
the answer.
If a device ignores a SetConfiguration call, then the IOUSBFamily will
not instantiate any IOUSBInterface objects for the Interfaces. This
means that there will not be any accessible IOUSBPipe objects.
The only situation under which I could see this as being OK would be if
the device didn't really have any interfaces, and call communications
with the device happened through the Control Pipe in the device.
Rhoads Hollowell
USB Software Team
Apple Computer, Inc.
On Mar 19, 2005, at 7:12 AM, Daniel R. Killoran,Ph.D. wrote:
On Mar 18, 2005, at 2:32 PM, Rhoads Hollowell wrote:
Secondly, almost every IOUSBDevice object in Mac OS X (and IO Kit)
needs to have a SetConfiguration call made on it to cause IOKit and
the IOUSBFamily to instantiate the IOUSBInterface object(s), and
there is an Apple delivered driver which does just that - the
AppleUSBComposite driver.
Ouch! What happens if the device is non-conformant, and ignores the
SetConfiguration call (resulting in a timeout)? I have encountered
several of them, fortunately all when doing OS9 drivers where you can
simply skip the SetConfiguration call, but does OS-X require it to be
done?
I realize, of course, that non-conformant behaviour is A Very Bad
Thing, but the hardware guys just say "it works on Windows" and shrug
their shoulders! Is there a reliable workaround on OS-X?
Dan Killoran
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/usb/email@hidden
