#include <firewire-cdev.h>

Data Fields
__u32	type

__u32	header_size

__u32	channel

__u32	speed

__u64	closure

__u32	handle

Detailed Description

struct fw_cdev_create_iso_context - Create a context for isochronous I/O : FW_CDEV_ISO_CONTEXT_TRANSMIT or FW_CDEV_ISO_CONTEXT_RECEIVE or FW_CDEV_ISO_CONTEXT_RECEIVE_MULTICHANNEL : Header size to strip in single-channel reception : Channel to bind to in single-channel reception or transmission : Transmission speed : To be returned in &fw_cdev_event_iso_interrupt or &fw_cdev_event_iso_interrupt_multichannel : Handle to context, written back by kernel

Prior to sending or receiving isochronous I/O, a context must be created. The context records information about the transmit or receive configuration and typically maps to an underlying hardware resource. A context is set up for either sending or receiving. It is bound to a specific isochronous .

In case of multichannel reception, and are ignored and the channels are selected by FW_CDEV_IOC_SET_ISO_CHANNELS.

For FW_CDEV_ISO_CONTEXT_RECEIVE contexts, must be at least 4 and must be a multiple of 4. It is ignored in other context types.

is ignored in receive context types.

If a context was successfully created, the kernel writes back a handle to the context, which must be passed in for subsequent operations on that context.

Limitations: No more than one iso context can be created per fd. The total number of contexts that all userspace and kernelspace drivers can create on a card at a time is a hardware limit, typically 4 or 8 contexts per direction, and of them at most one multichannel receive context.

Definition at line 696 of file firewire-cdev.h.