Searched refs:look (Results 51 – 75 of 108) sorted by relevance
12345
/Zephyr-latest/doc/connectivity/networking/ |
D | eth_bridge_native_sim_setup.rst | 82 The network interfaces look like this in Zephyr's side:
|
/Zephyr-latest/boards/ |
D | Kconfig | 10 if not found we look for the linker file in
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | smp_transport.rst | 76 frame look below.
|
/Zephyr-latest/doc/hardware/porting/ |
D | board_porting.rst | 186 - checking :ref:`boards` for names that look relevant, and reading individual 255 Your board directory should look like this: 375 In general, :file:`plank.dts` should look like this: 530 A :file:`Kconfig.plank` may look like this: 595 console, etc. The results are architecture-specific, but typically look 951 When extending a board, your board directory should look like:
|
/Zephyr-latest/doc/build/dts/ |
D | intro-input-output.rst | 26 The devicetree files inside the :file:`zephyr` directory look like this:
|
/Zephyr-latest/samples/kernel/metairq_dispatch/ |
D | README.rst | 84 look different based upon the clock frequency of the board and other
|
/Zephyr-latest/subsys/llext/ |
D | Kconfig | 108 harder and prevents usage of 'llext_find_sym' to look
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | coap_server.rst | 134 of CoAP services. An example using a temperature sensor can look like:
|
/Zephyr-latest/doc/build/snippets/ |
D | writing.rst | 83 system will look for :file:`snippet.yml` files underneath the following
|
/Zephyr-latest/samples/net/capture/ |
D | README.rst | 206 The actual captured network packets received at the end of the tunnel will look
|
/Zephyr-latest/doc/services/tfm/ |
D | build.rst | 142 For more information on these tools look here: :ref:`footprint_tools`
|
/Zephyr-latest/doc/build/kconfig/ |
D | menuconfig.rst | 92 things would look like in the ``menuconfig`` interface.
|
D | tips.rst | 261 way, without having to look for particular architectures: 634 idea to look up the symbols in :ref:`menuconfig or guiconfig <menuconfig>` 681 ``git grep FOO_BAR`` to look for references. It is also a good idea to search
|
/Zephyr-latest/boards/snps/nsim/arc_classic/doc/ |
D | index.rst | 38 It is recommended to look at precise description of a particular sub-configuration in either 298 It is advised to look for ``<board_name>_defconfig``, ``<board_name>.dts`` and
|
/Zephyr-latest/doc/build/ |
D | zephyr_cmake_package.rst | 307 Such a CMakeLists.txt could look as: 370 An example folder structure could look like this:
|
/Zephyr-latest/doc/services/binary_descriptors/ |
D | index.rst | 60 Putting it all together, here is what the example above would look like in memory
|
/Zephyr-latest/doc/hardware/arch/ |
D | arm-scmi.rst | 102 on the specification, the readers are encouraged to have a look at it.
|
/Zephyr-latest/doc/services/debugging/ |
D | gdbstub.rst | 129 #. Tell GDB where to look for the built ELF file:
|
/Zephyr-latest/cmake/modules/ |
D | kernel.cmake | 150 Move ${USER_CACHE_DIR}, re-run and look at ${log_file}")
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 364 message* describing the change. Acceptable commit messages look like 688 The output should look similar to:: 709 #. When things look good, start the pull request process by adding your changed 718 #. Verify changes to be committed look as you expected::
|
/Zephyr-latest/doc/develop/west/ |
D | extensions.rst | 176 multiple files, your :file:`west-commands.yml` will look something like this:
|
D | config.rst | 77 Doing the above means that commands like ``west update`` will look for the
|
/Zephyr-latest/doc/kernel/services/other/ |
D | fatal.rst | 62 look like the following:
|
/Zephyr-latest/boards/nxp/frdm_mcxn947/doc/ |
D | index.rst | 141 Please have a look at some already enabled samples:
|
/Zephyr-latest/doc/project/ |
D | release_process.rst | 463 tag must contain a signature (look for the ``BEGIN PGP SIGNATURE`` 501 tag must contain a signature (look for the ``BEGIN PGP SIGNATURE``
|
12345