Home
last modified time | relevance | path

Searched refs:figure (Results 226 – 240 of 240) sorted by relevance

12345678910

/Zephyr-latest/doc/contribute/documentation/
Dguidelines.rst716 .. figure:: ../../images/doc-gen-flow.png
719 Caption for the figure
/Zephyr-latest/doc/hardware/porting/
Dboard_porting.rst80 .. figure:: board/hierarchy.png
128 .. figure:: board/board-terminology.svg
/Zephyr-latest/doc/connectivity/networking/conn_mgr/
Dimplementation.rst46 .. figure:: figures/integration_diagram_detailed.svg
/Zephyr-latest/doc/kernel/usermode/
Dmemory_domain.rst241 .. figure:: auto_mem_domain.png
Dsyscalls.rst209 .. figure:: syscall_flow.png
/Zephyr-latest/doc/security/
Dsensor-threat.rst17 .. figure:: media/sensor-model.svg
/Zephyr-latest/doc/build/dts/
Dhowtos.rst17 includes the SoC's ``.dtsi``. One way to figure out the devicetree's contents
/Zephyr-latest/doc/kernel/services/smp/
Dsmp.rst154 .. figure:: smpinit.svg
/Zephyr-latest/doc/services/shell/
Dindex.rst424 Let's assume a command structure as in the following figure, where:
/Zephyr-latest/doc/develop/test/
Dtwister.rst246 .. figure:: figures/twister_test_project.svg
1405 .. figure:: figures/fixtures.svg
/Zephyr-latest/doc/build/kconfig/
Dtips.rst663 ``Included via ...`` path shown in the symbol information to figure out where
/Zephyr-latest/doc/develop/west/
Dmanifest.rst22 history, looks like the following figure (though some parts of this example are
25 .. figure:: west-mr-model.png
/Zephyr-latest/kernel/
DKconfig875 much worse but all we want here is a ball-park figure that ought
/Zephyr-latest/doc/releases/
Drelease-notes-3.0.rst309 * Introduced a mechanism to automatically figure out which scratch registers
/Zephyr-latest/samples/modules/tflite-micro/hello_world/train/
Dtrain_hello_world_model.ipynb2843 "plt.figure(figsize=(10, 4))\n",

12345678910