diff options
author | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-04-30 11:59:57 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-04-30 11:59:57 -0400 |
commit | 40caf5ea5a7d47f8a33e26b63ca81dea4b5109d2 (patch) | |
tree | 3f879353d5cb69d2dee707108e4aaeae075f5a0c /drivers/ieee1394/Kconfig | |
parent | d6454706c382ab74e2ecad7803c434cc6bd30343 (diff) | |
parent | bcfd09ee48f77a4fe903dbc3757e7af931998ce1 (diff) |
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6: (56 commits)
ieee1394: remove garbage from Kconfig
ieee1394: more help in Kconfig
ieee1394: ohci1394: Fix mistake in printk message.
ieee1394: ohci1394: remove unnecessary rcvPhyPkt bit flipping in LinkControl register
ieee1394: ohci1394: fix cosmetic problem in error logging
ieee1394: eth1394: send async streams at S100 on 1394b buses
ieee1394: eth1394: fix error path in module_init
ieee1394: eth1394: correct return codes in hard_start_xmit
ieee1394: eth1394: hard_start_xmit is called in atomic context
ieee1394: eth1394: some conditions are unlikely
ieee1394: eth1394: clean up fragment_overlap
ieee1394: eth1394: don't use alloc_etherdev
ieee1394: eth1394: omit useless set_mac_address callback
ieee1394: eth1394: CONFIG_INET is always defined
ieee1394: eth1394: allow MTU bigger than 1500
ieee1394: unexport highlevel_host_reset
ieee1394: eth1394: contain host reset
ieee1394: eth1394: shorter error messages
ieee1394: eth1394: correct a memset argument
ieee1394: eth1394: refactor .probe and .update
...
Diffstat (limited to 'drivers/ieee1394/Kconfig')
-rw-r--r-- | drivers/ieee1394/Kconfig | 52 |
1 files changed, 21 insertions, 31 deletions
diff --git a/drivers/ieee1394/Kconfig b/drivers/ieee1394/Kconfig index cd84a55ecf20..61d7809a5a26 100644 --- a/drivers/ieee1394/Kconfig +++ b/drivers/ieee1394/Kconfig | |||
@@ -1,11 +1,8 @@ | |||
1 | # -*- shell-script -*- | ||
2 | |||
3 | menu "IEEE 1394 (FireWire) support" | 1 | menu "IEEE 1394 (FireWire) support" |
4 | 2 | ||
5 | config IEEE1394 | 3 | config IEEE1394 |
6 | tristate "IEEE 1394 (FireWire) support" | 4 | tristate "IEEE 1394 (FireWire) support" |
7 | depends on PCI || BROKEN | 5 | depends on PCI || BROKEN |
8 | select NET | ||
9 | help | 6 | help |
10 | IEEE 1394 describes a high performance serial bus, which is also | 7 | IEEE 1394 describes a high performance serial bus, which is also |
11 | known as FireWire(tm) or i.Link(tm) and is used for connecting all | 8 | known as FireWire(tm) or i.Link(tm) and is used for connecting all |
@@ -35,24 +32,7 @@ config IEEE1394_VERBOSEDEBUG | |||
35 | Say Y if you really want or need the debugging output, everyone | 32 | Say Y if you really want or need the debugging output, everyone |
36 | else says N. | 33 | else says N. |
37 | 34 | ||
38 | config IEEE1394_EXTRA_CONFIG_ROMS | 35 | comment "Controllers" |
39 | bool "Build in extra config rom entries for certain functionality" | ||
40 | depends on IEEE1394 | ||
41 | help | ||
42 | Some IEEE1394 functionality depends on extra config rom entries | ||
43 | being available in the host adapters CSR. These options will | ||
44 | allow you to choose which ones. | ||
45 | |||
46 | config IEEE1394_CONFIG_ROM_IP1394 | ||
47 | bool "IP-1394 Entry" | ||
48 | depends on IEEE1394_EXTRA_CONFIG_ROMS && IEEE1394 | ||
49 | help | ||
50 | Adds an entry for using IP-over-1394. If you want to use your | ||
51 | IEEE1394 bus as a network for IP systems (including interacting | ||
52 | with MacOSX and WinXP IP-over-1394), enable this option and the | ||
53 | eth1394 option below. | ||
54 | |||
55 | comment "Device Drivers" | ||
56 | depends on IEEE1394 | 36 | depends on IEEE1394 |
57 | 37 | ||
58 | comment "Texas Instruments PCILynx requires I2C" | 38 | comment "Texas Instruments PCILynx requires I2C" |
@@ -70,6 +50,10 @@ config IEEE1394_PCILYNX | |||
70 | To compile this driver as a module, say M here: the | 50 | To compile this driver as a module, say M here: the |
71 | module will be called pcilynx. | 51 | module will be called pcilynx. |
72 | 52 | ||
53 | Only some old and now very rare PCI and CardBus cards and | ||
54 | PowerMacs G3 B&W contain the PCILynx controller. Therefore | ||
55 | almost everybody can say N here. | ||
56 | |||
73 | config IEEE1394_OHCI1394 | 57 | config IEEE1394_OHCI1394 |
74 | tristate "OHCI-1394 support" | 58 | tristate "OHCI-1394 support" |
75 | depends on PCI && IEEE1394 | 59 | depends on PCI && IEEE1394 |
@@ -83,7 +67,7 @@ config IEEE1394_OHCI1394 | |||
83 | To compile this driver as a module, say M here: the | 67 | To compile this driver as a module, say M here: the |
84 | module will be called ohci1394. | 68 | module will be called ohci1394. |
85 | 69 | ||
86 | comment "Protocol Drivers" | 70 | comment "Protocols" |
87 | depends on IEEE1394 | 71 | depends on IEEE1394 |
88 | 72 | ||
89 | config IEEE1394_VIDEO1394 | 73 | config IEEE1394_VIDEO1394 |
@@ -121,11 +105,15 @@ config IEEE1394_SBP2_PHYS_DMA | |||
121 | This option is buggy and currently broken on some architectures. | 105 | This option is buggy and currently broken on some architectures. |
122 | If unsure, say N. | 106 | If unsure, say N. |
123 | 107 | ||
108 | config IEEE1394_ETH1394_ROM_ENTRY | ||
109 | depends on IEEE1394 | ||
110 | bool | ||
111 | default n | ||
112 | |||
124 | config IEEE1394_ETH1394 | 113 | config IEEE1394_ETH1394 |
125 | tristate "Ethernet over 1394" | 114 | tristate "IP over 1394" |
126 | depends on IEEE1394 && EXPERIMENTAL && INET | 115 | depends on IEEE1394 && EXPERIMENTAL && INET |
127 | select IEEE1394_CONFIG_ROM_IP1394 | 116 | select IEEE1394_ETH1394_ROM_ENTRY |
128 | select IEEE1394_EXTRA_CONFIG_ROMS | ||
129 | help | 117 | help |
130 | This driver implements a functional majority of RFC 2734: IPv4 over | 118 | This driver implements a functional majority of RFC 2734: IPv4 over |
131 | 1394. It will provide IP connectivity with implementations of RFC | 119 | 1394. It will provide IP connectivity with implementations of RFC |
@@ -134,6 +122,8 @@ config IEEE1394_ETH1394 | |||
134 | This driver is still considered experimental. It does not yet support | 122 | This driver is still considered experimental. It does not yet support |
135 | MCAP, therefore multicast support is significantly limited. | 123 | MCAP, therefore multicast support is significantly limited. |
136 | 124 | ||
125 | The module is called eth1394 although it does not emulate Ethernet. | ||
126 | |||
137 | config IEEE1394_DV1394 | 127 | config IEEE1394_DV1394 |
138 | tristate "OHCI-DV I/O support (deprecated)" | 128 | tristate "OHCI-DV I/O support (deprecated)" |
139 | depends on IEEE1394 && IEEE1394_OHCI1394 | 129 | depends on IEEE1394 && IEEE1394_OHCI1394 |
@@ -146,12 +136,12 @@ config IEEE1394_RAWIO | |||
146 | tristate "Raw IEEE1394 I/O support" | 136 | tristate "Raw IEEE1394 I/O support" |
147 | depends on IEEE1394 | 137 | depends on IEEE1394 |
148 | help | 138 | help |
149 | Say Y here if you want support for the raw device. This is generally | 139 | This option adds support for the raw1394 device file which enables |
150 | a good idea, so you should say Y here. The raw device enables | 140 | direct communication of user programs with the IEEE 1394 bus and thus |
151 | direct communication of user programs with the IEEE 1394 bus and | 141 | with the attached peripherals. Almost all application programs which |
152 | thus with the attached peripherals. | 142 | access FireWire require this option. |
153 | 143 | ||
154 | To compile this driver as a module, say M here: the | 144 | To compile this driver as a module, say M here: the module will be |
155 | module will be called raw1394. | 145 | called raw1394. |
156 | 146 | ||
157 | endmenu | 147 | endmenu |