Crash_Override/OVMS3-idf
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
OVMS3-idf/components/esp_netif/Kconfig

41 lines
1.7 KiB
Text
Raw Normal View History

esp_netif: Introduction of esp-netif component as a replacement of tcpip_adpter - provides object oriented access to network intefaces - not limited to default netifs - more generic abstraction to network input output functions - event handler registration removed from component responsibility - backward compatibility layer for legacy tcpip_apapter APIs Closes IDF-39
2019-06-28 14:47:34 +00:00
menu "ESP NETIF Adapter"
tcpip_adapter/lwip: optimize wifi/ip event
2017-07-19 01:15:11 +00:00
esp_netif: Introduction of esp-netif component as a replacement of tcpip_adpter - provides object oriented access to network intefaces - not limited to default netifs - more generic abstraction to network input output functions - event handler registration removed from component responsibility - backward compatibility layer for legacy tcpip_apapter APIs Closes IDF-39
2019-06-28 14:47:34 +00:00
config ESP_NETIF_IP_LOST_TIMER_INTERVAL
Correct Kconfigs according to the coding style
2019-01-25 16:10:53 +00:00
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 everytime 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.
tcpip_adapter/lwip: optimize wifi/ip event
2017-07-19 01:15:11 +00:00
esp_netif: Introduction of esp-netif component as a replacement of tcpip_adpter - provides object oriented access to network intefaces - not limited to default netifs - more generic abstraction to network input output functions - event handler registration removed from component responsibility - backward compatibility layer for legacy tcpip_apapter APIs Closes IDF-39
2019-06-28 14:47:34 +00:00
choice ESP_NETIF_USE_TCPIP_STACK_LIB
Correct Kconfigs according to the coding style
2019-01-25 16:10:53 +00:00
prompt "TCP/IP Stack Library"
esp_netif: update default DHCP IP addresses to be in line with old interface, added loopback implementation, explicit esp-netif init, sanity checks for parameters added
2019-09-02 09:22:09 +00:00
default ESP_NETIF_TCPIP_LWIP
emac:optimise tcpip_adapter and fix emac_dev.c 1. move CONFIG_xx macros to Kconfig 2. fix a bug that make EMAC_DMAOPERATION_MODE_ERG mess
2018-08-15 08:33:32 +00:00
help
Correct Kconfigs according to the coding style
2019-01-25 16:10:53 +00:00
Choose the TCP/IP Stack to work, for example, LwIP, uIP, etc.
esp_netif: update default DHCP IP addresses to be in line with old interface, added loopback implementation, explicit esp-netif init, sanity checks for parameters added
2019-09-02 09:22:09 +00:00
config ESP_NETIF_TCPIP_LWIP
Correct Kconfigs according to the coding style
2019-01-25 16:10:53 +00:00
bool "LwIP"
help
lwIP is a small independent implementation of the TCP/IP protocol suite.
esp_netif: update default DHCP IP addresses to be in line with old interface, added loopback implementation, explicit esp-netif init, sanity checks for parameters added
2019-09-02 09:22:09 +00:00
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
Correct Kconfigs according to the coding style
2019-01-25 16:10:53 +00:00
endchoice
emac:optimise tcpip_adapter and fix emac_dev.c 1. move CONFIG_xx macros to Kconfig 2. fix a bug that make EMAC_DMAOPERATION_MODE_ERG mess
2018-08-15 08:33:32 +00:00
esp_netif: update default DHCP IP addresses to be in line with old interface, added loopback implementation, explicit esp-netif init, sanity checks for parameters added
2019-09-02 09:22:09 +00:00
config ESP_NETIF_TCPIP_ADAPTER_COMPATIBLE_LAYER
esp_netif: Introduction of esp-netif component as a replacement of tcpip_adpter - provides object oriented access to network intefaces - not limited to default netifs - more generic abstraction to network input output functions - event handler registration removed from component responsibility - backward compatibility layer for legacy tcpip_apapter APIs Closes IDF-39
2019-06-28 14:47:34 +00:00
bool "Enable backward compatible tcpip_adapter interface"
default y
help
Backward compatible interface to tcpip_adapter is enabled by default to support
esp_netif: update default DHCP IP addresses to be in line with old interface, added loopback implementation, explicit esp-netif init, sanity checks for parameters added
2019-09-02 09:22:09 +00:00
legacy TCP/IP stack initialisation code. Disable this option to use only esp-netif
esp_netif: Introduction of esp-netif component as a replacement of tcpip_adpter - provides object oriented access to network intefaces - not limited to default netifs - more generic abstraction to network input output functions - event handler registration removed from component responsibility - backward compatibility layer for legacy tcpip_apapter APIs Closes IDF-39
2019-06-28 14:47:34 +00:00
interface.
tcpip_adapter/lwip: optimize wifi/ip event
2017-07-19 01:15:11 +00:00
endmenu
Reference in a new issue Copy permalink