Lines Matching refs:to
44 * `........` Initialization line from user code to esp-netif and comm driver
46 * `--<--->--` Data packets going from communication media to TCP/IP stack and back
48 * `********` Events agregated in ESP-NETIP propagates to driver, user code and network stack
72 * glue IO layer: adapt the input/output functions to use esp-netif transmit/input/free_rx
73 - install driver_transmit to appropriate ESP-NETIF object, so that outgoing packets from
74 network stack are passed to the IO driver
75 - calls esp_netif_receive to pass incoming data to network stack
92 The ESP-NETIF L2 TAP interface is ESP-IDF mechanism utilized to access Data Link Layer (L2 per OSI/…
101 …ce the ESP-NETIF L2 TAP interface can be understood as generic entry point to the NETIF internal s…
102 …configuration of particular file descriptor. It can be configured to give an access to specific Ne…
103 identified by ``if_key`` (e.g. `ETH_DEF`) and to filter only specific frames based on their type (e…
104 Filtering only specific frames is crucial since the ESP-NETIF L2 TAP needs to work along with IP st…
105 (IP, ARP, etc.) should not be passed directly to the user application. Even though such option is s…
106 …so advantageous from a perspective the user’s application gets access only to frame types it is in…
107 in and the remaining traffic is either passed to other L2 TAP file descriptors or to IP stack.