drivers/firewire/Kconfig

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