| Previous | Next |
| kIOConfigNoEntry | kIOFireWireLastDCLToken |
kIOFireWirePending
A state notification, not a completed transaction
kIOFireWirePending means that the FireWire-family operation is in a pending queue and waiting for execution. It should not be interpreted as a remote-device response or as proof of failure. The owning API still has to deliver a later callback, response, cancellation, reset-related result, or timeout according to the operation type.
Asynchronous FireWire work is sensitive to bus generation and controller state. Reissuing a pending request may create duplicate work or disturb ordering; cancelling it without knowing the ownership rules can lose the only result path. The correct next action is usually to keep the request identity and follow its state transition.
Track the request through completion
- Record a stable request identifier, target node, transaction type, bus generation, and enqueue timestamp.
- Correlate later responses with bus reset, device removal, power transitions, and local cancellation.
- Use the API's completion mechanism to release capacity rather than treating a pending status as permission to submit duplicates.
- Apply a timeout appropriate to the command and topology, not a busy loop that polls the same operation.
References
- Apple: IOFireWireFamilyCommon.h
- Apple: IOFireWireDeviceInterface
- Linux kernel: FireWire driver interface guide
Looking for a different code? Search another status or error code.