Searched refs:physical (Results 1 – 25 of 128) sorted by relevance
123456
| /Zephyr-latest/doc/hardware/arch/ |
| D | x86.rst | 16 is executing in virtual address space. By default, physical and virtual
18 taking place in physical address space. The physical address space is
29 On 32-bit x86, it is possible to have separate physical and virtual
31 but are still loaded in physical memory. However, during boot, code
32 and data must be available and also addressable in physical address
37 (:file:`arch/x86/gen_mmu.py`) identity maps the physical addresses
39 to the physical memory. Later in the boot process,
42 the identity mapping of physical memory. This unmapping must be done
44 restricted memory via physical addresses. Since the identity mapping
95 ``<physical address>,<size>[,<flags:LUWX>[,<virtual address>]]``, where:
[all …]
|
| /Zephyr-latest/subsys/sensing/sensor/phy_3d_sensor/ |
| D | Kconfig | 5 bool "sensing subsystem physical 3d sensors(accel, gyro, mag)"
9 Enable sensing subsystem physical 3d sensors(accel, gyro, mag).
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | kscan.rst | 17 many keys through fewer physical pins. Keyboard matrix
20 There is no correlation between the physical and electrical layout of keys.
21 For, example, the physical layout may be one array of 16 or fewer keys, which
|
| /Zephyr-latest/include/zephyr/arch/x86/ |
| D | memory.ld | 11 * By default, the kernel is linked at its physical address and all addresses
21 * LMA for all sections relative to physical address. The virtual address VMAs
34 /* Bounds of physical RAM from DTS */
39 * the same as its physical location, although an identity mapping for RAM
87 * or copied into physical RAM by a loader (MMU)
95 * physical ROM locations
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | virtual_memory.rst | 15 between physical and virtual memory address spaces, if demand paging
22 the physical memory.
26 allowing larger usable memory than the available physical memory.
29 * Although the virtual memory space can be larger than physical
31 mapped memory must be backed by physical memory.
60 virtual and physical addresses, instead of kernel choosing addresses within
122 * If it is enabled, which means all physical memory are mapped in virtual
170 The unused physical memory can be mapped in virtual address space on demand.
174 * :c:func:`k_mem_map` can be used to map unused physical memory:
|
| D | demand_paging.rst | 6 Demand paging provides a mechanism where data is only brought into physical
7 memory as required by current execution context. The physical memory is
15 the corresponding data page from backing store into physical memory if
25 page into the free page frame. Now the data page is in physical memory
32 minimize number of page faults as these data pages are already in physical
50 A page frame is a page-sized physical memory region in RAM. It is a
52 physical address. Zephyr has a convention of using ``uintptr_t`` for physical
63 * ``K_MEM_PAGE_FRAME_RESERVED`` indicates a physical page reserved by hardware
66 * ``K_MEM_PAGE_FRAME_MAPPED`` is set when a physical page is mapped to
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.vm | 22 By default, this is the same as the DT_CHOSEN_Z_SRAM physical base SRAM
27 as their physical address (demand paging at runtime may later modify
35 the kernel's address space, such as not overlapping physical RAM
36 regions if RAM is not identity-mapped, or the virtual and physical
42 page tables are in use, they all have the same virtual-to-physical
53 build-time cases, or when a physical address cannot be looked up
59 Will be used to convert between physical and virtual addresses for
63 physical memory have dissimilar alignment.
80 implement a notion of "high" memory in Zephyr to work around physical
88 mapping between virtual address and physical address.
|
| /Zephyr-latest/boards/qemu/x86/ |
| D | qemu_x86_atom_virt_defconfig | 24 # For now, the mapped stacks require physical addresses
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | triggers.rst | 13 data ready to physical events such as taps or steps.
|
| D | channels.rst | 10 the same physical property (e.g. acceleration); or because they can measure
|
| /Zephyr-latest/subsys/shell/modules/ |
| D | Kconfig | 24 This shell command provides read/write access to physical memory.
|
| /Zephyr-latest/boards/qemu/cortex_a53/ |
| D | Kconfig.defconfig | 27 # QEMU PCI requires physical addresses with more than 32 bits
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | health_srv.rst | 8 faults in the mesh node and map the mesh nodes to their physical location.
36 through some physical behavior like blinking, playing a sound or vibrating.
|
| /Zephyr-latest/samples/boards/st/uart/single_wire/ |
| D | README.rst | 12 board. You need to establish a physical connection between pins PA2 (USART2_TX) and
|
| /Zephyr-latest/boards/brcm/bcm958401m2/doc/ |
| D | index.rst | 13 The BCM958401M2 is a PCIe card with the following physical features:
|
| /Zephyr-latest/boards/brcm/bcm958402m2/doc/ |
| D | a72.rst | 13 The ``bcm958402m2/bcm58402/a72`` is a PCIe card with the following physical features:
|
| D | m7.rst | 13 The ``bcm958402m2/bcm58402/m7`` is a PCIe card with the following physical features:
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | features.rst | 29 * Controller-only (HCI) over UART, SPI, USB and IPC physical transports
49 * Support for Controller (HCI) builds over different physical transports
|
| D | bluetooth-dev.rst | 64 and Controller, even if there is no physical transport. See :ref:`Embedded HCI
107 and have it interact with a physical external Bluetooth Controller.
125 instrumented like any other, and it communicates with a physical or virtual
128 - :ref:`bluetooth_qemu_native` for the physical controller
|
| /Zephyr-latest/samples/subsys/mgmt/osdp/ |
| D | README.rst | 14 secure data over any stream based physical channel. Read more about `OSDP here
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 12 The TLB stores virtual to physical translation for individual pages of
64 physical address. Which means that the page tables occupy a 4M region
65 of virtual, not physical, address space, in the same memory space
67 of which might be mapped in physical memory) are a linear array of
107 needs to tell the hardware how to find a physical address using the
201 top of physical memory. The intent here would (presumably) be that
202 these would be used by the kernel for all physical memory and that the
205 page-level control over physical memory (e.g. .text/.rodata is cached
246 the L1 data cache on the CPU. If the physical memory storing page
|
| /Zephyr-latest/boards/efinix/titanium_ti60_f225/doc/ |
| D | index.rst | 7 high performance with the lowest possible power on a small physical size. In addition, Efinix offer…
|
| /Zephyr-latest/subsys/net/lib/tls_credentials/ |
| D | Kconfig | 34 API to store credentials with integrity check against physical
|
| /Zephyr-latest/doc/security/standards/ |
| D | etsi-303645.rst | 46 - device which has physical limitations in either the ability to process data, the
64 - physical interface used by the manufacturer to communicate with the device during
103 … - physical interface that can be used to access the functionality of consumer IoT via a network.
111 * - physical interface
112 … - physical port or air interface (such as radio, audio or optical) used to communicate with the
113 device at the physical layer.
387 either by labelling on the device or via a physical interface.
402 it shall be implemented in such a way that it resists tampering by means such as physical,
506 - Device hardware should not unnecessarily expose physical interfaces to attack.
|
| /Zephyr-latest/doc/connectivity/lora_lorawan/ |
| D | index.rst | 13 LoRa acts as the physical layer (PHY) based on the chirp spread spectrum
|
123456
