ieee1394(4) manual page

To compile this driver into the kernel, place the following line in your kernel configuration file: device firewire

Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

firewire_load="YES"

FreeBSD provides machine-independent bus support and raw drivers for firewire interfaces.

The firewire driver consists of two layers: the controller and the bus layer. The controller attaches to a physical bus (like pci(4)). The firewire bus attaches to the controller. Additional drivers can be attached to the bus.

Up to 63 devices, including the host itself, can be attached to a firewire bus. The root node is dynamically assigned with a PHY device function. Also, the other firewire bus specific parameters, e.g., node ID, cycle master, isochronous resource manager and bus manager, are dynamically assigned, after bus reset is initiated. On the firewire bus, every device is identified by an EUI 64 address.

Debugging over the firewire interface is possible with the dcons(4) driver. Please see
.Lk https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-dcons for details on how to setup debugging with firewire.

dcons(4), fwe(4), fwip(4), fwohci(4), pci(4), sbp(4), eui64(5), fwcontrol(8), kldload(8), sysctl(8)

See fwohci(4) for security notes.

“	Never write it in C if you can do it in `awk'; Never do it in `awk' if `sed' can handle it; Never use `sed' when `tr' can do the job; Never invoke `tr' when `cat' is sufficient; Avoid using `cat' whenever possible.	”
— Taylor's Laws of Programming

Manual Pages — FIREWIRE

NAME

CONTENTS

SYNOPSIS

DESCRIPTION

FILES

SEE ALSO

HISTORY

AUTHORS

BUGS

`/dev/fw0.0` `/dev/fwmem0.0`