commit 0c53decdd0a9f9c459ccabe0b5f79660bde5375b · tjh.dev/kernel

tjh.dev / kernel

Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

kernel os linux

firewire: new stack is no longer experimental

The new stack is now recommended over the old one if used for industrial
video (IIDC/DCAM) or for storage devices (SBP-2) due to better
performance, improved compatibility, added features, and security. It
should also be functionally on par with and is more secure than the old
ieee1394 stack in the use case of consumer video devices.

IP-over-1394 support for the new stack is currently emerging, and a
backend of the firedtv DVB driver to the new stack should be available
soon.

The one remaining area where the old stack is still required are audio
devices, as the new stack is not yet able to support the FFADO FireWire
audio framework.

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>

Stefan Richter 16 years ago 0c53decd 00635b8e

+30 -41

2 changed files

expand all

unified split

drivers

firewire

Kconfig

ieee1394

Kconfig

+24 -28

drivers/firewire/Kconfig

··· 1 - comment "A new alternative FireWire stack is available with EXPERIMENTAL=y" 2 - depends on EXPERIMENTAL=n 3 - 4 - comment "Enable only one of the two stacks, unless you know what you are doing" 5 - depends on EXPERIMENTAL 6 7 config FIREWIRE 8 - tristate "New FireWire stack, EXPERIMENTAL" 9 - depends on EXPERIMENTAL 10 select CRC_ITU_T 11 help 12 - This is the "Juju" FireWire stack, a new alternative implementation 13 - designed for robustness and simplicity. You can build either this 14 - stack, or the old stack (the ieee1394 driver, ohci1394 etc.) or both. 15 - Please read http://ieee1394.wiki.kernel.org/index.php/Juju_Migration 16 - before you enable the new stack. 17 18 To compile this driver as a module, say M here: the module will be 19 called firewire-core. 20 21 This module functionally replaces ieee1394, raw1394, and video1394. 22 To access it from application programs, you generally need at least 23 - libraw1394 version 2. IIDC/DCAM applications also need libdc1394 24 - version 2. No libraries are required to access storage devices 25 - through the firewire-sbp2 driver. 26 27 config FIREWIRE_OHCI 28 tristate "OHCI-1394 controllers" ··· 38 stack. 39 40 NOTE: 41 - 42 - You should only build either firewire-ohci or the old ohci1394 driver, 43 - but not both. If you nevertheless want to install both, you should 44 - configure them only as modules and blacklist the driver(s) which you 45 - don't want to have auto-loaded. Add either 46 47 blacklist firewire-ohci 48 or ··· 49 blacklist dv1394 50 51 to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf 52 - depending on your distribution. The latter two modules should be 53 - blacklisted together with ohci1394 because they depend on ohci1394. 54 - 55 - If you have an old modprobe which doesn't implement the blacklist 56 - directive, use "install modulename /bin/true" for the modules to be 57 - blacklisted. 58 59 config FIREWIRE_OHCI_DEBUG 60 bool ··· 73 configuration section. 74 75 config FIREWIRE_NET 76 - tristate "IP networking over 1394" 77 - depends on FIREWIRE && INET 78 help 79 This enables IPv4 over IEEE 1394, providing IP connectivity with 80 other implementations of RFC 2734 as found on several operating 81 systems. Multicast support is currently limited. 82 83 To compile this driver as a module, say M here: The module will be 84 called firewire-net. It replaces eth1394 of the classic IEEE 1394

