Due to performance reasons _esp_wifi_recv_cb and _send have to be executed in IRAM.

To avoid conflicts on receiption of a frame while sending, _esp_wifi_recv_cb should not executed while a frame is in transmission

Overriding ethernet_input function _esp_wifi_recv_cb is only used when the WiFi interface is in connected state.

wifi_station_connect and wifi_stattion_disconnect never produce errors. Thus, error handling can be removed.

Different connection states defined to be able to realize a better connect/reconnect handling

Some SDK interrupt service routines obviously use malloc/free in the interrupt context. Because the rmutex-based lock/unlock approach of the malloc/free function suite of the newlib does not work in the interrupt context, the SDK memory management functions MUST therefore be used. To use the same memory management functions in RIOT as in the SDK, the malloc/free function suite has to be replaced by wrapper functions.

Since complete MAC frames are handled, ETHERNET_MAX_LEN has to be used instead of ETHERNET_DATA_LEN for receive buffer size and length check.

Fixes sporadic blocking of the wifi thread in esp_wifi_recv_cb function under heavy network load conditions when frames are coming in faster than they can be processed. Since esp_wifi_recv_cb function is not executed in interrupt context, the msg_send function used for ISR event can block when the message queue is full. With this change esp_wifi can be flooded with icmpv6 packets of maximum size without any problems over hours.

Add SAML10/SAML11 support through SAM0 because hardware IP are the same so reuse to avoid duplication

During flash write access, the IROM cache cannot be used and is disabled therefore. During that time, ets_post crashes if a functions is called which is not in IRAM. Therefore thread_flags_set must not be called if IROM cache is disabled.

With the new ETS task handling thread, the stack sizes could be down sized.

Changes of ETS task handling require the context switch by software interrupt. The context switch based on interrupt is therefore enabled by default. Furthermore, the number of priority levels are increased due to the new additional thread.

ETS tasks are now handled by a high priority RIOT thread

Since complete MAC frames are handled, ETHERNET_MAX_LEN has to be used instead of ETHERNET_DATA_LEN for buffer sizes and length checks.

Since complete MAC frames are handled, ETHERNET_MAX_LEN has to be used instead of ETHERNET_DATA_LEN for buffer sizes and length checks.

The type [is documented as `gnrc_nettype_t`][1] so it should by checked
as such.

[1]: https://github.com/RIOT-OS/RIOT/blob/f9a3bdf1a749f0e6a0d9e79eee652d8b31d4d9e0/sys/include/net/netopt.h#L210-L212

ESP-IDF heap handling has to be used for esp_wifi for stability reasons. Otherwise, heap is corrupted sporadically

Fixes sporadic blocking of the wifi thread in esp_wifi_recv_cb function under heavy network load conditions when frames are coming in faster than they can be processed. Since esp_wifi_recv_cb function is not executed in interrupt context, the msg_send function used for ISR event can block when the message queue is full. With this change esp_wifi can be flooded with icmpv6 packets of maximum size without any problems over hours.

To avoid further inconsistencies in documentation, README.md is not provided any longer