Kconfig 2.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283
  1. # -*- shell-script -*-
  2. comment "An alternative FireWire stack is available with EXPERIMENTAL=y"
  3. depends on EXPERIMENTAL=n
  4. config FIREWIRE
  5. tristate "IEEE 1394 (FireWire) support - alternative stack, EXPERIMENTAL"
  6. depends on EXPERIMENTAL
  7. select CRC_ITU_T
  8. help
  9. This is the "Juju" FireWire stack, a new alternative implementation
  10. designed for robustness and simplicity. You can build either this
  11. stack, or the classic stack (the ieee1394 driver, ohci1394 etc.)
  12. or both. Please read http://wiki.linux1394.org/JujuMigration before
  13. you enable the new stack.
  14. To compile this driver as a module, say M here: the module will be
  15. called firewire-core. It functionally replaces ieee1394, raw1394,
  16. and video1394.
  17. NOTE:
  18. You should only build ONE of the stacks, unless you REALLY know what
  19. you are doing. If you install both, you should configure them only as
  20. modules rather than link them statically, and you should blacklist one
  21. of the concurrent low-level drivers in /etc/modprobe.conf. Add either
  22. blacklist firewire-ohci
  23. or
  24. blacklist ohci1394
  25. there depending on which driver you DON'T want to have auto-loaded.
  26. You can optionally do the same with the other IEEE 1394/ FireWire
  27. drivers.
  28. If you have an old modprobe which doesn't implement the blacklist
  29. directive, use either
  30. install firewire-ohci /bin/true
  31. or
  32. install ohci1394 /bin/true
  33. and so on, depending on which modules you DON't want to have
  34. auto-loaded.
  35. config FIREWIRE_OHCI
  36. tristate "Support for OHCI FireWire host controllers"
  37. depends on PCI && FIREWIRE
  38. help
  39. Enable this driver if you have a FireWire controller based
  40. on the OHCI specification. For all practical purposes, this
  41. is the only chipset in use, so say Y here.
  42. To compile this driver as a module, say M here: The module will be
  43. called firewire-ohci. It replaces ohci1394 of the classic IEEE 1394
  44. stack.
  45. NOTE:
  46. If you also build ohci1394 of the classic stack, blacklist either
  47. ohci1394 or firewire-ohci to let hotplug load only the desired driver.
  48. config FIREWIRE_SBP2
  49. tristate "Support for storage devices (SBP-2 protocol driver)"
  50. depends on FIREWIRE && SCSI
  51. help
  52. This option enables you to use SBP-2 devices connected to a
  53. FireWire bus. SBP-2 devices include storage devices like
  54. harddisks and DVD drives, also some other FireWire devices
  55. like scanners.
  56. To compile this driver as a module, say M here: The module will be
  57. called firewire-sbp2. It replaces sbp2 of the classic IEEE 1394
  58. stack.
  59. You should also enable support for disks, CD-ROMs, etc. in the SCSI
  60. configuration section.
  61. NOTE:
  62. If you also build sbp2 of the classic stack, blacklist either sbp2
  63. or firewire-sbp2 to let hotplug load only the desired driver.