1menu "IEEE 1394 (FireWire) support" 2 depends on PCI || BROKEN 3 # firewire-core does not depend on PCI but is 4 # not useful without PCI controller driver 5 6comment "You can enable one or both FireWire driver stacks." 7comment "The newer stack is recommended." 8 9config FIREWIRE 10 tristate "FireWire driver stack" 11 select CRC_ITU_T 12 help 13 This is the new-generation IEEE 1394 (FireWire) driver stack 14 a.k.a. Juju, a new implementation designed for robustness and 15 simplicity. 16 See http://ieee1394.wiki.kernel.org/index.php/Juju_Migration 17 for information about migration from the older Linux 1394 stack 18 to the new driver stack. 19 20 To compile this driver as a module, say M here: the module will be 21 called firewire-core. 22 23config FIREWIRE_OHCI 24 tristate "OHCI-1394 controllers" 25 depends on PCI && FIREWIRE 26 help 27 Enable this driver if you have a FireWire controller based 28 on the OHCI specification. For all practical purposes, this 29 is the only chipset in use, so say Y here. 30 31 To compile this driver as a module, say M here: The module will be 32 called firewire-ohci. 33 34config FIREWIRE_OHCI_DEBUG 35 bool 36 depends on FIREWIRE_OHCI 37 default y 38 39config FIREWIRE_SBP2 40 tristate "Storage devices (SBP-2 protocol)" 41 depends on FIREWIRE && SCSI 42 help 43 This option enables you to use SBP-2 devices connected to a 44 FireWire bus. SBP-2 devices include storage devices like 45 harddisks and DVD drives, also some other FireWire devices 46 like scanners. 47 48 To compile this driver as a module, say M here: The module will be 49 called firewire-sbp2. 50 51 You should also enable support for disks, CD-ROMs, etc. in the SCSI 52 configuration section. 53 54config FIREWIRE_NET 55 tristate "IP networking over 1394 (EXPERIMENTAL)" 56 depends on FIREWIRE && INET && EXPERIMENTAL 57 help 58 This enables IPv4 over IEEE 1394, providing IP connectivity with 59 other implementations of RFC 2734 as found on several operating 60 systems. Multicast support is currently limited. 61 62 NOTE, this driver is not stable yet! 63 64 To compile this driver as a module, say M here: The module will be 65 called firewire-net. 66 67source "drivers/ieee1394/Kconfig" 68 69config FIREWIRE_NOSY 70 tristate "Nosy - a FireWire traffic sniffer for PCILynx cards" 71 depends on PCI 72 help 73 Nosy is an IEEE 1394 packet sniffer that is used for protocol 74 analysis and in development of IEEE 1394 drivers, applications, 75 or firmwares. 76 77 This driver lets you use a Texas Instruments PCILynx 1394 to PCI 78 link layer controller TSB12LV21/A/B as a low-budget bus analyzer. 79 PCILynx is a nowadays very rare IEEE 1394 controller which is 80 not OHCI 1394 compliant. 81 82 The following cards are known to be based on PCILynx or PCILynx-2: 83 IOI IOI-1394TT (PCI card), Unibrain Fireboard 400 PCI Lynx-2 84 (PCI card), Newer Technology FireWire 2 Go (CardBus card), 85 Apple Power Mac G3 blue & white (onboard controller). 86 87 To compile this driver as a module, say M here: The module will be 88 called nosy. 89 90 If unsure, say N. 91 92endmenu 93