Lines Matching +full:stream +full:- +full:id +full:- +full:range

1 What:		/dev/fw[0-9]+
4 Contact:	linux1394-[email protected]
7 		firewire-core and IEEE 1394 device drivers implemented in
8 		userspace.  The ioctl(2)- and read(2)-based ABI is defined and
9 		documented in <linux/firewire-cdev.h>.
11 		This ABI offers most of the features which firewire-core also
18 		  - The 1394 node which is associated with the file:
20 			  - Asynchronous request transmission
21 			  - Get the Configuration ROM
22 			  - Query node ID
23 			  - Query maximum speed of the path between this node
26 		  - The 1394 bus (i.e. "card") to which the node is attached to:
28 			  - Isochronous stream transmission and reception
29 			  - Asynchronous stream transmission and reception
30 			  - Asynchronous broadcast request transmission
31 			  - PHY packet transmission and reception
32 			  - Allocate, reallocate, deallocate isochronous
34 			  - Query node IDs of local node, root node, IRM, bus
36 			  - Query cycle time
37 			  - Bus reset initiation, bus reset event reception
39 		  - All 1394 buses:
41 			  - Allocation of IEEE 1212 address ranges on the local
43 			    an address range, asynchronous response transmission
45 			  - Addition of descriptors or directories to the local
53 			  - Addition of descriptors or directories to the local
55 			  - PHY packet transmission and reception
59 		node ID changes, are tracked by firewire-core.  ABI users do not
70 		    See the inline documentation in <linux/firewire-cdev.h> for
82 		    could ever arrive.  See <linux/firewire-cdev.h> for descriptions
95 		Isochronous reception works in packet-per-buffer fashion except
96 		for multichannel reception which works in buffer-fill mode.
105 		    bandwidth at the IRM that were marked for kernel-assisted
106 		    re- and deallocation.
111 		tools like linux-firewire-utils, fwhack, ...