]>
Commit | Line | Data |
---|---|---|
9899b81e MS |
1 | # |
2 | # WIZnet devices configuration | |
3 | # | |
4 | ||
5 | config NET_VENDOR_WIZNET | |
6 | bool "WIZnet devices" | |
9fafbd4d | 7 | depends on HAS_IOMEM |
9899b81e MS |
8 | default y |
9 | ---help--- | |
138b15ed | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
9899b81e MS |
11 | |
12 | Note that the answer to this question doesn't directly affect the | |
13 | kernel: saying N will just cause the configurator to skip all | |
14 | the questions about WIZnet devices. If you say Y, you will be asked | |
15 | for your specific card in the following questions. | |
16 | ||
17 | if NET_VENDOR_WIZNET | |
18 | ||
8b1467a3 MS |
19 | config WIZNET_W5100 |
20 | tristate "WIZnet W5100 Ethernet support" | |
32ed53b8 | 21 | depends on HAS_IOMEM |
8b1467a3 MS |
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 | ||
9899b81e MS |
32 | config WIZNET_W5300 |
33 | tristate "WIZnet W5300 Ethernet support" | |
32ed53b8 | 34 | depends on HAS_IOMEM |
9899b81e MS |
35 | ---help--- |
36 | Support for WIZnet W5300 chips. | |
37 | ||
38 | W5300 is a single chip with integrated 10/100 Ethernet MAC, | |
39 | PHY and hardware TCP/IP stack, but this driver is limited to | |
40 | the MAC and PHY functions only, onchip TCP/IP is unused. | |
41 | ||
42 | To compile this driver as a module, choose M here: the module | |
43 | will be called w5300. | |
44 | ||
45 | choice | |
46 | prompt "WIZnet interface mode" | |
32ed53b8 | 47 | depends on WIZNET_W5100 || WIZNET_W5300 |
9899b81e MS |
48 | default WIZNET_BUS_ANY |
49 | ||
50 | config WIZNET_BUS_DIRECT | |
51 | bool "Direct address bus mode" | |
52 | ---help--- | |
53 | In direct address mode host system can directly access all registers | |
54 | after mapping to Memory-Mapped I/O space. | |
55 | ||
56 | config WIZNET_BUS_INDIRECT | |
57 | bool "Indirect address bus mode" | |
58 | ---help--- | |
59 | In indirect address mode host system indirectly accesses registers | |
60 | using Indirect Mode Address Register and Indirect Mode Data Register, | |
61 | which are directly mapped to Memory-Mapped I/O space. | |
62 | ||
63 | config WIZNET_BUS_ANY | |
64 | bool "Select interface mode in runtime" | |
65 | ---help--- | |
66 | If interface mode is unknown in compile time, it can be selected | |
67 | in runtime from board/platform resources configuration. | |
68 | ||
69 | Performance may decrease compared to explicitly selected bus mode. | |
70 | endchoice | |
71 | ||
630cf097 | 72 | config WIZNET_W5100_SPI |
35ef7d68 | 73 | tristate "WIZnet W5100/W5200/W5500 Ethernet support for SPI mode" |
b67d1df5 | 74 | depends on WIZNET_BUS_ANY && WIZNET_W5100 |
630cf097 AM |
75 | depends on SPI |
76 | ---help--- | |
77 | In SPI mode host system accesses registers using SPI protocol | |
78 | (mode 0) on the SPI bus. | |
79 | ||
80 | Performance decreases compared to other bus interface mode. | |
81 | In W5100 SPI mode, burst READ/WRITE processing are not provided. | |
82 | ||
83 | To compile this driver as a module, choose M here: the module | |
84 | will be called w5100-spi. | |
85 | ||
9899b81e | 86 | endif # NET_VENDOR_WIZNET |