f211cd6345
Deprecate CONFIG_NET_TCP_ACK_TIMEOUT as it is redundant with the combination of CONFIG_NET_TCP_INIT_RETRANSMISSION_TIMEOUT and CONFIG_NET_TCP_RETRY_COUNT. The total retransmission timeout (i. e. waiting for ACK) should depend on the individual retransmission timeout and retry count, having separate config is simply ambiguous and confusing for users. Moreover, the config was currently only used during TCP handshake, and for that purpose we could use the very same timeout that is used for the FIN timeout. Therefore, repurpose the fin_timeout_ms to be a generic, maximum timeout at the TCP stack. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| README.txt | ||
| check_net_options.sh | ||
| prj.conf | ||
| testcase.yaml | ||
README.txt
This test tries to enable all possible networking related config options and build a sample application. The application is not supposed to be run as typically the generated configuration is not usable. The check_net_options.sh script can be used in Linux host to generate a list of missing network related kconfig options from prj.conf file. TODO: * separate conflicting configuration options and create new test cases for them