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