Lines Matching refs:will
41 into a :c:struct:`net_pkt`, will push this buffer to the network
47 function will return ``NET_DROP`` in case of an erroneous packet,
51 - ``send()``: Similar to receive function, the network stack will call this
53 will be generated and added by this function.
60 - ``get_flags()``: This function will return the capabilities of an L2 driver,
76 macros will call the :c:macro:`DEVICE_DEFINE()` macro, and also
83 In the next section, we will describe how a device driver should behave when
93 :c:func:`net_pkt_rx_alloc_with_buffer`. Then all data buffers will be
97 call :c:func:`net_recv_data`. If that call fails, it will be up to the
100 On sending, the device driver send function will be called, and it is up to
103 Each Ethernet device driver will need, in the end, to call
127 header, payload and frame checksum. Buffers to be sent over the radio will
129 packet will often have to be split into several fragments and IP6 packet headers
149 management calls will call into the driver, e.g. to send a packet over the
150 radio link or re-configure the driver at runtime. These incoming calls will
166 :zephyr_file:`include/zephyr/net/ieee802154_radio.h`. The API documentation will
175 As all net interfaces, IEEE 802.15.4 device driver implementations will have to call