Kconfig 5.1 KB

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