Kedar Sovani 87c3decc12 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-17 16:36:18 +05:30
..
mbedtls@f5f2e5926c	NimBLE: Add optional mbedTLS support to NimBLE	2019-09-30 14:15:43 +08:00
port	Remove check for would_block in mbedtls	2019-10-17 16:36:18 +05:30
test	tools: Mass fixing of empty prototypes (for -Wstrict-prototypes)	2019-08-01 16:28:56 +07:00
CMakeLists.txt	mbedtls: add source files to appropriate library	2019-08-15 12:43:45 +08:00
component.mk	move hwcrypto from esp32 to mbedtls	2019-03-26 16:24:22 +08:00
Kconfig	NimBLE: Add optional mbedTLS support to NimBLE	2019-09-30 14:15:43 +08:00
Makefile.projbuild	esp32, mbedtls: check component name when enabling test flags	2018-11-20 01:27:24 +08:00