Searched full:such (Results 1 – 25 of 961) sorted by relevance
12345678910>>...39
/Zephyr-Core-3.6.0/subsys/bindesc/ |
D | Kconfig.version | 14 The kernel version string, such as "3.4.0" 19 The major version number, such as 3 in 3.4.0 24 The minor version number, such as 4 in 3.4.0 29 The patchlevel version number, such as 0 in 3.4.0 41 The app version string, such as "1.0.0" 46 The app major version number, such as 1 in 1.0.0 51 The app minor version number, such as 0 in 1.0.0 56 The app patchlevel version number, such as 0 in 1.0.0
|
D | Kconfig.host_info | 19 The C compiler name, such as "GNU" 24 The C compiler version, such as "12.3.0" 29 The C++ compiler name, such as "GNU" 34 The C++ compiler version, such as "12.3.0"
|
D | Kconfig.build_time | 28 The year the image was compiled, such as 2023 33 The month the image was compiled, such as 5 (May) 38 The day of the month the image was compiled, such as 9 43 The hour of the day the image was compiled, such as 13 in 13:34:52 48 The minute the image was compiled, such as 34 in 13:34:52 53 The second the image was compiled, such as 52 in 13:34:52 64 The date and time of compilation as a string, such as "2023-09-29T17:43:14+0000" 69 The date of compilation as a string, such as "2023-09-29" 74 The time of compilation as a string, such as "T17:43:14+0000"
|
/Zephyr-Core-3.6.0/ |
D | LICENSE | 19 direction or management of such entity, whether by contract or 21 outstanding shares, or (iii) beneficial ownership of such entity. 71 Work and such Derivative Works in Source or Object form. 78 where such license applies only to those patent claims licensable 79 by such Contributor that are necessarily infringed by their 81 with the Work to which such Contribution(s) was submitted. If You 87 as of the date such litigation is filed. 109 within such NOTICE file, excluding those notices that do not 115 wherever such third-party notices normally appear. The contents 120 that such additional attribution notices cannot be construed [all …]
|
/Zephyr-Core-3.6.0/cmake/linker/ |
D | linker_flags_template.cmake | 8 # such as ls --print-memory-usage flag. 17 # such as, "-no-pie" for LD, and "--no-pie" for LLD. 21 # such as, "-r" or "--relocatable" for LD and LLD.
|
/Zephyr-Core-3.6.0/doc/build/dts/ |
D | dt-vs-kconfig.rst | 27 property) and certain settings such as the address range of the hardware 30 devicetree. This could include configuration such as the RX IRQ line's 43 * **Boot-time configuration** for the radio, such as TX power in dBm, should 46 radio, such as selecting a BLE or 802.15.4 protocol stack. 57 configuration parameters, such as the size of an internal buffer, these
|
/Zephyr-Core-3.6.0/include/zephyr/linker/ |
D | linker-tool-lld.h | 35 * @param options Section options, such as (NOLOAD), or left blank 36 * @param align Alignment directives, such as SUBALIGN(). May be blank. 48 * program startup). Such a section must also use 55 * @param align Alignment directives, such as SUBALIGN(). May be blank.
|
D | linker-tool-mwdt.h | 26 * of sections located in one memory area, such as RAM, ROM, etc. 54 * also be used on the first section *after* such an initialized data 77 * is to include any special options such as (NOLOAD). Page alignment has its 88 * program startup). Such a section must (!) also use
|
D | linker-tool-gcc.h | 68 * of sections located in one memory area, such as RAM, ROM, etc. 171 * @param options Section options, such as (NOLOAD), or left blank 172 * @param align Alignment directives, such as SUBALIGN(). ALIGN() itself is 190 * program startup). Such a section must also use 198 * @param align Alignment directives, such as SUBALIGN(). ALIGN() itself is
|
/Zephyr-Core-3.6.0/include/zephyr/ |
D | bindesc.h | 36 /** The app version string such as "1.2.3" */ 39 /** The app version major such as 1 */ 42 /** The app version minor such as 2 */ 45 /** The app version patchlevel such as 3 */ 48 /** The app version number such as 0x10203 */ 51 /** The kernel version string such as "3.4.0" */ 54 /** The kernel version major such as 3 */ 57 /** The kernel version minor such as 4 */ 60 /** The kernel version patchlevel such as 0 */ 63 /** The kernel version number such as 0x30400 */ [all …]
|
/Zephyr-Core-3.6.0/doc/services/storage/stream/ |
D | stream_flash.rst | 17 other operations, such as radio RX and TX. Also, fewer write operations result 22 Some stream write operations, such as DFU operations, may run for a long time. 23 When performing such long running operations it can be useful to be able to save
|
/Zephyr-Core-3.6.0/doc/develop/languages/c/ |
D | index.rst | 28 as C99) such as those listed below, effectively requiring the use of a compiler 40 C11) such as the type-generic expressions using the ``_Generic`` keyword. For 51 compiler toolchain that supports such standards. 78 C defines standard formatted output functions such as ``printf`` and 114 <memory_management_api>` supported by the Zephyr kernel such as 118 C standard dynamic memory management interface functions such as
|
/Zephyr-Core-3.6.0/include/zephyr/net/ |
D | dns_sd.h | 102 * @param _instance name of the service instance such as "My HTTP Server" 103 * @param _service name of the service, such as "_http" 105 * @param _domain the domain of the service, such as "local" 153 * @param instance name of the service instance such as "My HTTP Server" 154 * @param service name of the service, such as "_http" 155 * @param domain the domain of the service, such as "local" 184 * @param instance name of the service instance such as "My TFTP Server" 185 * @param service name of the service, such as "_tftp" 186 * @param domain the domain of the service, such as "local" or "zephyrproject.org" 224 /** Top half of the <Service> such as "_http" */ [all …]
|
/Zephyr-Core-3.6.0/drivers/interrupt_controller/ |
D | Kconfig.intel_vtd | 13 Such interrupt remapping hardware is provided through Intel VT-D 15 multi-vector support. If you have such PCIe device requiring
|
/Zephyr-Core-3.6.0/samples/boards/nrf/nrfx_prs/ |
D | README.rst | 10 and base address. Such peripherals cannot be used simultaneously because they 14 a driver at boot, such switching cannot be achieved with Zephyr APIs. Therefore, 32 is also received back. Without such wiring, no data is received by UARTE and
|
/Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/ |
D | connection_mgmt.rst | 9 (such as the remote address) can be acquired using the 22 events related to a connection such as a change in the security level or
|
/Zephyr-Core-3.6.0/lib/mem_blocks/ |
D | Kconfig | 14 This is useful for operations such as scatter-gather DMA 27 events, such as memory allocation and de-allocation.
|
/Zephyr-Core-3.6.0/doc/templates/ |
D | sample.tmpl | 15 hardware components such as sensors and shields] 35 [ Links to external references such as datasheets or additional documentation]
|
/Zephyr-Core-3.6.0/soc/xtensa/intel_adsp/ace/include/intel_ace15_mtpm/ |
D | adsp_boot.h | 17 * control, such as reset, stall, power gating, clock gating etc. 32 * control, such as boot path, watch dog timer etc.
|
/Zephyr-Core-3.6.0/soc/xtensa/intel_adsp/ace/include/intel_ace20_lnl/ |
D | adsp_boot.h | 17 * control, such as reset, stall, power gating, clock gating etc. 32 * control, such as boot path, watch dog timer etc.
|
/Zephyr-Core-3.6.0/include/zephyr/drivers/flash/ |
D | npcx_flash_api_ex.h | 22 * configuration such as status registers of nor flash, power on/off, 29 * It configures specific operation for Quad-SPI nor flash such as lock
|
/Zephyr-Core-3.6.0/subsys/bluetooth/controller/coex/ |
D | readme.rst | 8 …er.c` is designed to utilize co-existence with another transmitter. Chips such as nordic nRF9160 p… 22 Whenever the grant pin transitions into non-active (such as 1 for the nRF9160). state the implement…
|
/Zephyr-Core-3.6.0/tests/subsys/logging/log_blocking/ |
D | REAME.md | 22 with units such as `[msg/s]`. However, in the table below, we are mainly 25 `N` such that `N > 1`. 42 Many log backends, such as UARTs, have a built-in hardware FIFO that 44 based on the baud rate of the UART. Other backends, such as UDP sockets or
|
/Zephyr-Core-3.6.0/doc/kernel/usermode/ |
D | overview.rst | 20 - The kernel can sandbox complex data parsers such as interpreters, network 21 protocols, and filesystems such that malicious third-party code or data 35 memory that has an incompatible policy, such as attempting to write to a 142 domains, or via kernel objects such as semaphores and pipes. 152 driver other than their own thread object. Such access must be granted by 167 - Thread stacks are defined in such a way that exceeding the specified stack
|
/Zephyr-Core-3.6.0/drivers/flash/ |
D | Kconfig.nordic_qspi_nor | 38 these restrictions. Such data will be copied into this buffer to 58 Primarily intended for long running operations such as
|
12345678910>>...39