drivers/ieee1394/Kconfig

   1 menu "IEEE 1394 (FireWire) support"
   2         depends on PCI || BROKEN
   3
   4 source "drivers/firewire/Kconfig"
   5
   6 config IEEE1394
   7         tristate "IEEE 1394 (FireWire) support"
   8         depends on PCI || BROKEN
   9         help
  10           IEEE 1394 describes a high performance serial bus, which is also
  11           known as FireWire(tm) or i.Link(tm) and is used for connecting all
  12           sorts of devices (most notably digital video cameras) to your
  13           computer.
  14
  15           If you have FireWire hardware and want to use it, say Y here.  This
  16           is the core support only, you will also need to select a driver for
  17           your IEEE 1394 adapter.
  18
  19           To compile this driver as a module, say M here: the
  20           module will be called ieee1394.
  21
  22 comment "Subsystem Options"
  23         depends on IEEE1394
  24
  25 config IEEE1394_VERBOSEDEBUG
  26         bool "Excessive debugging output"
  27         depends on IEEE1394
  28         help
  29           If you say Y here, you will get very verbose debugging logs from
  30           the subsystem which includes a dump of the header of every sent
  31           and received packet.  This can amount to a high amount of data
  32           collected in a very short time which is usually also saved to
  33           disk by the system logging daemons.
  34
  35           Say Y if you really want or need the debugging output, everyone
  36           else says N.
  37
  38 comment "Controllers"
  39         depends on IEEE1394
  40
  41 comment "Texas Instruments PCILynx requires I2C"
  42         depends on IEEE1394 && I2C=n
  43
  44 config IEEE1394_PCILYNX
  45         tristate "Texas Instruments PCILynx support"
  46         depends on PCI && IEEE1394 && I2C
  47         select I2C_ALGOBIT
  48         help
  49           Say Y here if you have an IEEE-1394 controller with the Texas
  50           Instruments PCILynx chip.  Note: this driver is written for revision
  51           2 of this chip and may not work with revision 0.
  52
  53           To compile this driver as a module, say M here: the
  54           module will be called pcilynx.
  55
  56           Only some old and now very rare PCI and CardBus cards and
  57           PowerMacs G3 B&W contain the PCILynx controller.  Therefore
  58           almost everybody can say N here.
  59
  60 config IEEE1394_OHCI1394
  61         tristate "OHCI-1394 support"
  62         depends on PCI && IEEE1394
  63         help
  64           Enable this driver if you have an IEEE 1394 controller based on the
  65           OHCI-1394 specification. The current driver is only tested with OHCI
  66           chipsets made by Texas Instruments and NEC. Most third-party vendors
  67           use one of these chipsets.  It should work with any OHCI-1394
  68           compliant card, however.
  69
  70           To compile this driver as a module, say M here: the
  71           module will be called ohci1394.
  72
  73 comment "Protocols"
  74         depends on IEEE1394
  75
  76 config IEEE1394_VIDEO1394
  77         tristate "OHCI-1394 Video support"
  78         depends on IEEE1394 && IEEE1394_OHCI1394
  79         help
  80           This option enables video device usage for OHCI-1394 cards.  Enable
  81           this option only if you have an IEEE 1394 video device connected to
  82           an OHCI-1394 card.
  83
  84 comment "SBP-2 support (for storage devices) requires SCSI"
  85         depends on IEEE1394 && SCSI=n
  86
  87 config IEEE1394_SBP2
  88         tristate "SBP-2 support (Harddisks etc.)"
  89         depends on IEEE1394 && SCSI
  90         help
  91           This option enables you to use SBP-2 devices connected to an IEEE
  92           1394 bus.  SBP-2 devices include storage devices like harddisks and
  93           DVD drives, also some other FireWire devices like scanners.
  94
  95           You should also enable support for disks, CD-ROMs, etc. in the SCSI
  96           configuration section.
  97
  98 config IEEE1394_SBP2_PHYS_DMA
  99         bool "Enable replacement for physical DMA in SBP2"
 100         depends on IEEE1394_SBP2 && VIRT_TO_BUS && EXPERIMENTAL
 101         help
 102           This builds sbp2 for use with non-OHCI host adapters which do not
 103           support physical DMA or for when ohci1394 is run with phys_dma=0.
 104           Physical DMA is data movement without assistance of the drivers'
 105           interrupt handlers.  This option includes the interrupt handlers
 106           that are required in absence of this hardware feature.
 107
 108           This option is buggy and currently broken on some architectures.
 109           If unsure, say N.
 110
 111 config IEEE1394_ETH1394_ROM_ENTRY
 112         depends on IEEE1394
 113         bool
 114         default n
 115
 116 config IEEE1394_ETH1394
 117         tristate "IP over 1394"
 118         depends on IEEE1394 && EXPERIMENTAL && INET
 119         select IEEE1394_ETH1394_ROM_ENTRY
 120         help
 121           This driver implements a functional majority of RFC 2734: IPv4 over
 122           1394.  It will provide IP connectivity with implementations of RFC
 123           2734 found on other operating systems.  It will not communicate with
 124           older versions of this driver found in stock kernels prior to 2.6.3.
 125           This driver is still considered experimental.  It does not yet support
 126           MCAP, therefore multicast support is significantly limited.
 127
 128           The module is called eth1394 although it does not emulate Ethernet.
 129
 130 config IEEE1394_DV1394
 131         tristate "OHCI-DV I/O support (deprecated)"
 132         depends on IEEE1394 && IEEE1394_OHCI1394
 133         help
 134           The dv1394 driver is unsupported and may be removed from Linux in a
 135           future release.  Its functionality is now provided by raw1394 together
 136           with libraries such as libiec61883.
 137
 138 config IEEE1394_RAWIO
 139         tristate "Raw IEEE1394 I/O support"
 140         depends on IEEE1394
 141         help
 142           This option adds support for the raw1394 device file which enables
 143           direct communication of user programs with the IEEE 1394 bus and thus
 144           with the attached peripherals.  Almost all application programs which
 145           access FireWire require this option.
 146
 147           To compile this driver as a module, say M here: the module will be
 148           called raw1394.
 149
 150 endmenu