Searched refs:their (Results 326 – 350 of 351) sorted by relevance
1...<<1112131415
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.7.rst | 40 * New documentation pages have been introduced to help developers setup their local development
710 need their devicetree updated, see the display section of
1031 * Added mspi/api and mspi/flash testcase for developers to check their implementations.
1616 * Added :c:macro:`DT_NODELABEL_STRING_ARRAY` and :c:macro:`DT_NUM_NODELABELS` and their variants.
|
| D | release-notes-3.5.rst | 440 subsystems no longer have their marshalling functions generated.
587 existing drivers couldn't properly express their channel page and channel
661 * Fixed regulators can now specify their operating voltage
|
| D | release-notes-2.1.rst | 434 their own standalone repositories.
440 box" experience for developers, from setting up their development
|
| D | release-notes-3.3.rst | 130 upon their behaviour previously, these will need to be updated in order for
194 below for the list of deprecated Kconfig options and their replacements:
218 Deprecated functions and their replacements:
235 Deprecated callback types and their replacements:
1482 - All DMA controller devices have had their ``dma-buf-alignment``
2720 - :github:`53505` - Some device tree integers may be signed or unsigned depending on their value
3785 * :github:`29087` - Moving (some) boards to their own repo/module
|
| D | release-notes-2.6.rst | 488 according to their function.
521 and the protect implementation removed from their API tables.
524 flash_erase() driver shims will wrap their calls with calls to the protect
870 according to their function. Driver's Kconfig options are revised and renamed.
979 their own standalone repositories.
|
| D | release-notes-4.0.rst | 36 enabling users to add haptic feedback to their applications.
1345 for users that intend to directly call them in their code.
|
| D | release-notes-2.4.rst | 69 had their signature changed to add a struct device pointer as first parameter.
170 when their flag is set, otherwise always call bt_recv().
875 their own standalone repositories.
|
| D | release-notes-2.3.rst | 77 their devices.
705 their own standalone repositories.
|
| D | release-notes-3.1.rst | 744 multiple specific modules and their dependencies
815 * Some bindings had their :ref:`compatible properties <dt-important-props>`
|
| D | release-notes-3.4.rst | 891 their initial sector split into two parts (usually marked as 0a and 0b).
|
| D | release-notes-3.0.rst | 639 * Make mdns and llmnr responders join their multicast groups.
|
| D | release-notes-2.0.rst | 484 in their own standalone repositories.
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 674 Developers are encouraged to run the script locally to validate their changes
1026 to try to give such changes increased review and user visibility due to their
|
| /Zephyr-latest/share/sysbuild/cmake/modules/ |
| D | sysbuild_extensions.cmake | 676 # this stage, their sysbuild.cmake files will be included as well, and so on.
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 484 their I/O regions, :kconfig:option:`CONFIG_MMU` needs to be enabled and the
680 all memory regions be sized to a power of two, and aligned to their own size.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 508 must be enabled separately and each resource needs their own storage.
|
| /Zephyr-latest/scripts/ |
| D | spelling.txt | 1565 thier||their
|
| /Zephyr-latest/boards/openisa/rv32m1_vega/doc/ |
| D | index.rst | 750 with their system package manager.
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 1059 hardware map needs to be created with all connected devices and their
1060 details such as the serial device, baud and their IDs if available.
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig | 193 combined builds for single CPU SoCs, applications can use their own
|
| /Zephyr-latest/boards/native/native_sim/doc/ |
| D | index.rst | 50 Note that some drivers may have limitations, or may not support their whole driver API optional
|
| /Zephyr-latest/drivers/wifi/nxp/ |
| D | Kconfig.nxp | 1110 with their timestamp.
|
| /Zephyr-latest/ |
| D | Kconfig.zephyr | 879 By default, all sections will have their LMA adjusted. The following
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 690 set the bondable flag in their pairing request. Any other kind of
|
| /Zephyr-latest/cmake/modules/ |
| D | extensions.cmake | 748 # This lets the user set the runner at cmake time, or in their
1277 # files must instead define their own output sections to achieve the same thing:
4618 # This allows Zephyr developers to define linker sections and their content and
|
1...<<1112131415
