| /Zephyr-latest/subsys/net/l2/ethernet/ |
| D | Kconfig | 59 VLAN virtual interface is not created in this case.
134 How many bridge interfaces are created. Each interface can bridge
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | mqtt.rst | 46 Multiple MQTT client instances can be created in the application and managed
57 callback function created to handle respective events:
|
| D | net_if.rst | 16 created at runtime. A special linker section will contain information about them
19 Network interfaces are created by ``NET_DEVICE_INIT()`` macro.
|
| D | vlan.rst | 21 created for each VLAN, and this virtual network interface connects to the
|
| D | mqtt_sn.rst | 16 over any message-based transport. Originally, it was mainly created with ZigBee in mind,
48 Multiple MQTT-SN client instances can be created in the application and managed
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 52 On the host PC, a virtual SocketCAN interface needs to be created and brought up before running the
70 Once the virtual SocketCAN interface has been created, brought up, and configured the test suite can
|
| /Zephyr-latest/samples/boards/renesas/openamp_linux_zephyr/ |
| D | README.rst | 136 [CM33] RPMSG endpoint has created. rp_ept:0xffff9c86f870
139 [CM33] RPMSG service has created.
|
| /Zephyr-latest/doc/services/ |
| D | formatted_output.rst | 77 Package can be created using two methods:
83 and package is created as simple assignments to a provided memory. This method
109 flag was used when package was created.
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 13 to be created. After the process is implemented and all supporting
14 documents are created, this document is a top-level overview and entry
32 relevant sub-modules is created, threats are identified, and
245 created and kept up-to-date with future development.
262 be created and kept up to date with future development. This document
265 document shall be created and evaluated against the implementation.
453 issues. Furthermore, threat models need to be created for currently
547 model is created. This model contains the asset and system
570 Additionally, new models shall be created, or existing ones shall be
605 hardware platform), a suitable VA plan shall be created and executed.
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_eth_setup.rst | 56 should be created in the host system.
|
| /Zephyr-latest/arch/common/ |
| D | CMakeLists.txt | 93 # note that the pattern will affect empty spaces created after FILL(0x00).
|
| /Zephyr-latest/samples/subsys/edac/ |
| D | README.rst | 26 The Zephyr image that's created can be run on the :ref:`intel_ehl_crb` board
|
| /Zephyr-latest/subsys/net/lib/lwm2m/ |
| D | lwm2m_rw_cbor.c | 532 uint8_t created = 0U; in do_write_op_cbor() local
534 ret = lwm2m_get_or_create_engine_obj(msg, &obj_inst, &created); in do_write_op_cbor()
|
| D | lwm2m_rw_json.c | 916 uint8_t created; in do_write_op_json() local
984 created = 0U; in do_write_op_json()
994 ret = lwm2m_get_or_create_engine_obj(msg, &obj_inst, &created); in do_write_op_json()
|
| D | lwm2m_registry.c | 1375 struct lwm2m_engine_obj_inst **obj_inst, uint8_t *created) in lwm2m_get_or_create_engine_obj() argument
1379 if (created) { in lwm2m_get_or_create_engine_obj()
1380 *created = 0U; in lwm2m_get_or_create_engine_obj()
1391 if (created) { in lwm2m_get_or_create_engine_obj()
1392 *created = 1U; in lwm2m_get_or_create_engine_obj()
|
| /Zephyr-latest/tests/subsys/ipc/ipc_sessions/interoperability/ |
| D | Kconfig.icmsg_v1 | 57 created to prevent notifying service users about received data
|
| /Zephyr-latest/samples/bluetooth/direction_finding_central/ |
| D | README.rst | 51 …as those in the created file :file:`samples/bluetooth/hci_ipc/boards/nrf5340dk_nrf5340_cpunet.ove…
|
| /Zephyr-latest/samples/bluetooth/direction_finding_peripheral/ |
| D | README.rst | 50 …as those in the created file :file:`samples/bluetooth/hci_ipc/boards/nrf5340dk_nrf5340_cpunet.over…
|
| /Zephyr-latest/samples/net/openthread/coap/ |
| D | README.rst | 13 By running a client and server on two boards, a local Thread network can be created.
16 automatically created and configured.
|
| /Zephyr-latest/subsys/net/lib/sockets/ |
| D | Kconfig | 138 Call mbedtls_ssl_conf_max_frag_len() on created TLS context
278 int "Maximum number of dispatcher sockets created"
282 Maximum number of dispatcher sockets created at a time. Note, that
284 After a proper socket has been created for a given file descriptor,
|
| /Zephyr-latest/samples/bluetooth/direction_finding_connectionless_rx/ |
| D | README.rst | 51 …as those in the created file :file:`samples/bluetooth/hci_ipc/boards/nrf5340dk_nrf5340_cpunet.over…
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wroom/doc/ |
| D | index.rst | 9 variations. ESP32 is created and developed by Espressif Systems, a
124 Build directory structure created by sysbuild is different from traditional
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wrover/doc/ |
| D | index.rst | 9 variations. ESP32 is created and developed by Espressif Systems, a
124 Build directory structure created by sysbuild is different from traditional
|
| /Zephyr-latest/doc/services/logging/ |
| D | index.rst | 81 API is called a message is created and added to the list. Dedicated,
136 :kconfig:option:`CONFIG_LOG_PROCESS_THREAD`: When enabled, logging thread is created
279 are not created.
473 given source of logging. Aggregate slot determines if log message is created
498 created and no backend is handled. Otherwise, custom frontend can coexist with
535 created from the backend on one side and linked to the other.
595 Let's consider a log message created on the *B_S* domain:
703 instead of the whole strings. A dictionary created at build time contains
739 a JSON database file, named :file:`log_dictionary.json`, will be created
|
| /Zephyr-latest/share/sysbuild/cmake/modules/ |
| D | sysbuild_kconfig.cmake | 76 # Not adding it to CMake cache ensures that a later created sysbuild.conf
|
