Kconfig 2.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283
  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.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. To compile this driver as a module, say M here: the module will be
  17. called firewire-core.
  18. config FIREWIRE_OHCI
  19. tristate "OHCI-1394 controllers"
  20. depends on PCI && FIREWIRE && MMU
  21. help
  22. Enable this driver if you have a FireWire controller based
  23. on the OHCI specification. For all practical purposes, this
  24. is the only chipset in use, so say Y here.
  25. To compile this driver as a module, say M here: The module will be
  26. called firewire-ohci.
  27. config FIREWIRE_SBP2
  28. tristate "Storage devices (SBP-2 protocol)"
  29. depends on FIREWIRE && SCSI
  30. help
  31. This option enables you to use SBP-2 devices connected to a
  32. FireWire bus. SBP-2 devices include storage devices like
  33. harddisks and DVD drives, also some other FireWire devices
  34. like scanners.
  35. To compile this driver as a module, say M here: The module will be
  36. called firewire-sbp2.
  37. You should also enable support for disks, CD-ROMs, etc. in the SCSI
  38. configuration section.
  39. config FIREWIRE_NET
  40. tristate "IP networking over 1394"
  41. depends on FIREWIRE && INET
  42. help
  43. This enables IPv4/IPv6 over IEEE 1394, providing IP connectivity
  44. with other implementations of RFC 2734/3146 as found on several
  45. operating systems. Multicast support is currently limited.
  46. To compile this driver as a module, say M here: The module will be
  47. called firewire-net.
  48. config FIREWIRE_NOSY
  49. tristate "Nosy - a FireWire traffic sniffer for PCILynx cards"
  50. depends on PCI
  51. help
  52. Nosy is an IEEE 1394 packet sniffer that is used for protocol
  53. analysis and in development of IEEE 1394 drivers, applications,
  54. or firmwares.
  55. This driver lets you use a Texas Instruments PCILynx 1394 to PCI
  56. link layer controller TSB12LV21/A/B as a low-budget bus analyzer.
  57. PCILynx is a nowadays very rare IEEE 1394 controller which is
  58. not OHCI 1394 compliant.
  59. The following cards are known to be based on PCILynx or PCILynx-2:
  60. IOI IOI-1394TT (PCI card), Unibrain Fireboard 400 PCI Lynx-2
  61. (PCI card), Newer Technology FireWire 2 Go (CardBus card),
  62. Apple Power Mac G3 blue & white and G4 with PCI graphics
  63. (onboard controller).
  64. To compile this driver as a module, say M here: The module will be
  65. called nosy. Source code of a userspace interface to nosy, called
  66. nosy-dump, can be found in tools/firewire/ of the kernel sources.
  67. If unsure, say N.
  68. endmenu