Skip to content
Snippets Groups Projects
Commit 5a835e91 authored by Gunar Schorcht's avatar Gunar Schorcht Committed by Schorcht
Browse files

cpu/esp8266: fix some comments in esp_wifi

parent 107e196b
No related branches found
No related tags found
No related merge requests found
...@@ -92,7 +92,7 @@ extern struct netif * eagle_lwip_getif(uint8 index); ...@@ -92,7 +92,7 @@ extern struct netif * eagle_lwip_getif(uint8 index);
static bool _in_esp_wifi_recv_cb = false; static bool _in_esp_wifi_recv_cb = false;
/** /**
* @brief Callback when UDP packet is received * @brief Callback when ethernet frame is received. Has to run in IRAM.
*/ */
void _esp_wifi_recv_cb(struct pbuf *pb, struct netif *netif) void _esp_wifi_recv_cb(struct pbuf *pb, struct netif *netif)
{ {
...@@ -100,10 +100,10 @@ void _esp_wifi_recv_cb(struct pbuf *pb, struct netif *netif) ...@@ -100,10 +100,10 @@ void _esp_wifi_recv_cb(struct pbuf *pb, struct netif *netif)
assert(netif != NULL); assert(netif != NULL);
/* /*
* The function `esp_wifi_recv_cb` is executed in the context of the `wifi` * The function `esp_wifi_recv_cb` is executed in the context of the `ets`
* thread. The ISRs handling the hardware interrupts from the WiFi * thread. The ISRs handling the hardware interrupts from the WiFi
* interface pass events to a message queue of the `wifi` thread which is * interface pass events to a message queue of the `ets` thread which is
* sequentially processed by the `wifi` thread to asynchronously execute * sequentially processed by the `ets` thread to asynchronously execute
* callback functions such as `esp_wifi_recv_cb`. * callback functions such as `esp_wifi_recv_cb`.
* *
* It should be therefore not possible to reenter function * It should be therefore not possible to reenter function
...@@ -123,7 +123,7 @@ void _esp_wifi_recv_cb(struct pbuf *pb, struct netif *netif) ...@@ -123,7 +123,7 @@ void _esp_wifi_recv_cb(struct pbuf *pb, struct netif *netif)
critical_enter(); critical_enter();
/* check the first packet buffer for the minimum packet size */ /* first, check packet buffer for the minimum packet size */
if (pb->len < sizeof(ethernet_hdr_t)) { if (pb->len < sizeof(ethernet_hdr_t)) {
ESP_WIFI_DEBUG("frame length is less than the size of an Ethernet" ESP_WIFI_DEBUG("frame length is less than the size of an Ethernet"
"header (%u < %u)", pb->len, sizeof(ethernet_hdr_t)); "header (%u < %u)", pb->len, sizeof(ethernet_hdr_t));
...@@ -311,7 +311,7 @@ static int _send(netdev_t *netdev, const iolist_t *iolist) ...@@ -311,7 +311,7 @@ static int _send(netdev_t *netdev, const iolist_t *iolist)
ESP_WIFI_DEBUG("could not allocate buffer to send %d bytes ", iol_len); ESP_WIFI_DEBUG("could not allocate buffer to send %d bytes ", iol_len);
/* /*
* The memory of EPS8266 is quite small. Therefore, it may happen on * The memory of EPS8266 is quite small. Therefore, it may happen on
* haevy network load that we run into out of memory and we have * heavy network load that we run into out of memory and we have
* to wait until lwIP pbuf has been flushed. For that purpose, we * to wait until lwIP pbuf has been flushed. For that purpose, we
* have to disconnect from AP and slow down sending. The node will * have to disconnect from AP and slow down sending. The node will
* then reconnect to AP automatically. * then reconnect to AP automatically.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment