Searched refs:spaces (Results 1 – 25 of 42) sorted by relevance
12
| /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/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/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 | 87 # note that the pattern will affect empty spaces created after FILL(0x00).
|
| /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/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/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.
|
| /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/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/drivers/ethernet/ |
| D | Kconfig | 49 spaces between arguments. Example: "mac=02:03:04:f0:0d:01" or
|
| /Zephyr-latest/boards/digilent/zybo/doc/ |
| D | index.rst | 147 …https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/749142017/Using+Distro+Boot+With+Xilinx+U-Bo…
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | x86.rst | 51 - Physical and virtual address spaces must be disjoint. This is
|
| /Zephyr-latest/boards/amd/kv260_r5/doc/ |
| D | index.rst | 77 https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+K26+SOM#PetaLinux
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | guidelines.rst | 36 Tabs, spaces, and indenting
39 Indenting is significant in reST file content, and using spaces is
86 spaces.
94 using a ``#`` sign. Indent continuation lines with three spaces::
455 spaces (to the first non-white space of the directive name).
571 (``::``) and indent the code block content that follows it by three spaces. On output, only one
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | virtual_memory.rst | 15 between physical and virtual memory address spaces, if demand paging
|
| /Zephyr-latest/tests/unit/cbprintf/ |
| D | main.c | 384 size_t spaces = 255; in ZTEST() local
389 while (spaces-- > 0) { in ZTEST()
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 23 and data spaces, but the hardware page table refill mechanism (see
24 below) does not, and Zephyr's memory spaces are unified regardless.
|
| /Zephyr-latest/soc/espressif/esp32s3/ |
| D | default_appcpu.ld | 40 /* Flash segments (rodata and text) should be mapped in the virtual address spaces.
|
| /Zephyr-latest/soc/espressif/esp32/ |
| D | default_appcpu.ld | 40 /* Flash segments (rodata and text) should be mapped in the virtual address spaces.
|
| /Zephyr-latest/boards/openisa/rv32m1_vega/doc/ |
| D | index.rst | 429 - Don't use installation directories with spaces anywhere in the path;
739 Don't use installation directories with spaces anywhere in
|
12
