| Mike Sinkovsky | 9899b81 | 2012-04-04 19:33:53 +0000 | [diff] [blame] | 1 | # |
| 2 | # WIZnet devices configuration |
| 3 | # |
| 4 | |
| 5 | config NET_VENDOR_WIZNET |
| 6 | bool "WIZnet devices" |
| 7 | default y |
| 8 | ---help--- |
| 9 | If you have a network (Ethernet) card belonging to this class, say Y |
| 10 | and read the Ethernet-HOWTO, available from |
| 11 | <http://www.tldp.org/docs.html#howto>. |
| 12 | |
| 13 | Note that the answer to this question doesn't directly affect the |
| 14 | kernel: saying N will just cause the configurator to skip all |
| 15 | the questions about WIZnet devices. If you say Y, you will be asked |
| 16 | for your specific card in the following questions. |
| 17 | |
| 18 | if NET_VENDOR_WIZNET |
| 19 | |
| Mike Sinkovsky | 8b1467a | 2012-04-04 19:33:54 +0000 | [diff] [blame^] | 20 | config WIZNET_W5100 |
| 21 | tristate "WIZnet W5100 Ethernet support" |
| 22 | ---help--- |
| 23 | Support for WIZnet W5100 chips. |
| 24 | |
| 25 | W5100 is a single chip with integrated 10/100 Ethernet MAC, |
| 26 | PHY and hardware TCP/IP stack, but this driver is limited to |
| 27 | the MAC and PHY functions only, onchip TCP/IP is unused. |
| 28 | |
| 29 | To compile this driver as a module, choose M here: the module |
| 30 | will be called w5100. |
| 31 | |
| Mike Sinkovsky | 9899b81 | 2012-04-04 19:33:53 +0000 | [diff] [blame] | 32 | config WIZNET_W5300 |
| 33 | tristate "WIZnet W5300 Ethernet support" |
| 34 | ---help--- |
| 35 | Support for WIZnet W5300 chips. |
| 36 | |
| 37 | W5300 is a single chip with integrated 10/100 Ethernet MAC, |
| 38 | PHY and hardware TCP/IP stack, but this driver is limited to |
| 39 | the MAC and PHY functions only, onchip TCP/IP is unused. |
| 40 | |
| 41 | To compile this driver as a module, choose M here: the module |
| 42 | will be called w5300. |
| 43 | |
| 44 | choice |
| 45 | prompt "WIZnet interface mode" |
| 46 | default WIZNET_BUS_ANY |
| 47 | |
| 48 | config WIZNET_BUS_DIRECT |
| 49 | bool "Direct address bus mode" |
| 50 | ---help--- |
| 51 | In direct address mode host system can directly access all registers |
| 52 | after mapping to Memory-Mapped I/O space. |
| 53 | |
| 54 | config WIZNET_BUS_INDIRECT |
| 55 | bool "Indirect address bus mode" |
| 56 | ---help--- |
| 57 | In indirect address mode host system indirectly accesses registers |
| 58 | using Indirect Mode Address Register and Indirect Mode Data Register, |
| 59 | which are directly mapped to Memory-Mapped I/O space. |
| 60 | |
| 61 | config WIZNET_BUS_ANY |
| 62 | bool "Select interface mode in runtime" |
| 63 | ---help--- |
| 64 | If interface mode is unknown in compile time, it can be selected |
| 65 | in runtime from board/platform resources configuration. |
| 66 | |
| 67 | Performance may decrease compared to explicitly selected bus mode. |
| 68 | endchoice |
| 69 | |
| 70 | config WIZNET_TX_FLOW |
| 71 | bool "Use transmit flow control" |
| 72 | default y |
| 73 | help |
| 74 | This enables transmit flow control for WIZnet chips. |
| 75 | If unsure, say Y. |
| 76 | |
| 77 | endif # NET_VENDOR_WIZNET |