# SPDX-License-Identifier: GPL-2.0-only menu "IEEE 1394 (FireWire) support" depends on [31mCONFIG_PCI[0m || [31mCONFIG_COMPILE_TEST[0m # firewire-core does not depend on [31mCONFIG_PCI[0m but is # not useful without [31mCONFIG_PCI[0m controller driver config [31mCONFIG_FIREWIRE[0m tristate "FireWire driver stack" select [31mCONFIG_CRC_ITU_T[0m help This is the new-generation IEEE 1394 (FireWire) driver stack a.k.a. Juju, a new implementation designed for robustness and simplicity. See http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for information about migration from the older Linux 1394 stack to the new driver stack. To compile this driver as a module, say [31mCONFIG_M[0m here: the module will be called firewire-core. config [31mCONFIG_FIREWIRE_OHCI[0m tristate "OHCI-1394 controllers" depends on [31mCONFIG_PCI[0m && [31mCONFIG_FIREWIRE[0m && [31mCONFIG_MMU[0m help Enable this driver if you have a FireWire controller based on the OHCI specification. For all practical purposes, this is the only chipset in use, so say Y here. To compile this driver as a module, say [31mCONFIG_M[0m here: The module will be called firewire-ohci. config [31mCONFIG_FIREWIRE_SBP2[0m tristate "Storage devices (SBP-2 protocol)" depends on [31mCONFIG_FIREWIRE[0m && [31mCONFIG_SCSI[0m help This option enables you to use SBP-2 devices connected to a FireWire bus. SBP-2 devices include storage devices like harddisks and DVD drives, also some other FireWire devices like scanners. To compile this driver as a module, say [31mCONFIG_M[0m here: The module will be called firewire-sbp2. You should also enable support for disks, CD-ROMs, etc. in the [31mCONFIG_SCSI[0m configuration section. config [31mCONFIG_FIREWIRE_NET[0m tristate "IP networking over 1394" depends on [31mCONFIG_FIREWIRE[0m && [31mCONFIG_INET[0m help This enables IPv4/IPv6 over IEEE 1394, providing IP connectivity with other implementations of RFC 2734/3146 as found on several operating systems. Multicast support is currently limited. To compile this driver as a module, say [31mCONFIG_M[0m here: The module will be called firewire-net. config [31mCONFIG_FIREWIRE_NOSY[0m tristate "Nosy - a FireWire traffic sniffer for PCILynx cards" depends on [31mCONFIG_PCI[0m help Nosy is an IEEE 1394 packet sniffer that is used for protocol analysis and in development of IEEE 1394 drivers, applications, or firmwares. This driver lets you use a Texas Instruments PCILynx 1394 to [31mCONFIG_PCI[0m link layer controller TSB12LV21/[31mCONFIG_A[0m/[31mCONFIG_B[0m as a low-budget bus analyzer. PCILynx is a nowadays very rare IEEE 1394 controller which is not OHCI 1394 compliant. The following cards are known to be based on PCILynx or PCILynx-2: IOI IOI-1394TT ([31mCONFIG_PCI[0m card), Unibrain Fireboard 400 [31mCONFIG_PCI[0m Lynx-2 ([31mCONFIG_PCI[0m card), Newer Technology FireWire 2 Go (CardBus card), Apple Power Mac G3 blue & white and G4 with [31mCONFIG_PCI[0m graphics (onboard controller). To compile this driver as a module, say [31mCONFIG_M[0m here: The module will be called nosy. Source code of a userspace interface to nosy, called nosy-dump, can be found in tools/firewire/ of the kernel sources. If unsure, say N. endmenu |