Searched refs:what (Results 176 – 200 of 245) sorted by relevance
12345678910
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 331 related to the sample and what is being demonstrated:
443 A board or platform can announce what features it supports, this option
578 what features it supports. This option will enable the test to run on
899 tests, the testing tools should be able to adapt the scope and select/filter out what
900 is relevant and what is not.
1422 - Option to specify your own list of default platforms overriding what
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 170 information helps figuring out what went wrong when hitting an exception that
234 what thread to context switch in. :code:`_Swap` is called by the kernel logic
461 decision on what to do next by invoking :c:func:`k_sys_fatal_error`.
473 See what exists in that file for currently supported architectures.
922 the G-packet is architecture specific. Consult GDB on what is
|
| /Zephyr-latest/boards/wiznet/w5500_evb_pico/doc/ |
| D | index.rst | 198 **RPI_PICO_DEBUG_ADAPTER** specifies what debug adapter is used for debugging.
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | testplan.py | 435 def info(what): argument
436 sys.stdout.write(what + "\n")
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | network_monitoring.rst | 200 You can use ``net iface`` command to see what network interfaces are available.
|
| D | net_config_guide.rst | 42 can be tweaked by selecting the size of the data part according to what kind of network
|
| /Zephyr-latest/samples/subsys/mgmt/mcumgr/smp_svr/ |
| D | README.rst | 208 with it using :file:`mcumgr`, you might want to test what is commonly called
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-upstream.rst | 192 Some examples of what **not** to do, and why:
|
| D | phandles.rst | 149 metadata about the GPIO, like whether it is active low or high, what kind of
|
| /Zephyr-latest/include/zephyr/arch/x86/ia32/ |
| D | linker.ld | 14 * This script places the various sections of the image according to what
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig | 852 This value tells what is the fixed size of each network buffer.
860 This value tell what is the size of the RX memory pool where each
869 This value tell what is the size of the TX memory pool where each
|
| /Zephyr-latest/doc/kernel/ |
| D | timeutil.rst | 19 discontinuities due to `leap seconds <https://what-if.xkcd.com/26/>`__ and
|
| /Zephyr-latest/boards/raspberrypi/rpi_pico/doc/ |
| D | index.rst | 232 **RPI_PICO_DEBUG_ADAPTER** specifies what debug adapter is used for debugging.
|
| /Zephyr-latest/boards/altr/max10/doc/ |
| D | index.rst | 266 In a terminal, launch the nios2 GDB server. It doesn't matter what kernel (if
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | Kconfig | 554 This value should typically be fine-tuned based on what
555 models the local node supports, i.e. what's the largest
576 This value should typically be fine-tuned based on what
577 models the local node supports, i.e. what's the largest
1574 ways that the node will be used and what kind of power source it
|
| /Zephyr-latest/ |
| D | Kconfig.zephyr | 593 limits checking to what can be done with information available
928 - off: the SHA of one or more west projects are not what the manifest
947 - off: the SHA of one or more west projects are not what the manifest
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 807 https://www.omaspecworks.org/what-is-oma-specworks/iot/lightweight-m2m-lwm2m/
813 https://www.omaspecworks.org/what-is-oma-specworks/iot/lightweight-m2m-lwm2m/
|
| D | net_pkt.rst | 230 to read what has been already written by resetting the cursor of the
|
| /Zephyr-latest/soc/intel/intel_adsp/ace/ |
| D | ace-link.ld | 277 * what to put in this section. It would mostly be things
|
| /Zephyr-latest/cmake/modules/ |
| D | dts.cmake | 33 # information on what is currently available to you.
|
| D | kconfig.cmake | 346 # Read out what the checksum was previously
|
| /Zephyr-latest/doc/services/debugging/ |
| D | coredump.rst | 413 GDB's code and documentation on what it is expecting for
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 299 The host-side setup depends on what debug probe you are using. Learn more in the Tracealyzer
349 The stream ports are small modules within TraceRecorder that define what functions to call to
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/audio/ |
| D | bluetooth-le-audio-arch.rst | 1039 It is left up to the implementation to determine what telephone bearer a characteristic of
1155 where multiple service have requirements for what to advertise and when,
1182 The choice of what the return type of the callbacks often depend on the specifications,
|
| /Zephyr-latest/subsys/net/lib/sockets/ |
| D | Kconfig | 148 This is mostly useful for TLS client side to tell TLS server what is
|
12345678910
