Searched refs:what (Results 101 – 125 of 245) sorted by relevance
12345678910
| /Zephyr-latest/doc/develop/toolchains/ |
| D | custom_cmake.rst | 27 :zephyr_file:`cmake/modules/FindTargetTools.cmake` for more details on what your
|
| /Zephyr-latest/samples/net/sockets/txtime/ |
| D | Kconfig | 57 This tells what is the expected sending time of the network
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 43 A license tells you what rights you have as a developer, as provided by the
320 system to see what's been reported on the issue you'd like to address. Have a
322 Server`_) to see what others think of your issue (and proposed solution). You
434 If you're not sure what to use, try running ``git log FILE``, where
440 what you've done. Here are some examples:
454 This part of the commit should explain what your change does, and why
458 * **what** the change does,
460 * **what** assumptions were made, and
656 what build or test failed click on the row that contains the failed (i.e.
939 #. Make sure title of PR explains what is being fixed or added
[all …]
|
| /Zephyr-latest/cmake/modules/ |
| D | FindBabbleSim.cmake | 17 # Note that what we find through the environment variables is meant to have precedence.
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig | 96 Do not mess with it unless you know what you are doing.
|
| /Zephyr-latest/samples/drivers/fpga/fpga_controller/ |
| D | README.rst | 66 After executing the sample, you can see at what address it is stored and its size in bytes.
|
| /Zephyr-latest/subsys/net/l2/ieee802154/ |
| D | Kconfig | 28 verbose, do not enable this unless you know what you are doing.
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf54l15bsim.rst | 59 For more information on what is modeled to which level of detail,
|
| /Zephyr-latest/doc/security/standards/ |
| D | etsi-303645.rst | 460 cannot guarantee what configuration will be required for the device to operate.
698 what personal data is processed, how it is being used, by whom, and for what purposes,
733 shall be provided with information on what telemetry data is collected, how it is
734 being used, by whom, and for what purposes.
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 127 A :ref:`recent CMake version <install-required-tools>` is required. Check what
189 A :ref:`recent DTC version <install-required-tools>` is required. Check what
198 what version you have by using ``python3 --version``.
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.nrf5 | 28 you know what you are doing.
|
| /Zephyr-latest/scripts/net/ |
| D | README.txt | 44 User can see what samples are supported like this:
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.ublox-sara-r4 | 89 Do not mess with it unless you know what you are doing.
|
| /Zephyr-latest/doc/services/tfm/ |
| D | integration.rst | 52 /* The memory regions defined below must match what the TF-M
|
| /Zephyr-latest/boards/shields/x_nucleo_iks02a1/doc/ |
| D | index.rst | 51 using the JP7/JP8 jumpers to modify to what the I2C1 bus connects to.
|
| /Zephyr-latest/doc/build/dts/ |
| D | design.rst | 81 dtschema does not yet meet Zephyr's needs, we should try to follow what it is
|
| D | dt-vs-kconfig.rst | 42 what driver or drivers it's compatible with, etc.
|
| /Zephyr-latest/doc/hardware/cache/ |
| D | guide.rst | 6 This section discusses the basics of cache coherency and under what situations a
31 processor's cache, resulting in what appears to be corrupt data. If you are
|
| /Zephyr-latest/doc/security/ |
| D | reporting.rst | 116 sensitive nature of what is being fixed, and shall not refer to CVE
118 should merely describe what has been fixed.
|
| /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
75 1. The ``west bindesc`` tool would be able to recognize what the descriptor means and
|
| /Zephyr-latest/doc/develop/west/ |
| D | basics.rst | 181 placed within the workspace, what URLs to clone them from, and what Git
|
| /Zephyr-latest/samples/subsys/zbus/remote_mock/ |
| D | README.rst | 13 …ts more controllability and observability since we can control and access what is sent and receive…
|
| /Zephyr-latest/doc/project/ |
| D | documentation.rst | 29 To help understand what each test does and which functionality it tests we also
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_config.rst | 76 parameter can be used to give hints to the library about what kind of
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | networking_with_host.rst | 22 Depending on what board is used for development, the following options are
|
12345678910