··· 1 + comment "You can enable one or both FireWire driver stacks." 2 + comment "See the help texts for more information." 3 4 config FIREWIRE 5 + tristate "FireWire driver stack" 6 select CRC_ITU_T 7 help 8 + This is the new-generation IEEE 1394 (FireWire) driver stack 9 + a.k.a. Juju, a new implementation designed for robustness and 10 + simplicity. 11 + See http://ieee1394.wiki.kernel.org/index.php/Juju_Migration 12 + for information about migration from the older Linux 1394 stack 13 + to the new driver stack. 14 15 To compile this driver as a module, say M here: the module will be 16 called firewire-core. 17 18 This module functionally replaces ieee1394, raw1394, and video1394. 19 To access it from application programs, you generally need at least 20 + libraw1394 v2. IIDC/DCAM applications need libdc1394 v2. 21 + No libraries are required to access storage devices through the 22 + firewire-sbp2 driver. 23 + 24 + NOTE: 25 + FireWire audio devices currently require the old drivers (ieee1394, 26 + ohci1394, raw1394). 27 28 config FIREWIRE_OHCI 29 tristate "OHCI-1394 controllers" ··· 37 stack. 38 39 NOTE: 40 + If you want to install firewire-ohci and ohci1394 together, you 41 + should configure them only as modules and blacklist the driver(s) 42 + which you don't want to have auto-loaded. Add either 43 44 blacklist firewire-ohci 45 or ··· 50 blacklist dv1394 51 52 to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf 53 + depending on your distribution. 54 55 config FIREWIRE_OHCI_DEBUG 56 bool ··· 79 configuration section. 80 81 config FIREWIRE_NET 82 + tristate "IP networking over 1394 (EXPERIMENTAL)" 83 + depends on FIREWIRE && INET && EXPERIMENTAL 84 help 85 This enables IPv4 over IEEE 1394, providing IP connectivity with 86 other implementations of RFC 2734 as found on several operating 87 systems. Multicast support is currently limited. 88 + 89 + NOTE, this driver is not stable yet! 90 91 To compile this driver as a module, say M here: The module will be 92 called firewire-net. It replaces eth1394 of the classic IEEE 1394

+6 -13

drivers/ieee1394/Kconfig

··· 4 source "drivers/firewire/Kconfig" 5 6 config IEEE1394 7 - tristate "Stable FireWire stack" 8 depends on PCI || BROKEN 9 help 10 IEEE 1394 describes a high performance serial bus, which is also ··· 33 module will be called ohci1394. 34 35 NOTE: 36 - 37 - You should only build either ohci1394 or the new firewire-ohci driver, 38 - but not both. If you nevertheless want to install both, you should 39 - configure them only as modules and blacklist the driver(s) which you 40 - don't want to have auto-loaded. Add either 41 42 blacklist firewire-ohci 43 or ··· 44 blacklist dv1394 45 46 to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf 47 - depending on your distribution. The latter two modules should be 48 - blacklisted together with ohci1394 because they depend on ohci1394. 49 - 50 - If you have an old modprobe which doesn't implement the blacklist 51 - directive, use "install modulename /bin/true" for the modules to be 52 - blacklisted. 53 54 comment "PCILynx controller requires I2C" 55 depends on IEEE1394 && I2C=n ··· 98 default n 99 100 config IEEE1394_ETH1394 101 - tristate "IP networking over 1394" 102 depends on IEEE1394 && EXPERIMENTAL && INET 103 select IEEE1394_ETH1394_ROM_ENTRY 104 help

··· 4 source "drivers/firewire/Kconfig" 5 6 config IEEE1394 7 + tristate "Legacy alternative FireWire driver stack" 8 depends on PCI || BROKEN 9 help 10 IEEE 1394 describes a high performance serial bus, which is also ··· 33 module will be called ohci1394. 34 35 NOTE: 36 + If you want to install firewire-ohci and ohci1394 together, you 37 + should configure them only as modules and blacklist the driver(s) 38 + which you don't want to have auto-loaded. Add either 39 40 blacklist firewire-ohci 41 or ··· 46 blacklist dv1394 47 48 to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf 49 + depending on your distribution. 50 51 comment "PCILynx controller requires I2C" 52 depends on IEEE1394 && I2C=n ··· 105 default n 106 107 config IEEE1394_ETH1394 108 + tristate "IP networking over 1394 (experimental)" 109 depends on IEEE1394 && EXPERIMENTAL && INET 110 select IEEE1394_ETH1394_ROM_ENTRY 111 help