diff options
author | Krzysztof Halasa <khc@pm.waw.pl> | 2006-11-13 13:48:54 -0500 |
---|---|---|
committer | Jeff Garzik <jeff@garzik.org> | 2006-12-02 00:12:03 -0500 |
commit | b690bdef7c4523bf55103b7a841c454d4674b315 (patch) | |
tree | 5c41f3e64d01baf7fe5d413cd92bb7485ea98f5d /drivers/net/wan/Kconfig | |
parent | 5e123b844a1cbd4ec258cd37847ce4d57fa308c1 (diff) |
[PATCH] WAN: DSCC4 driver requires generic HDLC
Another thing, reported recently to me by several people - DSCC4 WAN
driver now (and perhaps for the last couple of years+) requires the
generic HDLC. I've fixed the Kconfig and moved the DSCC4 option
under CONFIG_HDLC so it's consistent visually.
Signed-off-by: Krzysztof Halasa <khc@pm.waw.pl>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'drivers/net/wan/Kconfig')
-rw-r--r-- | drivers/net/wan/Kconfig | 76 |
1 files changed, 38 insertions, 38 deletions
diff --git a/drivers/net/wan/Kconfig b/drivers/net/wan/Kconfig index b5d0d7fb647a..d5ab9cf13257 100644 --- a/drivers/net/wan/Kconfig +++ b/drivers/net/wan/Kconfig | |||
@@ -57,44 +57,6 @@ config COSA | |||
57 | The driver will be compiled as a module: the | 57 | The driver will be compiled as a module: the |
58 | module will be called cosa. | 58 | module will be called cosa. |
59 | 59 | ||
60 | config DSCC4 | ||
61 | tristate "Etinc PCISYNC serial board support" | ||
62 | depends on WAN && PCI && m | ||
63 | help | ||
64 | Driver for Etinc PCISYNC boards based on the Infineon (ex. Siemens) | ||
65 | DSCC4 chipset. | ||
66 | |||
67 | This is supposed to work with the four port card. Take a look at | ||
68 | <http://www.cogenit.fr/dscc4/> for further information about the | ||
69 | driver. | ||
70 | |||
71 | To compile this driver as a module, choose M here: the | ||
72 | module will be called dscc4. | ||
73 | |||
74 | config DSCC4_PCISYNC | ||
75 | bool "Etinc PCISYNC features" | ||
76 | depends on DSCC4 | ||
77 | help | ||
78 | Due to Etinc's design choice for its PCISYNC cards, some operations | ||
79 | are only allowed on specific ports of the DSCC4. This option is the | ||
80 | only way for the driver to know that it shouldn't return a success | ||
81 | code for these operations. | ||
82 | |||
83 | Please say Y if your card is an Etinc's PCISYNC. | ||
84 | |||
85 | config DSCC4_PCI_RST | ||
86 | bool "Hard reset support" | ||
87 | depends on DSCC4 | ||
88 | help | ||
89 | Various DSCC4 bugs forbid any reliable software reset of the ASIC. | ||
90 | As a replacement, some vendors provide a way to assert the PCI #RST | ||
91 | pin of DSCC4 through the GPIO port of the card. If you choose Y, | ||
92 | the driver will make use of this feature before module removal | ||
93 | (i.e. rmmod). The feature is known to be available on Commtech's | ||
94 | cards. Contact your manufacturer for details. | ||
95 | |||
96 | Say Y if your card supports this feature. | ||
97 | |||
98 | # | 60 | # |
99 | # Lan Media's board. Currently 1000, 1200, 5200, 5245 | 61 | # Lan Media's board. Currently 1000, 1200, 5200, 5245 |
100 | # | 62 | # |
@@ -323,6 +285,44 @@ config FARSYNC | |||
323 | To compile this driver as a module, choose M here: the | 285 | To compile this driver as a module, choose M here: the |
324 | module will be called farsync. | 286 | module will be called farsync. |
325 | 287 | ||
288 | config DSCC4 | ||
289 | tristate "Etinc PCISYNC serial board support" | ||
290 | depends on HDLC && PCI && m | ||
291 | help | ||
292 | Driver for Etinc PCISYNC boards based on the Infineon (ex. Siemens) | ||
293 | DSCC4 chipset. | ||
294 | |||
295 | This is supposed to work with the four port card. Take a look at | ||
296 | <http://www.cogenit.fr/dscc4/> for further information about the | ||
297 | driver. | ||
298 | |||
299 | To compile this driver as a module, choose M here: the | ||
300 | module will be called dscc4. | ||
301 | |||
302 | config DSCC4_PCISYNC | ||
303 | bool "Etinc PCISYNC features" | ||
304 | depends on DSCC4 | ||
305 | help | ||
306 | Due to Etinc's design choice for its PCISYNC cards, some operations | ||
307 | are only allowed on specific ports of the DSCC4. This option is the | ||
308 | only way for the driver to know that it shouldn't return a success | ||
309 | code for these operations. | ||
310 | |||
311 | Please say Y if your card is an Etinc's PCISYNC. | ||
312 | |||
313 | config DSCC4_PCI_RST | ||
314 | bool "Hard reset support" | ||
315 | depends on DSCC4 | ||
316 | help | ||
317 | Various DSCC4 bugs forbid any reliable software reset of the ASIC. | ||
318 | As a replacement, some vendors provide a way to assert the PCI #RST | ||
319 | pin of DSCC4 through the GPIO port of the card. If you choose Y, | ||
320 | the driver will make use of this feature before module removal | ||
321 | (i.e. rmmod). The feature is known to be available on Commtech's | ||
322 | cards. Contact your manufacturer for details. | ||
323 | |||
324 | Say Y if your card supports this feature. | ||
325 | |||
326 | config DLCI | 326 | config DLCI |
327 | tristate "Frame Relay DLCI support" | 327 | tristate "Frame Relay DLCI support" |
328 | depends on WAN | 328 | depends on WAN |