Kconfig 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  1. menu "IEEE 1394 (FireWire) support"
  2. depends on PCI || BROKEN
  3. # firewire-core does not depend on PCI but is
  4. # not useful without PCI controller driver
  5. config FIREWIRE
  6. tristate "FireWire driver stack"
  7. select CRC_ITU_T
  8. help
  9. This is the new-generation IEEE 1394 (FireWire) driver stack
  10. a.k.a. Juju, a new implementation designed for robustness and
  11. simplicity.
  12. See http://ieee1394.wiki.kernel.org/index.php/Juju_Migration
  13. for information about migration from the older Linux 1394 stack
  14. to the new driver stack.
  15. To compile this driver as a module, say M here: the module will be
  16. called firewire-core.
  17. config FIREWIRE_OHCI
  18. tristate "OHCI-1394 controllers"
  19. depends on PCI && FIREWIRE && MMU
  20. help
  21. Enable this driver if you have a FireWire controller based
  22. on the OHCI specification. For all practical purposes, this
  23. is the only chipset in use, so say Y here.
  24. To compile this driver as a module, say M here: The module will be
  25. called firewire-ohci.
  26. config FIREWIRE_OHCI_DEBUG
  27. bool
  28. depends on FIREWIRE_OHCI
  29. default y
  30. config FIREWIRE_SBP2
  31. tristate "Storage devices (SBP-2 protocol)"
  32. depends on FIREWIRE && SCSI
  33. help
  34. This option enables you to use SBP-2 devices connected to a
  35. FireWire bus. SBP-2 devices include storage devices like
  36. harddisks and DVD drives, also some other FireWire devices
  37. like scanners.
  38. To compile this driver as a module, say M here: The module will be
  39. called firewire-sbp2.
  40. You should also enable support for disks, CD-ROMs, etc. in the SCSI
  41. configuration section.
  42. config FIREWIRE_NET
  43. tristate "IP networking over 1394"
  44. depends on FIREWIRE && INET
  45. help
  46. This enables IPv4 over IEEE 1394, providing IP connectivity with
  47. other implementations of RFC 2734 as found on several operating
  48. systems. Multicast support is currently limited.
  49. To compile this driver as a module, say M here: The module will be
  50. called firewire-net.
  51. config FIREWIRE_NOSY
  52. tristate "Nosy - a FireWire traffic sniffer for PCILynx cards"
  53. depends on PCI
  54. help
  55. Nosy is an IEEE 1394 packet sniffer that is used for protocol
  56. analysis and in development of IEEE 1394 drivers, applications,
  57. or firmwares.
  58. This driver lets you use a Texas Instruments PCILynx 1394 to PCI
  59. link layer controller TSB12LV21/A/B as a low-budget bus analyzer.
  60. PCILynx is a nowadays very rare IEEE 1394 controller which is
  61. not OHCI 1394 compliant.
  62. The following cards are known to be based on PCILynx or PCILynx-2:
  63. IOI IOI-1394TT (PCI card), Unibrain Fireboard 400 PCI Lynx-2
  64. (PCI card), Newer Technology FireWire 2 Go (CardBus card),
  65. Apple Power Mac G3 blue & white and G4 with PCI graphics
  66. (onboard controller).
  67. To compile this driver as a module, say M here: The module will be
  68. called nosy. Source code of a userspace interface to nosy, called
  69. nosy-dump, can be found in tools/firewire/ of the kernel sources.
  70. If unsure, say N.
  71. endmenu