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.docs.kernel.org/en/latest/migration.html 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_KUNIT_DEVICE_ATTRIBUTE_TEST 38 tristate "KUnit tests for device attributes" if !KUNIT_ALL_TESTS 39 depends on FIREWIRE && KUNIT 40 default KUNIT_ALL_TESTS 41 help 42 This builds the KUnit tests for device attribute for node and 43 unit. 44 45 KUnit tests run during boot and output the results to the debug 46 log in TAP format (https://testanything.org/). Only useful for 47 kernel devs running KUnit test harness and are not for inclusion 48 into a production build. 49 50 For more information on KUnit and unit tests in general, refer 51 to the KUnit documentation in Documentation/dev-tools/kunit/. 52 53config FIREWIRE_KUNIT_PACKET_SERDES_TEST 54 tristate "KUnit tests for packet serialization/deserialization" if !KUNIT_ALL_TESTS 55 depends on FIREWIRE && KUNIT 56 default KUNIT_ALL_TESTS 57 help 58 This builds the KUnit tests for packet serialization and 59 deserialization. 60 61 KUnit tests run during boot and output the results to the debug 62 log in TAP format (https://testanything.org/). Only useful for 63 kernel devs running KUnit test harness and are not for inclusion 64 into a production build. 65 66 For more information on KUnit and unit tests in general, refer 67 to the KUnit documentation in Documentation/dev-tools/kunit/. 68 69config FIREWIRE_KUNIT_SELF_ID_SEQUENCE_HELPER_TEST 70 tristate "KUnit tests for helpers of self ID sequence" if !KUNIT_ALL_TESTS 71 depends on FIREWIRE && KUNIT 72 default KUNIT_ALL_TESTS 73 help 74 This builds the KUnit tests for helpers of self ID sequence. 75 76 KUnit tests run during boot and output the results to the debug 77 log in TAP format (https://testanything.org/). Only useful for 78 kernel devs running KUnit test harness and are not for inclusion 79 into a production build. 80 81 For more information on KUnit and unit tests in general, refer 82 to the KUnit documentation in Documentation/dev-tools/kunit/. 83 84config FIREWIRE_KUNIT_NODE_TREE_TEST 85 tristate "KUnit tests for node tree" if !KUNIT_ALL_TESTS 86 depends on FIREWIRE && KUNIT 87 default KUNIT_ALL_TESTS 88 help 89 This builds the KUnit tests for node tree. 90 91 KUnit tests run during boot and output the results to the debug 92 log in TAP format (https://testanything.org/). Only useful for 93 kernel devs running KUnit test harness and are not for inclusion 94 into a production build. 95 96 For more information on KUnit and unit tests in general, refer 97 to the KUnit documentation in Documentation/dev-tools/kunit/. 98 99config FIREWIRE_OHCI 100 tristate "OHCI-1394 controllers" 101 depends on PCI && FIREWIRE 102 help 103 Enable this driver if you have a FireWire controller based 104 on the OHCI specification. For all practical purposes, this 105 is the only chipset in use, so say Y here. 106 107 To compile this driver as a module, say M here: The module will be 108 called firewire-ohci. 109 110config FIREWIRE_KUNIT_OHCI_SERDES_TEST 111 tristate "KUnit tests for serialization/deserialization of data in buffers/registers" if !KUNIT_ALL_TESTS 112 depends on FIREWIRE && KUNIT 113 default KUNIT_ALL_TESTS 114 help 115 This builds the KUnit tests to check serialization and deserialization 116 of data in buffers and registers defined in 1394 OHCI specification. 117 118 KUnit tests run during boot and output the results to the debug 119 log in TAP format (https://testanything.org/). Only useful for 120 kernel devs running KUnit test harness and are not for inclusion 121 into a production build. 122 123 For more information on KUnit and unit tests in general, refer 124 to the KUnit documentation in Documentation/dev-tools/kunit/. 125 126config FIREWIRE_SBP2 127 tristate "Storage devices (SBP-2 protocol)" 128 depends on FIREWIRE && SCSI 129 help 130 This option enables you to use SBP-2 devices connected to a 131 FireWire bus. SBP-2 devices include storage devices like 132 harddisks and DVD drives, also some other FireWire devices 133 like scanners. 134 135 To compile this driver as a module, say M here: The module will be 136 called firewire-sbp2. 137 138 You should also enable support for disks, CD-ROMs, etc. in the SCSI 139 configuration section. 140 141config FIREWIRE_NET 142 tristate "IP networking over 1394" 143 depends on FIREWIRE && INET 144 help 145 This enables IPv4/IPv6 over IEEE 1394, providing IP connectivity 146 with other implementations of RFC 2734/3146 as found on several 147 operating systems. Multicast support is currently limited. 148 149 To compile this driver as a module, say M here: The module will be 150 called firewire-net. 151 152config FIREWIRE_NOSY 153 tristate "Nosy - a FireWire traffic sniffer for PCILynx cards" 154 depends on PCI 155 help 156 Nosy is an IEEE 1394 packet sniffer that is used for protocol 157 analysis and in development of IEEE 1394 drivers, applications, 158 or firmwares. 159 160 This driver lets you use a Texas Instruments PCILynx 1394 to PCI 161 link layer controller TSB12LV21/A/B as a low-budget bus analyzer. 162 PCILynx is a nowadays very rare IEEE 1394 controller which is 163 not OHCI 1394 compliant. 164 165 The following cards are known to be based on PCILynx or PCILynx-2: 166 IOI IOI-1394TT (PCI card), Unibrain Fireboard 400 PCI Lynx-2 167 (PCI card), Newer Technology FireWire 2 Go (CardBus card), 168 Apple Power Mac G3 blue & white and G4 with PCI graphics 169 (onboard controller). 170 171 To compile this driver as a module, say M here: The module will be 172 called nosy. Source code of a userspace interface to nosy, called 173 nosy-dump, can be found in tools/firewire/ of the kernel sources. 174 175 If unsure, say N. 176 177endmenu 178