Kconfig 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. menu "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. 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.docs.kernel.org/en/latest/migration.html
  14. for information about migration from the older Linux 1394 stack
  15. to the new driver stack.
  16. To compile this driver as a module, say M here: the module will be
  17. called firewire-core.
  18. config FIREWIRE_KUNIT_UAPI_TEST
  19. tristate "KUnit tests for layout of structure in UAPI" if !KUNIT_ALL_TESTS
  20. depends on FIREWIRE && KUNIT
  21. default KUNIT_ALL_TESTS
  22. help
  23. This builds the KUnit tests whether structures exposed to user
  24. space have expected layout.
  25. KUnit tests run during boot and output the results to the debug
  26. log in TAP format (https://testanything.org/). Only useful for
  27. kernel devs running KUnit test harness and are not for inclusion
  28. into a production build.
  29. For more information on KUnit and unit tests in general, refer
  30. to the KUnit documentation in Documentation/dev-tools/kunit/.
  31. config FIREWIRE_KUNIT_DEVICE_ATTRIBUTE_TEST
  32. tristate "KUnit tests for device attributes" if !KUNIT_ALL_TESTS
  33. depends on FIREWIRE && KUNIT
  34. default KUNIT_ALL_TESTS
  35. help
  36. This builds the KUnit tests for device attribute for node and
  37. unit.
  38. KUnit tests run during boot and output the results to the debug
  39. log in TAP format (https://testanything.org/). Only useful for
  40. kernel devs running KUnit test harness and are not for inclusion
  41. into a production build.
  42. For more information on KUnit and unit tests in general, refer
  43. to the KUnit documentation in Documentation/dev-tools/kunit/.
  44. config FIREWIRE_KUNIT_PACKET_SERDES_TEST
  45. tristate "KUnit tests for packet serialization/deserialization" if !KUNIT_ALL_TESTS
  46. depends on FIREWIRE && KUNIT
  47. default KUNIT_ALL_TESTS
  48. help
  49. This builds the KUnit tests for packet serialization and
  50. deserialization.
  51. KUnit tests run during boot and output the results to the debug
  52. log in TAP format (https://testanything.org/). Only useful for
  53. kernel devs running KUnit test harness and are not for inclusion
  54. into a production build.
  55. For more information on KUnit and unit tests in general, refer
  56. to the KUnit documentation in Documentation/dev-tools/kunit/.
  57. config FIREWIRE_KUNIT_SELF_ID_SEQUENCE_HELPER_TEST
  58. tristate "KUnit tests for helpers of self ID sequence" if !KUNIT_ALL_TESTS
  59. depends on FIREWIRE && KUNIT
  60. default KUNIT_ALL_TESTS
  61. help
  62. This builds the KUnit tests for helpers of self ID sequence.
  63. KUnit tests run during boot and output the results to the debug
  64. log in TAP format (https://testanything.org/). Only useful for
  65. kernel devs running KUnit test harness and are not for inclusion
  66. into a production build.
  67. For more information on KUnit and unit tests in general, refer
  68. to the KUnit documentation in Documentation/dev-tools/kunit/.
  69. config FIREWIRE_OHCI
  70. tristate "OHCI-1394 controllers"
  71. depends on PCI && FIREWIRE && MMU
  72. help
  73. Enable this driver if you have a FireWire controller based
  74. on the OHCI specification. For all practical purposes, this
  75. is the only chipset in use, so say Y here.
  76. To compile this driver as a module, say M here: The module will be
  77. called firewire-ohci.
  78. config FIREWIRE_KUNIT_OHCI_SERDES_TEST
  79. tristate "KUnit tests for serialization/deserialization of data in buffers/registers" if !KUNIT_ALL_TESTS
  80. depends on FIREWIRE && KUNIT
  81. default KUNIT_ALL_TESTS
  82. help
  83. This builds the KUnit tests to check serialization and deserialization
  84. of data in buffers and registers defined in 1394 OHCI specification.
  85. KUnit tests run during boot and output the results to the debug
  86. log in TAP format (https://testanything.org/). Only useful for
  87. kernel devs running KUnit test harness and are not for inclusion
  88. into a production build.
  89. For more information on KUnit and unit tests in general, refer
  90. to the KUnit documentation in Documentation/dev-tools/kunit/.
  91. config FIREWIRE_SBP2
  92. tristate "Storage devices (SBP-2 protocol)"
  93. depends on FIREWIRE && SCSI
  94. help
  95. This option enables you to use SBP-2 devices connected to a
  96. FireWire bus. SBP-2 devices include storage devices like
  97. harddisks and DVD drives, also some other FireWire devices
  98. like scanners.
  99. To compile this driver as a module, say M here: The module will be
  100. called firewire-sbp2.
  101. You should also enable support for disks, CD-ROMs, etc. in the SCSI
  102. configuration section.
  103. config FIREWIRE_NET
  104. tristate "IP networking over 1394"
  105. depends on FIREWIRE && INET
  106. help
  107. This enables IPv4/IPv6 over IEEE 1394, providing IP connectivity
  108. with other implementations of RFC 2734/3146 as found on several
  109. operating systems. Multicast support is currently limited.
  110. To compile this driver as a module, say M here: The module will be
  111. called firewire-net.
  112. config FIREWIRE_NOSY
  113. tristate "Nosy - a FireWire traffic sniffer for PCILynx cards"
  114. depends on PCI
  115. help
  116. Nosy is an IEEE 1394 packet sniffer that is used for protocol
  117. analysis and in development of IEEE 1394 drivers, applications,
  118. or firmwares.
  119. This driver lets you use a Texas Instruments PCILynx 1394 to PCI
  120. link layer controller TSB12LV21/A/B as a low-budget bus analyzer.
  121. PCILynx is a nowadays very rare IEEE 1394 controller which is
  122. not OHCI 1394 compliant.
  123. The following cards are known to be based on PCILynx or PCILynx-2:
  124. IOI IOI-1394TT (PCI card), Unibrain Fireboard 400 PCI Lynx-2
  125. (PCI card), Newer Technology FireWire 2 Go (CardBus card),
  126. Apple Power Mac G3 blue & white and G4 with PCI graphics
  127. (onboard controller).
  128. To compile this driver as a module, say M here: The module will be
  129. called nosy. Source code of a userspace interface to nosy, called
  130. nosy-dump, can be found in tools/firewire/ of the kernel sources.
  131. If unsure, say N.
  132. endmenu