Home
last modified time | relevance | path

Searched full:layer (Results 1 – 25 of 265) sorted by relevance

1234567891011

/Zephyr-Core-2.7.6/subsys/net/l2/canbus/
DKconfig5 bool "Enable CANBUS L2 layer [EXPERIMENTAL]"
9 Add a CANBUS L2 layer driver. This is the layer for IPv6 over CAN
30 Greater than one only makes sense for random link layer addresses.
67 module-str = Log level for CANbus L2 layer
74 bool "Enable CANBUS RAW l2 layer"
76 Add a CANBUS L2 layer driver. This is the layer for SOCKET CAN.
/Zephyr-Core-2.7.6/subsys/net/l2/virtual/
DKconfig7 Add a virtual L2 layer driver. This is needed if you have a L2
8 layer that depends on other L2 layer. Like running VPN on top of
22 int "Max length of the virtual L2 layer name"
31 module-str = Log level for virtual L2 layer
/Zephyr-Core-2.7.6/doc/reference/networking/
Dnet_linkaddr.rst3 Link Layer Address Handling
13 The link layer addresses are set for network interfaces so that L2
14 connectivity works correctly in the network stack. Typically the link layer
16 layer address length is 8 bytes.
Dnet_mgmt.rst14 layer code itself, to call defined network routines at any level in
36 mask that tells which stack layer is targeted, if a ``net_if`` object is
51 pair of layer and code, whereas on the command part it will be a mask of
69 layer and layer code. A callback handler function **must** check
75 multiple listeners registered, one for each layer being listened.
76 The callback handler function can be shared between different layer events.
78 (False positives can occur for events which have the same layer and
79 layer code.)
134 the targeted layer or eventually, if l2 is the layer, on the
135 technology as well. For instance, all IP layer management request code
Dnet_l2.rst3 L2 Layer Management
13 The L2 stack is designed to hide the whole networking link-layer part
19 object and the generic API provided by the L2 layer in
22 Only the L2 layer can talk to the device driver, linked to the net_if
23 object. The L2 layer dictates the API provided by the device driver,
29 :ref:`OpenThread <thread_protocol_interface>`, Wi-Fi, and a dummy layer
32 L2 layer API
35 In order to create an L2 layer, or a driver for a specific L2 layer,
36 one needs to understand how the L3 layer interacts with it and
37 how the L2 layer is supposed to behave.
[all …]
Dlldp.rst3 Link Layer Discovery Protocol
13 The Link Layer Discovery Protocol (LLDP) is a vendor-neutral link layer
Dppp.rst15 layer (layer 2) communications protocol used to establish a direct connection
/Zephyr-Core-2.7.6/subsys/net/l2/
DKconfig4 menu "Link layer options"
7 bool "Enable dummy l2 layer"
10 Add a dummy L2 layer driver. This is usually only needed when
50 module-str = Log level for Bluetooth L2 layer
92 module-str = Log level for Wi-Fi management layer
/Zephyr-Core-2.7.6/drivers/wifi/esp32/
DKconfig.esp3265 and then delivers it to the high layer TCP/IP stack. The dynamic RX buffer
66 is freed after the higher layer has successfully received the data frame.
87 frame sent by the TCP/IP layer.
114 For each transmitted data frame from the higher layer TCP/IP stack,
116 especially UDP applications, the upper layer can deliver frames faster
117 than WiFi layer can transmit.
143 For each transmitted frame from the higher layer TCP/IP stack,
145 especially UDP applications, the upper layer can deliver frames faster
146 than WiFi layer can transmit. In these cases, we may run out of TX
/Zephyr-Core-2.7.6/subsys/net/ip/
Dnbr.h25 /* The neighbors are tracked by link layer address. This is not part
30 /** Link layer address */
166 * @param lladdr Neighbor link layer address
174 * @brief Link a neighbor to specific link layer address.
177 * @param lladdr Neighbor link layer address
184 * @brief Unlink a neighbor from specific link layer address.
186 * @param lladdr Neighbor link layer address
193 * @param idx Link layer address index in ll table.
194 * @return Pointer to link layer address storage, NULL if not found
Dpacket_socket.c37 /* Currently we are skipping L2 layer verification and not in net_packet_socket_input()
40 * 1) Pass it through L2 layer, so that L2 will verify in net_packet_socket_input()
/Zephyr-Core-2.7.6/include/net/
Dnet_linkaddr.h84 * when we have to store the link layer address.
102 * @brief Compare two link layer addresses.
104 * @param lladdr1 Pointer to a link layer address
105 * @param lladdr2 Pointer to a link layer address
125 * @brief Set the member data of a link layer address storage structure.
Dnet_l2.h24 * @brief Network Layer 2 abstraction layer
25 * @defgroup net_l2 Network L2 Abstraction Layer
56 * This function is used by net core to get iface's L2 layer parsing
62 * This function is used by net core to push a packet to lower layer
Dnet_stats.h59 * @brief IP layer statistics
62 /** Number of received packets at the IP layer. */
65 /** Number of sent packets at the IP layer. */
68 /** Number of forwarded packets at the IP layer. */
71 /** Number of dropped packets at the IP layer. */
76 * @brief IP layer error statistics
132 /** Number of dropped packets at the TCP layer. */
302 /** IP layer errors */
Dcan.h126 /** Filter ID for link layer duplicate address detection. */
128 /** Work item for responding to link layer DAD requests. */
132 /** The link layer address chosen for this interface */
145 * Canbus link layer addresses have a length of 14 bit for source and destination.
228 * This function checks the destination link layer address for addresses
/Zephyr-Core-2.7.6/drivers/modem/
DKconfig70 To configure this layer for use, create a modem_iface_uart_data
85 To configure this layer for use, create a modem_cmd_handler_data
100 bool "Generic modem socket support layer"
102 This layer provides much of the groundwork for keeping track of
105 To configure this layer for use, create a modem_socket_config
/Zephyr-Core-2.7.6/modules/
DKconfig.syst13 bool "STP Transport Layer for MIPI SyS-T"
16 Transport Layer for MIPI SyS-T
/Zephyr-Core-2.7.6/modules/hal_nordic/nrf_802154/sl_opensource/platform/
Dnrf_802154_irq_zephyr.c29 /* Zephyr does not provide abstraction layer for setting pending IRQ */ in nrf_802154_irq_set_pending()
35 /* Zephyr does not provide abstraction layer for clearing pending IRQ */ in nrf_802154_irq_clear_pending()
/Zephyr-Core-2.7.6/drivers/crypto/
DKconfig33 Enable TinyCrypt shim layer compliant with crypto APIs.
55 Enable mbedTLS shim layer compliant with crypto APIs. You will need
/Zephyr-Core-2.7.6/subsys/bluetooth/mesh/
DKconfig20 # Virtual option enabled whenever Generic Provisioning layer is needed
172 bool "Enable direct Bluetooth message access layer messages"
175 Bluetooth access layer messages without the need to
391 which 4 or 8 bytes is used for the Transport Layer MIC). For
393 which leaves 56 bytes for application layer data using a
410 which 4 or 8 bytes is used for the Transport Layer MIC). For
412 which leaves 56 bytes for application layer data using a
716 layer to know about mesh model relationships.
785 bool "Network layer debug"
787 Use this option to enable Network layer debug logs for the
[all …]
Daccess.h59 * Register a callback function to act as a hook for recieving mesh model layer messages
69 * Send a mesh model layer message out into the mesh network without having instantiated
/Zephyr-Core-2.7.6/doc/guides/debug_tools/tracing/
Dindex.rst31 interface between payload/format (Top Layer) and the transport mechanics
32 (bottom Layer) is generic and efficient enough to model these. See the
62 As seen from *I/O taxonomy* section below, a bottom layer may:
70 CTF Top-Layer Example
88 internally and statically at compile-time in the bottom-layer.
91 The CTF top layer is enabled using the configuration option
237 Currently, the top-layer provided here is quite simple and bare-bones,
241 Linux's LTTng and change the top-layer to serialize to the same format.
328 E.g. Multi-UART. Lock-free if the bottom-layer maps each Zephyr
/Zephyr-Core-2.7.6/subsys/bluetooth/common/
Ddummy.c40 * with the software-based Link Layer since it introduces ISR latency
48 "supported with the software Link Layer");
/Zephyr-Core-2.7.6/subsys/net/lib/config/
DKconfig68 some link-layer dedicated settings like the channel.
151 The key string to use for the link-layer security part.
159 The key mode to use for the link-layer security part.
168 The security level to use for the link-layer security part.
/Zephyr-Core-2.7.6/subsys/net/
DKconfig69 bool "Link layer and IP networking support"
74 This option enabled generic link layer and IP networking support.

1234567891011