kopia lustrzana https://github.com/espressif/esp-idf
88 wiersze
3.7 KiB
Plaintext
88 wiersze
3.7 KiB
Plaintext
menu "ESP NETIF Adapter"
|
|
|
|
config ESP_NETIF_IP_LOST_TIMER_INTERVAL
|
|
int "IP Address lost timer interval (seconds)"
|
|
range 0 65535
|
|
default 120
|
|
help
|
|
The value of 0 indicates the IP lost timer is disabled, otherwise the timer is enabled.
|
|
|
|
The IP address may be lost because of some reasons, e.g. when the station disconnects
|
|
from soft-AP, or when DHCP IP renew fails etc. If the IP lost timer is enabled, it will
|
|
be started every time the IP is lost. Event SYSTEM_EVENT_STA_LOST_IP will be raised if
|
|
the timer expires. The IP lost timer is stopped if the station get the IP again before
|
|
the timer expires.
|
|
|
|
choice ESP_NETIF_USE_TCPIP_STACK_LIB
|
|
prompt "TCP/IP Stack Library"
|
|
default ESP_NETIF_TCPIP_LWIP
|
|
help
|
|
Choose the TCP/IP Stack to work, for example, LwIP, uIP, etc.
|
|
config ESP_NETIF_TCPIP_LWIP
|
|
bool "LwIP"
|
|
select ESP_NETIF_USES_TCPIP_WITH_BSD_API
|
|
depends on LWIP_ENABLE
|
|
help
|
|
lwIP is a small independent implementation of the TCP/IP protocol suite.
|
|
|
|
config ESP_NETIF_LOOPBACK
|
|
bool "Loopback"
|
|
help
|
|
Dummy implementation of esp-netif functionality which connects driver transmit
|
|
to receive function. This option is for testing purpose only
|
|
|
|
endchoice
|
|
|
|
config ESP_NETIF_USES_TCPIP_WITH_BSD_API
|
|
bool # Set to true if the chosen TCP/IP stack provides BSD socket API
|
|
|
|
config ESP_NETIF_REPORT_DATA_TRAFFIC
|
|
bool "Report data traffic via events"
|
|
default y
|
|
help
|
|
Enable if esp_netif_transmit() and esp_netif_receive() should generate events. This can be useful
|
|
to blink data traffic indication lights.
|
|
|
|
config ESP_NETIF_RECEIVE_REPORT_ERRORS
|
|
bool "Use esp_err_t to report errors from esp_netif_receive"
|
|
default n
|
|
help
|
|
Enable if esp_netif_receive() should return error code. This is useful to inform upper layers
|
|
that packet input to TCP/IP stack failed, so the upper layers could implement flow control.
|
|
This option is disabled by default due to backward compatibility and will be enabled in v6.0 (IDF-7194)
|
|
|
|
config ESP_NETIF_L2_TAP
|
|
bool "Enable netif L2 TAP support"
|
|
select ETH_TRANSMIT_MUTEX
|
|
help
|
|
A user program can read/write link layer (L2) frames from/to ESP TAP device.
|
|
The ESP TAP device can be currently associated only with Ethernet physical interfaces.
|
|
|
|
config ESP_NETIF_L2_TAP_MAX_FDS
|
|
depends on ESP_NETIF_L2_TAP
|
|
int "Maximum number of opened L2 TAP File descriptors"
|
|
range 1 10
|
|
default 5
|
|
help
|
|
Maximum number of opened File descriptors (FD's) associated with ESP TAP device. ESP TAP FD's take up
|
|
a certain amount of memory, and allowing fewer FD's to be opened at the same time conserves memory.
|
|
|
|
config ESP_NETIF_L2_TAP_RX_QUEUE_SIZE
|
|
depends on ESP_NETIF_L2_TAP
|
|
int "Size of L2 TAP Rx queue"
|
|
range 1 100
|
|
default 20
|
|
help
|
|
Maximum number of frames queued in opened File descriptor. Once the queue is full, the newly arriving
|
|
frames are dropped until the queue has enough room to accept incoming traffic (Tail Drop queue
|
|
management).
|
|
|
|
config ESP_NETIF_BRIDGE_EN
|
|
depends on ESP_NETIF_TCPIP_LWIP
|
|
bool "Enable LwIP IEEE 802.1D bridge"
|
|
default n
|
|
help
|
|
Enable LwIP IEEE 802.1D bridge support in ESP-NETIF. Note that "Number of clients store data in netif"
|
|
(LWIP_NUM_NETIF_CLIENT_DATA) option needs to be properly configured to be LwIP bridge available!
|
|
endmenu
|