Searched refs:their (Results 51 – 75 of 351) sorted by relevance
12345678910>>...15
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | gatt.rst | 45 Each attribute contain a ``uuid``, which describes their type, a ``read``
47 callbacks can be set to NULL if the attribute permission don't allow their
|
| /Zephyr-latest/include/zephyr/arch/x86/ |
| D | memory.ld | 16 * are set up, such that read/write data/bss have their VMA addresses
94 * linked in this space. Otherwise, rodata and text are linked at their
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 55 generated ELF file to find kernel objects and places their memory addresses
88 may drop their own permission on an object with
89 :c:func:`k_object_release`, and their permissions are automatically
106 the object placement criteria will have their memory addresses placed in a
186 :c:func:`k_object_release` to relinquish their own permissions on an
209 * Device driver objects are considered initialized after their init function
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ppp.rst | 17 cannot be transmitted over a modem line on their own, without some data link
|
| /Zephyr-latest/samples/bluetooth/ |
| D | bluetooth.rst | 16 documentation and are prefixed with :literal:`hci_` in their folder names.
|
| /Zephyr-latest/doc/releases/ |
| D | index.rst | 75 Changes that require the user to modify their own application to support the new
96 the user in order to keep the existing behavior of their application belong in
|
| /Zephyr-latest/drivers/display/ |
| D | Kconfig.mcux_elcdif | 69 from their values in the default screen orientation when using this
107 from their values in the default screen orientation when using this
|
| /Zephyr-latest/boards/beagle/beaglebone_ai64/doc/ |
| D | index.rst | 68 the R5 cores always see their local ATCM at address 0x00000000 and their BTCM
|
| /Zephyr-latest/samples/boards/nordic/nrfx_prs/boards/ |
| D | nrf9160dk_nrf9160.overlay | 62 * those instances; the application will use them via nrfx drivers. But their
|
| /Zephyr-latest/cmake/modules/ |
| D | FindLlvmLld.cmake | 56 # Extract GNU ld version. Different distros have their
|
| /Zephyr-latest/ |
| D | CONTRIBUTING.rst | 21 ensure developers are following licensing criteria for their
|
| /Zephyr-latest/lib/utils/ |
| D | Kconfig | 16 buffers manage their own buffer memory and can store arbitrary data.
|
| /Zephyr-latest/modules/cmsis-nn/ |
| D | Kconfig | 39 their variants. The convolution is implemented in 2 steps: im2col
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | virtual_memory.rst | 152 to their corresponding user mode threads during thread creation.
162 Note that SoCs have their own additional mappings required to boot where
163 these mappings are defined under their own SoC configurations. These mappings
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 43 to build the binary locally on their development machine and flash remotely,
55 Linux operating system on their board.
88 installed the toolchain(s) and core(s) for your board following their
104 your board's documentation for their values.
273 To see a list of their arguments:
328 clearing their Zephyr cache, as caching issues can occur from time to time.
|
| /Zephyr-latest/boards/others/stm32_min_dev/doc/ |
| D | index.rst | 27 Each board vendor has their own variations in pin mapping on their boards'
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | comparator.rst | 24 configuration must be provided using the devicetree. At runtime, comparators can have their
|
| /Zephyr-latest/boards/shields/adafruit_neopixel_grid_bff/doc/ |
| D | index.rst | 52 When using this example, all of the LEDs will be set to their maximum
|
| /Zephyr-latest/samples/posix/env/ |
| D | README.rst | 65 The shell command below may be used to display all environment variables and their associated
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/ |
| D | CMakeLists.txt | 36 # "helper" functions can be isolated in their own file, minimizing visual
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 20 An up-to-date table of all APIs and their maturity level can be found in the
127 A breaking API change is defined as one that forces users to modify their
128 existing code in order to maintain the current behavior of their application.
232 back to their previous form
246 ``docs.zephyrproject.org`` and support developers migrating their code. Zephyr
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 19 is supported by Zephyr, and the features and their availability documented
86 the applications that implement their own (non-standard) class library and do
166 because their ``testcase.yaml`` configuration lets ``twister`` iterate
179 their C90 mode.
240 unfortunately require enclosing their designated initializers with
|
| /Zephyr-latest/subsys/net/l2/ |
| D | Kconfig | 37 implementation for this L2 - users can implement their own L2 using
|
| /Zephyr-latest/soc/native/inf_clock/ |
| D | Kconfig | 18 native simulator as their runner.
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | find_functions.cocci | 14 // are not loosing their const qualifier.
|
12345678910>>...15
