]> bbs.cooldavid.org Git - net-next-2.6.git/blame - drivers/firewire/Kconfig
firewire: add IPv4 support
[net-next-2.6.git] / drivers / firewire / Kconfig
CommitLineData
a7b64b87 1comment "A new alternative FireWire stack is available with EXPERIMENTAL=y"
9c87da4e
SR
2 depends on EXPERIMENTAL=n
3
a7b64b87
SR
4comment "Enable only one of the two stacks, unless you know what you are doing"
5 depends on EXPERIMENTAL
6
11f494ee 7config FIREWIRE
a7b64b87 8 tristate "New FireWire stack, EXPERIMENTAL"
9c87da4e 9 depends on EXPERIMENTAL
e175569c 10 select CRC_ITU_T
3038e353 11 help
fe77d4f2 12 This is the "Juju" FireWire stack, a new alternative implementation
227e7d81 13 designed for robustness and simplicity. You can build either this
a7b64b87 14 stack, or the old stack (the ieee1394 driver, ohci1394 etc.) or both.
30b0aa7c
SR
15 Please read http://ieee1394.wiki.kernel.org/index.php/Juju_Migration
16 before you enable the new stack.
3038e353 17
fe77d4f2 18 To compile this driver as a module, say M here: the module will be
f05e21b3
SR
19 called firewire-core.
20
21 This module functionally replaces ieee1394, raw1394, and video1394.
22 To access it from application programs, you generally need at least
23 libraw1394 version 2. IIDC/DCAM applications also need libdc1394
24 version 2. No libraries are required to access storage devices
25 through the firewire-sbp2 driver.
fe77d4f2 26
11f494ee 27config FIREWIRE_OHCI
a7b64b87 28 tristate "OHCI-1394 controllers"
11f494ee 29 depends on PCI && FIREWIRE
ed568912 30 help
35b7541c 31 Enable this driver if you have a FireWire controller based
ed568912
KH
32 on the OHCI specification. For all practical purposes, this
33 is the only chipset in use, so say Y here.
34
227e7d81 35 To compile this driver as a module, say M here: The module will be
fe77d4f2
SR
36 called firewire-ohci. It replaces ohci1394 of the classic IEEE 1394
37 stack.
38
a7b64b87 39 NOTE:
227e7d81 40
a7b64b87
SR
41 You should only build either firewire-ohci or the old ohci1394 driver,
42 but not both. If you nevertheless want to install both, you should
43 configure them only as modules and blacklist the driver(s) which you
44 don't want to have auto-loaded. Add either
0a8da30d
SR
45
46 blacklist firewire-ohci
47 or
48 blacklist ohci1394
49 blacklist video1394
50 blacklist dv1394
51
52 to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf
53 depending on your distribution. The latter two modules should be
54 blacklisted together with ohci1394 because they depend on ohci1394.
55
56 If you have an old modprobe which doesn't implement the blacklist
57 directive, use "install modulename /bin/true" for the modules to be
58 blacklisted.
ed568912 59
ad3c0fe8
SR
60config FIREWIRE_OHCI_DEBUG
61 bool
62 depends on FIREWIRE_OHCI
63 default y
64
11f494ee 65config FIREWIRE_SBP2
a7b64b87 66 tristate "Storage devices (SBP-2 protocol)"
11f494ee 67 depends on FIREWIRE && SCSI
9ba136d0 68 help
35b7541c
SR
69 This option enables you to use SBP-2 devices connected to a
70 FireWire bus. SBP-2 devices include storage devices like
9ba136d0
KH
71 harddisks and DVD drives, also some other FireWire devices
72 like scanners.
73
227e7d81 74 To compile this driver as a module, say M here: The module will be
fe77d4f2
SR
75 called firewire-sbp2. It replaces sbp2 of the classic IEEE 1394
76 stack.
227e7d81 77
9ba136d0
KH
78 You should also enable support for disks, CD-ROMs, etc. in the SCSI
79 configuration section.