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