drivers/ieee1394/Kconfig

   1 # -*- shell-script -*-
   2
   3 menu "IEEE 1394 (FireWire) support"
   4
   5 config IEEE1394
   6         tristate "IEEE 1394 (FireWire) support"
   7         depends on PCI || BROKEN
   8         select NET
   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 config IEEE1394_OUI_DB
  39         bool "OUI Database built-in"
  40         depends on IEEE1394
  41         help
  42           If you say Y here, then an OUI list (vendor unique ID's) will be
  43           compiled into the ieee1394 module. This doesn't really do much
  44           except being able to display the vendor of a hardware node. The
  45           downside is that it adds about 300k to the size of the module,
  46           or kernel (depending on whether you compile ieee1394 as a
  47           module, or static in the kernel).
  48
  49           This option is not needed for userspace programs like gscanbus
  50           to show this information.
  51
  52 config IEEE1394_EXTRA_CONFIG_ROMS
  53         bool "Build in extra config rom entries for certain functionality"
  54         depends on IEEE1394
  55         help
  56           Some IEEE1394 functionality depends on extra config rom entries
  57           being available in the host adapters CSR. These options will
  58           allow you to choose which ones.
  59
  60 config IEEE1394_CONFIG_ROM_IP1394
  61         bool "IP-1394 Entry"
  62         depends on IEEE1394_EXTRA_CONFIG_ROMS && IEEE1394
  63         help
  64           Adds an entry for using IP-over-1394. If you want to use your
  65           IEEE1394 bus as a network for IP systems (including interacting
  66           with MacOSX and WinXP IP-over-1394), enable this option and the
  67           eth1394 option below.
  68
  69 comment "Device Drivers"
  70         depends on IEEE1394
  71
  72 comment "Texas Instruments PCILynx requires I2C"
  73         depends on IEEE1394 && I2C=n
  74
  75 config IEEE1394_PCILYNX
  76         tristate "Texas Instruments PCILynx support"
  77         depends on PCI && IEEE1394 && I2C
  78         select I2C_ALGOBIT
  79         help
  80           Say Y here if you have an IEEE-1394 controller with the Texas
  81           Instruments PCILynx chip.  Note: this driver is written for revision
  82           2 of this chip and may not work with revision 0.
  83
  84           To compile this driver as a module, say M here: the
  85           module will be called pcilynx.
  86
  87 # Non-maintained pcilynx options
  88 # if [ "$CONFIG_IEEE1394_PCILYNX" != "n" ]; then
  89 #     bool '    Use PCILynx local RAM' CONFIG_IEEE1394_PCILYNX_LOCALRAM
  90 #     bool '    Support for non-IEEE1394 local ports' CONFIG_IEEE1394_PCILYNX_PORTS
  91 # fi
  92 config IEEE1394_OHCI1394
  93         tristate "OHCI-1394 support"
  94         depends on PCI && IEEE1394
  95         help
  96           Enable this driver if you have an IEEE 1394 controller based on the
  97           OHCI-1394 specification. The current driver is only tested with OHCI
  98           chipsets made by Texas Instruments and NEC. Most third-party vendors
  99           use one of these chipsets.  It should work with any OHCI-1394
 100           compliant card, however.
 101
 102           To compile this driver as a module, say M here: the
 103           module will be called ohci1394.
 104
 105 comment "Protocol Drivers"
 106         depends on IEEE1394
 107
 108 config IEEE1394_VIDEO1394
 109         tristate "OHCI-1394 Video support"
 110         depends on IEEE1394 && IEEE1394_OHCI1394
 111         help
 112           This option enables video device usage for OHCI-1394 cards.  Enable
 113           this option only if you have an IEEE 1394 video device connected to
 114           an OHCI-1394 card.
 115
 116 config IEEE1394_SBP2
 117         tristate "SBP-2 support (Harddisks etc.)"
 118         depends on IEEE1394 && SCSI && (PCI || BROKEN)
 119         help
 120           This option enables you to use SBP-2 devices connected to your IEEE
 121           1394 bus.  SBP-2 devices include harddrives and DVD devices.
 122
 123 config IEEE1394_SBP2_PHYS_DMA
 124         bool "Enable Phys DMA support for SBP2 (Debug)"
 125         depends on IEEE1394 && IEEE1394_SBP2
 126
 127 config IEEE1394_ETH1394
 128         tristate "Ethernet over 1394"
 129         depends on IEEE1394 && EXPERIMENTAL && INET
 130         select IEEE1394_CONFIG_ROM_IP1394
 131         select IEEE1394_EXTRA_CONFIG_ROMS
 132         help
 133           This driver implements a functional majority of RFC 2734: IPv4 over
 134           1394.  It will provide IP connectivity with implementations of RFC
 135           2734 found on other operating systems.  It will not communicate with
 136           older versions of this driver found in stock kernels prior to 2.6.3.
 137           This driver is still considered experimental.  It does not yet support
 138           MCAP, therefore multicast support is significantly limited.
 139
 140 config IEEE1394_DV1394
 141         tristate "OHCI-DV I/O support"
 142         depends on IEEE1394 && IEEE1394_OHCI1394
 143         help
 144           This driver allows you to transmit and receive DV (digital video)
 145           streams on an OHCI-1394 card using a simple frame-oriented
 146           interface.
 147
 148           The user-space API for dv1394 is documented in dv1394.h.
 149
 150           To compile this driver as a module, say M here: the
 151           module will be called dv1394.
 152
 153 config IEEE1394_RAWIO
 154         tristate "Raw IEEE1394 I/O support"
 155         depends on IEEE1394
 156         help
 157           Say Y here if you want support for the raw device. This is generally
 158           a good idea, so you should say Y here. The raw device enables
 159           direct communication of user programs with the IEEE 1394 bus and
 160           thus with the attached peripherals.
 161
 162           To compile this driver as a module, say M here: the
 163           module will be called raw1394.
 164
 165 config IEEE1394_CMP
 166         tristate "IEC61883-1 Plug support"
 167         depends on IEEE1394
 168         help
 169           This option enables the Connection Management Procedures
 170           (IEC61883-1) driver, which implements input and output plugs.
 171
 172           To compile this driver as a module, say M here: the
 173           module will be called cmp.
 174
 175 config IEEE1394_AMDTP
 176         tristate "IEC61883-6 (Audio transmission) support"
 177         depends on IEEE1394 && IEEE1394_OHCI1394 && IEEE1394_CMP
 178         help
 179           This option enables the Audio & Music Data Transmission Protocol
 180           (IEC61883-6) driver, which implements audio transmission over
 181           IEEE1394.
 182
 183           The userspace interface is documented in amdtp.h.
 184
 185           To compile this driver as a module, say M here: the
 186           module will be called amdtp.
 187
 188 endmenu