| 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" |
| 30 | depends on PCI && FIREWIRE |
| 31 | help |
| 32 | Enable this driver if you have a FireWire controller based |
| 33 | on the OHCI specification. For all practical purposes, this |
| 34 | is the only chipset in use, so say Y here. |
| 35 | |
| 36 | To compile this driver as a module, say M here: The module will be |
| 37 | called firewire-ohci. It replaces ohci1394 of the classic IEEE 1394 |
| 38 | stack. |
| 39 | |
| 40 | NOTE: |
| 41 | If you want to install firewire-ohci and ohci1394 together, you |
| 42 | should configure them only as modules and blacklist the driver(s) |
| 43 | which you don't want to have auto-loaded. Add either |
| 44 | |
| 45 | blacklist firewire-ohci |
| 46 | or |
| 47 | blacklist ohci1394 |
| 48 | blacklist video1394 |
| 49 | blacklist dv1394 |
| 50 | |
| 51 | to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf |
| 52 | depending on your distribution. |
| 53 | |
| 54 | config FIREWIRE_OHCI_DEBUG |
| 55 | bool |
| 56 | depends on FIREWIRE_OHCI |
| 57 | default y |
| 58 | |
| 59 | config FIREWIRE_SBP2 |
| 60 | tristate "Storage devices (SBP-2 protocol)" |
| 61 | depends on FIREWIRE && SCSI |
| 62 | help |
| 63 | This option enables you to use SBP-2 devices connected to a |
| 64 | FireWire bus. SBP-2 devices include storage devices like |
| 65 | harddisks and DVD drives, also some other FireWire devices |
| 66 | like scanners. |
| 67 | |
| 68 | To compile this driver as a module, say M here: The module will be |
| 69 | called firewire-sbp2. It replaces sbp2 of the classic IEEE 1394 |
| 70 | stack. |
| 71 | |
| 72 | You should also enable support for disks, CD-ROMs, etc. in the SCSI |
| 73 | configuration section. |
| 74 | |
| 75 | config FIREWIRE_NET |
| 76 | tristate "IP networking over 1394 (EXPERIMENTAL)" |
| 77 | depends on FIREWIRE && INET && EXPERIMENTAL |
| 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 | NOTE, this driver is not stable yet! |
| 84 | |
| 85 | To compile this driver as a module, say M here: The module will be |
| 86 | called firewire-net. It replaces eth1394 of the classic IEEE 1394 |
| 87 | stack. |