Chaskiel M Grundman wrote: > the ccid spec supports using an interrupt pipe message to notify > the host of card insert/remove events, but devices are not required > to implement that part. Even for devices that do, I don't > understand enough of how usb and libusb handle interrupt endpoints > to know if the messages are buffered indefinitely, or only when > there's an outstanding urb.
USB is completely driven by the host, so unless an app keeps a transfer pending for the interrupt pipe, nothing will be transfered. The USB function (reader) detects that it couldn't send and takes some action, typically either throwing the message away, or queueing it for a retry later. //Peter _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
