| /Zephyr-latest/subsys/net/ |
| D | Kconfig | 15 and is the basis for higher level protocols (e.g. IP protocols).
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net-stack-architecture.rst | 42 * **Network Protocols.** This provides implementations for
43 various protocols such as
45 * Application-level network protocols like CoAP, LWM2M, and MQTT.
46 See :ref:`application protocols chapter <net_protocols>` for information
48 * Core network protocols like IPv6, IPv4, UDP, TCP, ICMPv4, and ICMPv6.
49 You access these protocols by using the
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | protocols.rst | 3 Protocols chapter
|
| D | ip_4_6.rst | 13 Miscellaneous defines and helper functions for IP addresses and IP protocols.
|
| D | websocket.rst | 16 network protocols like MQTT.
29 protocols like MQTT. The Zephyr MQTT client library can be configured to use
|
| D | index.rst | 23 protocols.rst
|
| D | ppp.rst | 25 The PPP implementation supports only these protocols:
|
| /Zephyr-latest/doc/services/debugging/ |
| D | mipi_stp_decoder.rst | 7 be shared by multiple application-specific trace protocols. It serves as a wrapper protocol
8 that merges disparate streams that typically contain different trace protocols from different
|
| /Zephyr-latest/doc/connectivity/canbus/ |
| D | index.rst | 3 Controller Area Network (CAN) Bus Protocols
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm-scmi.rst | 35 The SCMI specification defines ten standard protocols:
48 where each of these protocols is identified by an unique protocol ID
51 Apart from the standard protocols, the SCMI specification reserves the
52 **0x80-0xFF** protocol ID range for vendor-specific protocols.
133 Protocols section in ARM System Control and Management Interface
136 Currently, Zephyr has support for the following standard protocols:
|
| /Zephyr-latest/doc/services/sensing/ |
| D | index.rst | 38 protocols, the target is to support various up-layer frameworks and
39 Applications with different sensor expose/transfer protocols,
42 Applications with different up-layer sensor protocols at the same time
61 * Decoupled with any host link protocols, it's Zephyr Application's role to handle different
62 protocols (MQTT, HID or Private, all configurable)
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | dfu.rst | 17 or management protocols themselves required to send the image to the target
18 device. For information on these protocols and frameworks please refer to the
|
| /Zephyr-latest/subsys/net/l2/ppp/ |
| D | link.c | 44 /* Do the other network protocols if encryption is not needed for in do_network()
65 proto->close(ctx, "No network protocols open"); in do_network()
|
| D | ppp_l2.c | 267 /* Bring down network interface by terminating all protocols */
274 /* Terminate protocols and close LCP */ in ppp_down()
279 /* Terminate protocols */ in ppp_down()
505 NET_ERR("There are no PPP protocols configured!"); in net_ppp_init()
|
| D | network.c | 70 NET_WARN("Not all network protocols were closed (%d)", in ppp_network_all_down()
|
| /Zephyr-latest/subsys/net/lib/ptp/ |
| D | transport.h | 9 * @brief Function implementing abstraction over networking protocols.
36 * @brief Types of PTP networking protocols.
|
| /Zephyr-latest/subsys/net/lib/ |
| D | Kconfig | 4 menu "Network Protocols"
|
| /Zephyr-latest/samples/net/lwm2m_client/ |
| D | Kconfig | 39 Only accepted protocols are "coap://" and "coaps://"
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.cellular | 24 with the standard protocols CMUX and PPP, to configure
|
| D | Kconfig | 24 defined protocols. Driver doesn't inspect received data and all
44 using custom defined protocols. Driver doesn't inspect received data
|
| /Zephyr-latest/boards/shields/mikroe_accel13_click/doc/ |
| D | index.rst | 12 The `IIS2DLPC`_ sensor supports both SPI and I2C bus protocols. Currently
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | gnss.rst | 29 Adding support for GNSS modems which use other protocols and/or
|
| /Zephyr-latest/dts/bindings/usb/ |
| D | zephyr,hid-device.yaml | 22 the protocols, keyboard or mouse. For non-boot devices, this property is
|
| /Zephyr-latest/samples/net/lwm2m_client/src/ |
| D | firmware_update.c | 16 /* Array with supported PULL firmware update protocols */
|
| /Zephyr-latest/include/zephyr/net/ |
| D | net_time.h | 44 * @details Timed network protocols (PTP, TDMA, ...) usually require several
101 * is the ideal intermediate building block for timed network protocols.
|
