Searched full:spaces (Results 1 – 25 of 79) sorted by relevance
1234
| /Zephyr-latest/subsys/usb/device/class/ |
| D | Kconfig.msc | 23 Spaces must be added to bring the string to 8 bytes.
30 Spaces must be added to bring the string to 16 bytes.
37 Spaces must be added to bring the string to 4 bytes.
|
| /Zephyr-latest/doc/develop/sca/ |
| D | sparse.rst | 10 spaces in C code with subsequent verification that pointers to different
11 address spaces do not get confused. Additionally it supports a ``force``
13 spaces. At the moment Zephyr introduces a single custom address space
|
| /Zephyr-latest/ |
| D | .yamllint | 9 min-spaces-from-content: 1
11 spaces: 2
|
| D | CODE_OF_CONDUCT.md | 53 This Code of Conduct applies within all community spaces, and also applies when
54 an individual is officially representing the community in public spaces.
96 includes avoiding interactions in community spaces as well as external channels
|
| /Zephyr-latest/arch/common/ |
| D | fill_with_zeros.ld | 8 * LLVM LLD fills empty spaces (created using ALIGN() or moving the location
10 * TrapInstr pattern is 0xd4d4d4d4. GNU LD fills empty spaces with 0x00
|
| D | CMakeLists.txt | 93 # note that the pattern will affect empty spaces created after FILL(0x00).
|
| /Zephyr-latest/doc/build/dts/ |
| D | phandles.rst | 193 specifier spaces before moving on to some information about devicetree
196 .. _dt-specifier-spaces:
198 Specifier spaces
201 *Specifier spaces* are a way to allow nodes to describe how you should
204 We'll start with an abstract, high level description of how specifier spaces
256 spaces. For example, we might have:
300 Associating properties with specifier spaces
306 - specifier spaces are identified by name
311 spaces.
|
| D | intro-syntax-structure.rst | 350 - between angle brackets (``<`` and ``>``), separated by spaces
366 - between angle brackets (``<`` and ``>``), separated by spaces
370 - between angle brackets (``<`` and ``>``), separated by spaces
|
| /Zephyr-latest/doc/contribute/style/ |
| D | kconfig.rst | 8 one tab plus two extra spaces.
|
| D | cmake.rst | 11 - **Indentation**: Use **2 spaces** for indentation. Avoid tabs to ensure
92 arguments that may contain spaces.
|
| D | code.rst | 24 * Use spaces instead of tabs to align comments after declarations, as needed.
|
| /Zephyr-latest/tests/drivers/counter/counter_basic_api/boards/ |
| D | frdm_rw612.overlay | 36 * For testing purposes, free up memory spaces not needed by the testing.
|
| D | rd_rw612_bga.overlay | 36 * For testing purposes, free up memory spaces not needed by the testing.
|
| /Zephyr-latest/samples/subsys/display/cfb_shell/ |
| D | README.rst | 109 double quotation marks when it contains spaces. If text hits the edge
121 marks when it contains spaces. If the text hits the edge of the display, the
|
| /Zephyr-latest/doc/develop/west/ |
| D | moving-to-west.rst | 38 with no spaces anywhere in the path.
|
| D | alias.rst | 13 parameters as they were passed to the original command. Spaces are considered
|
| /Zephyr-latest/include/zephyr/xen/public/ |
| D | memory.h | 84 domid_t foreign_domid; /* IFF gmfn_foreign. Should be 0 for other spaces. */
88 uint16_t res0; /* All the other spaces. Should be 0 */
|
| /Zephyr-latest/samples/boards/renesas/openamp_linux_zephyr/src/ |
| D | resource_table.h | 30 * Macro to convert across CM33/CM33_FPU and A55 address spaces
|
| /Zephyr-latest/samples/userspace/shared_mem/ |
| D | README.rst | 38 output is the first message without spaces. The two messages are
|
| /Zephyr-latest/samples/boards/phytec/reel_board/mesh_badge/ |
| D | README.rst | 28 separated by spaces are possible. The font used on the reel display
|
| /Zephyr-latest/subsys/shell/ |
| D | shell_ops.h | 289 * - if there are spaces at the cursor position, remove all spaces to the left
290 * - remove the non-spaces (word) until a space is found or a beginning of
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig | 49 spaces between arguments. Example: "mac=02:03:04:f0:0d:01" or
|
| /Zephyr-latest/lib/utils/ |
| D | base64.c | 133 /* Skip spaces before checking for EOL */ in base64_decode()
140 /* Spaces at end of buffer are OK */ in base64_decode()
|
| /Zephyr-latest/samples/boards/espressif/flash_memory_mapped/ |
| D | README.rst | 11 and data address spaces. This mapping works only for read operations. It is not possible to modify
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | x86.rst | 51 - Physical and virtual address spaces must be disjoint. This is
|
1234
