Kedar Sovani 8f048ffddc Remove check for would_block in mbedtls ... Basically, in the portability layer, it is checked if the socket is NON-block, and if not, then even the EAGAIN and EWOULDBLOCK errors are diverted to a RECV error. This causes a problem for sockets with receive timeouts set. When such a timeout is set, the condition for NON_BLOCK isn't met and hence a hard error is returned. Searching for EAGAIN and EWOULDBLOCK in lwip returns only 3 results (accept, recvfrom, close) and all of them look to be genuine cases for EWOULDBLOCK. So removing this check to make receive timeout with TLS work.		2019-10-18 14:21:35 +05:30
..
mbedtls@f5f2e5926c	NimBLE: Port NimBLE stack to IDF Release v3.3 (Backport v3.3)	2019-10-18 13:23:24 +08:00
port	Remove check for would_block in mbedtls	2019-10-18 14:21:35 +05:30
test	mbedtls: Add UTs for modexp	2019-06-26 14:19:40 +08:00
CMakeLists.txt	mbedtls: fix unix makefile build on windows command line	2018-12-20 18:23:55 +08:00
component.mk	mbedtls: Add mbedtls submodule check to build system	2018-05-14 16:07:18 +08:00
Kconfig	NimBLE: Port NimBLE stack to IDF Release v3.3 (Backport v3.3)	2019-10-18 13:23:24 +08:00
Makefile.projbuild	esp32, mbedtls: check component name when enabling test flags	2018-11-20 01:27:24 +08:00
mbedtls.c	mbedtls: import mbedtls project w/o modification	2018-11-27 13:59:26 +08:00
mklink.py	mbedtls: fix unix makefile build on windows command line	2018-12-20 18:23:55 +08:00