cachepc-linux

Fork of AMDESE/linux with modifications for CachePC side-channel attack
git clone https://git.sinitax.com/sinitax/cachepc-linux
Log | Files | Refs | README | LICENSE | sfeed.txt

Kconfig (2938B)

      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_OHCI
     22	tristate "OHCI-1394 controllers"
     23	depends on PCI && FIREWIRE && MMU
     24	help
     25	  Enable this driver if you have a FireWire controller based
     26	  on the OHCI specification.  For all practical purposes, this
     27	  is the only chipset in use, so say Y here.
     28
     29	  To compile this driver as a module, say M here:  The module will be
     30	  called firewire-ohci.
     31
     32config FIREWIRE_SBP2
     33	tristate "Storage devices (SBP-2 protocol)"
     34	depends on FIREWIRE && SCSI
     35	help
     36	  This option enables you to use SBP-2 devices connected to a
     37	  FireWire bus.  SBP-2 devices include storage devices like
     38	  harddisks and DVD drives, also some other FireWire devices
     39	  like scanners.
     40
     41	  To compile this driver as a module, say M here:  The module will be
     42	  called firewire-sbp2.
     43
     44	  You should also enable support for disks, CD-ROMs, etc. in the SCSI
     45	  configuration section.
     46
     47config FIREWIRE_NET
     48	tristate "IP networking over 1394"
     49	depends on FIREWIRE && INET
     50	help
     51	  This enables IPv4/IPv6 over IEEE 1394, providing IP connectivity
     52	  with other implementations of RFC 2734/3146 as found on several
     53	  operating systems.  Multicast support is currently limited.
     54
     55	  To compile this driver as a module, say M here:  The module will be
     56	  called firewire-net.
     57
     58config FIREWIRE_NOSY
     59	tristate "Nosy - a FireWire traffic sniffer for PCILynx cards"
     60	depends on PCI
     61	help
     62	  Nosy is an IEEE 1394 packet sniffer that is used for protocol
     63	  analysis and in development of IEEE 1394 drivers, applications,
     64	  or firmwares.
     65
     66	  This driver lets you use a Texas Instruments PCILynx 1394 to PCI
     67	  link layer controller TSB12LV21/A/B as a low-budget bus analyzer.
     68	  PCILynx is a nowadays very rare IEEE 1394 controller which is
     69	  not OHCI 1394 compliant.
     70
     71	  The following cards are known to be based on PCILynx or PCILynx-2:
     72	  IOI IOI-1394TT (PCI card), Unibrain Fireboard 400 PCI Lynx-2
     73	  (PCI card), Newer Technology FireWire 2 Go (CardBus card),
     74	  Apple Power Mac G3 blue & white and G4 with PCI graphics
     75	  (onboard controller).
     76
     77	  To compile this driver as a module, say M here:  The module will be
     78	  called nosy.  Source code of a userspace interface to nosy, called
     79	  nosy-dump, can be found in tools/firewire/ of the kernel sources.
     80
     81	  If unsure, say N.
     82
     83endmenu