Home
last modified time | relevance | path

Searched refs:structured (Results 1 – 20 of 20) sorted by relevance

/Zephyr-4.2.1/samples/modules/nanopb/
DREADME.rst4 Serialize and deserialize structured data using the nanopb module.
9 A simple protocol buffer sample using :ref:`nanopb_reference` for serializing structured data
12 The structured data to encode/decode is presented as follows:
/Zephyr-4.2.1/subsys/shell/
Dshell_help.c119 const struct shell_cmd_help *structured = (const struct shell_cmd_help *)item_help; in formatted_structured_help_print() local
121 if (structured->description) { in formatted_structured_help_print()
122 formatted_text_print(sh, structured->description, terminal_offset, false); in formatted_structured_help_print()
125 if (structured->usage) { in formatted_structured_help_print()
128 formatted_text_print(sh, structured->usage, terminal_offset + 7, false); in formatted_structured_help_print()
/Zephyr-4.2.1/doc/services/serialization/
Dindex.rst7 structured data with a known format on-the-wire.
/Zephyr-4.2.1/include/zephyr/shell/
Dshell.h329 const struct shell_cmd_help *structured = (const struct shell_cmd_help *)help; in shell_help_is_structured() local
331 return structured != NULL && IS_PTR_ALIGNED(structured, struct shell_cmd_help) && in shell_help_is_structured()
332 structured->magic == SHELL_STRUCTURED_HELP_MAGIC; in shell_help_is_structured()
/Zephyr-4.2.1/subsys/logging/backends/
DKconfig.net17 bool "Print structured data according to RFC 5424"
19 Print additional structured data as described in
/Zephyr-4.2.1/boards/espressif/common/
Dbuilding-flashing.rst55 Zephyr build. Output is structured by the domain subdirectories:
/Zephyr-4.2.1/boards/renesas/ek_ra8m2/doc/
Dindex.rst145 Zephyr build. Output is structured by the domain subdirectories:
/Zephyr-4.2.1/boards/renesas/mck_ra8t2/doc/
Dindex.rst139 Zephyr build. Output is structured by the domain subdirectories:
/Zephyr-4.2.1/boards/renesas/ek_ra8d2/doc/
Dindex.rst164 Zephyr build. Output is structured by the domain subdirectories:
/Zephyr-4.2.1/doc/services/instrumentation/
Dindex.rst13 Unlike the :ref:`tracing <tracing>` subsystem, which provides RTOS-aware tracing with structured
/Zephyr-4.2.1/boards/st/stm32h750b_dk/doc/
Dindex.rst147 Zephyr build. Output is structured by the domain subdirectories:
/Zephyr-4.2.1/boards/renesas/ek_ra8p1/doc/
Dindex.rst187 Zephyr build. Output is structured by the domain subdirectories:
/Zephyr-4.2.1/doc/build/sysbuild/
Dindex.rst544 a CMake function call that is structured as follows:
577 In the previous example, :file:`sysbuild.cmake` would be structured as follows:
588 :file:`Kconfig.sysbuild` would be structured as follows:
/Zephyr-4.2.1/doc/connectivity/bluetooth/shell/audio/
Dmcp.rst38 The content of the media player is structured into tracks and groups.
/Zephyr-4.2.1/doc/safety/
Dsafety_overview.rst225 To create and maintain a structured software product it is also necessary to consider individual
/Zephyr-4.2.1/doc/hardware/porting/
Darch.rst378 to be structured. Some helper functions can be used:
/Zephyr-4.2.1/doc/develop/test/
Dtwister.rst105 The board metadata file is located in the board directory and is structured
/Zephyr-4.2.1/doc/releases/
Drelease-notes-3.7.rst1539 * Added structured logging support to syslog net backend.
Drelease-notes-1.14.rst1206 * :github:`15017` - Not able to set "0xFFFF No specific value" for GAP PPCP structured data
/Zephyr-4.2.1/doc/
Dzephyr.doxyfile.in1527 # shown in the various tree structured indices initially; the user can expand