1# SPDX-License-Identifier: GPL-2.0-only 2menu "IEEE 1394 (FireWire) support" 3 depends on PCI || COMPILE_TEST 4 # firewire-core does not depend on PCI but is 5 # not useful without PCI controller driver 6 7config FIREWIRE 8 tristate "FireWire driver stack" 9 select CRC_ITU_T 10 help 11 This is the new-generation IEEE 1394 (FireWire) driver stack 12 a.k.a. Juju, a new implementation designed for robustness and 13 simplicity. 14 See http://ieee1394.wiki.kernel.org/index.php/Juju_Migration 15 for information about migration from the older Linux 1394 stack 16 to the new driver stack. 17 18 To compile this driver as a module, say M here: the module will be 19 called firewire-core. 20 21config FIREWIRE_KUNIT_UAPI_TEST 22 tristate "KUnit tests for layout of structure in UAPI" if !KUNIT_ALL_TESTS 23 depends on FIREWIRE && KUNIT 24 default KUNIT_ALL_TESTS 25 help 26 This builds the KUnit tests whether structures exposed to user 27 space have expected layout. 28 29 KUnit tests run during boot and output the results to the debug 30 log in TAP format (https://testanything.org/). Only useful for 31 kernel devs running KUnit test harness and are not for inclusion 32 into a production build. 33 34 For more information on KUnit and unit tests in general, refer 35 to the KUnit documentation in Documentation/dev-tools/kunit/. 36 37config FIREWIRE_OHCI 38 tristate "OHCI-1394 controllers" 39 depends on PCI && FIREWIRE && MMU 40 help 41 Enable this driver if you have a FireWire controller based 42 on the OHCI specification. For all practical purposes, this 43 is the only chipset in use, so say Y here. 44 45 To compile this driver as a module, say M here: The module will be 46 called firewire-ohci. 47 48config FIREWIRE_SBP2 49 tristate "Storage devices (SBP-2 protocol)" 50 depends on FIREWIRE && SCSI 51 help 52 This option enables you to use SBP-2 devices connected to a 53 FireWire bus. SBP-2 devices include storage devices like 54 harddisks and DVD drives, also some other FireWire devices 55 like scanners. 56 57 To compile this driver as a module, say M here: The module will be 58 called firewire-sbp2. 59 60 You should also enable support for disks, CD-ROMs, etc. in the SCSI 61 configuration section. 62 63config FIREWIRE_NET 64 tristate "IP networking over 1394" 65 depends on FIREWIRE && INET 66 help 67 This enables IPv4/IPv6 over IEEE 1394, providing IP connectivity 68 with other implementations of RFC 2734/3146 as found on several 69 operating systems. Multicast support is currently limited. 70 71 To compile this driver as a module, say M here: The module will be 72 called firewire-net. 73 74config FIREWIRE_NOSY 75 tristate "Nosy - a FireWire traffic sniffer for PCILynx cards" 76 depends on PCI 77 help 78 Nosy is an IEEE 1394 packet sniffer that is used for protocol 79 analysis and in development of IEEE 1394 drivers, applications, 80 or firmwares. 81 82 This driver lets you use a Texas Instruments PCILynx 1394 to PCI 83 link layer controller TSB12LV21/A/B as a low-budget bus analyzer. 84 PCILynx is a nowadays very rare IEEE 1394 controller which is 85 not OHCI 1394 compliant. 86 87 The following cards are known to be based on PCILynx or PCILynx-2: 88 IOI IOI-1394TT (PCI card), Unibrain Fireboard 400 PCI Lynx-2 89 (PCI card), Newer Technology FireWire 2 Go (CardBus card), 90 Apple Power Mac G3 blue & white and G4 with PCI graphics 91 (onboard controller). 92 93 To compile this driver as a module, say M here: The module will be 94 called nosy. Source code of a userspace interface to nosy, called 95 nosy-dump, can be found in tools/firewire/ of the kernel sources. 96 97 If unsure, say N. 98 99endmenu 100