Searched refs:what (Results 126 – 150 of 245) sorted by relevance
12345678910
| /Zephyr-latest/samples/modules/lvgl/demos/ |
| D | README.rst | 13 …The music player demo shows what kind of modern, smartphone-like user interfaces can be created on…
|
| /Zephyr-latest/subsys/mgmt/updatehub/ |
| D | Kconfig | 123 storage is still valid, it only confirms that what has been
|
| /Zephyr-latest/doc/releases/ |
| D | index.rst | 76 release may be mentioned in the release notes, but the details regarding *what*
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_user_setup.rst | 66 this command line will be reported by QEMU only. Here's what this particular
|
| D | eth_bridge_native_sim_setup.rst | 27 The ``-i`` option tells what is the first host interface name. The ``-t`` tells how
|
| /Zephyr-latest/drivers/display/ |
| D | Kconfig.mcux_elcdif | 31 the display will show what is effectively a dump of
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_2.rst | 142 may be considered optional as it is known during compilation what groups will
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 74 :ref:`comparison of what the POSIX arch provides vs other options<posix_arch_compare>`.
93 - Integration tests on workstation (what the POSIX arch and these boards enable)
306 From the command line the user can query what tests are present, and select
336 its own separate ``bs_tests`` built with that MCU. You can select if and what test is used
|
| /Zephyr-latest/samples/drivers/uart/native_tty/ |
| D | README.rst | 28 ``/dev/ttyUSB0`` and ``/dev/ttyUSB1`` in the system. You can check what they
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 63 except what is noted above.
187 instantiate device drivers, or define system calls, regardless of what
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_l2.rst | 43 stack does not know what to do with it. Instead, it passes the
45 The L2 stack does what it needs to do with the packet, for example, parsing
|
| D | net_if.rst | 46 See Kconfig file :zephyr_file:`subsys/net/ip/Kconfig` what options are available for
|
| /Zephyr-latest/doc/project/ |
| D | proposals.rst | 72 - The project roadmap communicates the why; a release plan details the what
|
| D | working_groups.rst | 72 unable to reach consensus on what advice to offer, the working group Chair
|
| /Zephyr-latest/doc/develop/west/ |
| D | why.rst | 118 can always find out what is happening "under the hood" when using west.
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | x86.rst | 123 the ``gen_mmu.py`` script will print out a message indicating what
|
| /Zephyr-latest/doc/services/llext/ |
| D | load.rst | 96 * Use a debugger to inspect the memory and registers to try to understand what
|
| /Zephyr-latest/doc/build/version/ |
| D | index.rst | 38 field to a single byte (note that there may be further restrictions depending upon what the version
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf5340bsim.rst | 50 For more information on what is modelled to which level of detail,
|
| /Zephyr-latest/doc/kernel/services/ |
| D | polling.rst | 39 Each event must specify what **kernel object** it wants the condition to be
56 in the array to figure out which ones were fulfilled and what actions to take.
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 32 To enable asynchronous operations, especially with DMA, a description of what
85 and device on the bus it is embodied in what RTIO calls an iodev.
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-syntax.rst | 50 # SPI memory chip, use 'on-bus:' to say what type of bus, like this.
513 If the node is a bus controller, use ``bus:`` in the binding to say what type
544 what type of bus.
567 what bus it appears on. For example, consider a sensor device with compatible
|
| /Zephyr-latest/doc/develop/languages/c/ |
| D | picolibc.rst | 32 available to adjust the feature set in the library, balancing what the
|
| /Zephyr-latest/boards/cdns/xt-sim/doc/ |
| D | index.rst | 46 #aptitude install gcc-multilib # Or what ever package manager (apt, apt-get, ...)
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 150 :c:func:`usbd_init` does only what is necessary to detect VBUS changes. There
245 the implementation of these functions checks in what context they are called
|
12345678910
