Home
last modified time | relevance | path

Searched refs:RAM (Results 201 – 225 of 665) sorted by relevance

12345678910>>...27

/openbmc/linux/Documentation/translations/zh_CN/staging/
H A Dxz.rst63 在用户中间中,LZMA2通常使用几兆字节大小的字典。解码器需要在RAM中放置字典,
/openbmc/linux/Documentation/arch/mips/
H A Dbooting.rst19 II) in RAM. The device tree can be located anywhere in the first
/openbmc/u-boot/drivers/rtc/
H A DKconfig105 battery-backed RAM. The driver supports access to the clock and RAM.
/openbmc/linux/Documentation/devicetree/bindings/regulator/
H A Drichtek,rtq2208.yaml17 switching operation in normal mode; the latter defines the operation in suspend to RAM mode.
19 No matter the RTQ2208 is configured to normal or suspend to RAM mode, there are two switching
/openbmc/linux/Documentation/arch/arm64/
H A Dkdump.rst37 whole system RAM is low memory. Outside of the low memory described
38 above, the rest of system RAM is considered high memory.
/openbmc/linux/arch/sh/mm/
H A DKconfig46 does not specify the range that RAM takes.
48 The physical memory (RAM) start address will be automatically
50 boards typically map RAM at 0C000000.
/openbmc/linux/arch/m68k/q40/
H A DREADME79 The Q40 consists of a 68040@40 MHz, 1MB video RAM, up to 32MB RAM, AT-style
82 The Q60 has any of 68060 or 68LC060 and up to 128 MB RAM.
/openbmc/qemu/docs/about/
H A Dremoved-features.rst149 ``-mem-path`` fallback to RAM (removed in 5.0)
152 If guest RAM allocation from file pointed by ``mem-path`` failed,
153 QEMU was falling back to allocating from RAM, which might have resulted
157 ``-m`` and QEMU fails to start up if RAM allocation is unsuccessful.
168 The parameter ``mem`` of ``-numa node`` was used to assign a part of guest RAM
169 to a NUMA node. But when using it, it's impossible to manage a specified RAM
173 However since 2014 there is an alternative way to assign RAM to a NUMA node
175 means to actually manage node RAM on the host side. Use parameter ``memdev``
186 Splitting RAM by default between NUMA nodes had the same issues as ``mem``
191 Users of existing VMs, wishing to preserve the same RAM distribution, should
[all …]
/openbmc/u-boot/drivers/tee/
H A DKconfig26 of the TA is only kept in RAM and will be reset on each boot.
/openbmc/u-boot/arch/arm/mach-rockchip/
H A DMakefile39 obj-$(CONFIG_$(SPL_TPL_)RAM) += sdram_common.o
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-firmware-turris-mox-rwtm28 Description: (Read) RAM size in MiB of this Turris Mox board as was detected
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Power/
H A DACPIPowerState.interface.yaml35 Typically equates to "suspend-to-RAM".
/openbmc/openbmc/poky/meta/recipes-support/lz4/
H A Dlz4_1.9.4.bb2 …ely fast decoder, with speed in multiple GB/s per core, typically reaching RAM speed limits on mul…
/openbmc/linux/drivers/soc/loongson/
H A DKconfig26 S2Idle (Suspend To Idle), ACPI S3 (Suspend To RAM), ACPI S4 (Suspend To
/openbmc/linux/Documentation/arch/loongarch/
H A Dbooting.rst37 u64 load_offset /* Kernel image load offset from start of RAM */
/openbmc/u-boot/drivers/fastboot/
H A DKconfig41 downloads. Define this to the starting RAM address to use for
54 platform. Define this to the size available RAM for fastboot.
/openbmc/qemu/docs/specs/
H A Dedu.rst93 direction (0: from RAM to EDU, 1: from EDU to RAM)
/openbmc/linux/arch/powerpc/boot/dts/
H A Dwii.dts17 * contiguous RAM range and will BUG() if the memreserve is outside
20 /*/memreserve/ 0x10000000 0x0004000;*/ /* DSP RAM */
/openbmc/linux/Documentation/devicetree/bindings/cache/
H A Dl2c2x0.yaml70 description: Cycles of latency for Data RAM accesses. Specifies 3 cells of
81 description: Cycles of latency for Tag RAM accesses. Specifies 3 cells of
83 should use 0. Controllers without separate read and write Tag RAM latency
/openbmc/linux/Documentation/power/
H A Duserland-swsusp.rst108 suspend to RAM; using this call causes the kernel to
109 immediately enter the suspend-to-RAM state, so this call must always
114 to disk, and then the system is suspended to RAM (this makes it possible
115 to resume the system from RAM if there's enough battery power or restore
/openbmc/u-boot/board/freescale/m5373evb/
H A DREADME228 mtest - simple RAM test
269 …table entries: 2048 (order: 1, 8192 bytes) Memory available: 28092k/32768k RAM, (1788k kernel code…
285 ttyS2 at 0xfc068000 (irq = 92) is a builtin ColdFire UART RAMDISK driver initialized: 16 RAM disks …
291 uclinux[mtd]: RAM probe address=0x4021c22c size=0x22b000 Creating 1 MTD partitions on "RAM":
/openbmc/u-boot/doc/
H A DREADME.uniphier448 BKSZ Description RAM slot Peripherals
450 0b00 15MB RAM / 1MB Peri 00000000-00efffff 00f00000-00ffffff
451 0b01 31MB RAM / 1MB Peri 00000000-01efffff 01f00000-01ffffff
452 0b10 64MB RAM / 1MB Peri 00000000-03efffff 03f00000-03ffffff
453 0b11 127MB RAM / 1MB Peri 00000000-07efffff 07f00000-07ffffff
/openbmc/qemu/docs/
H A Dnvdimm.txt28 normal RAM devices and vNVDIMM devices, e.g. $N should be >= 2 here.
31 of normal RAM devices and vNVDIMM devices, e.g. $MAX_SIZE should be
114 devices. Similarly to the RAM hotplug, the vNVDIMM hotplug is
128 N >= number of RAM devices +
133 M >= size of RAM devices +
/openbmc/linux/Documentation/devicetree/bindings/net/
H A Ddavinci_emac.txt24 - ti,davinci-no-bd-ram: boolean, does EMAC have BD RAM?
/openbmc/u-boot/board/renesas/sh7757lcr/
H A DREADME.sh7757lcr70 1. Copy u-boot image to RAM area.

12345678910>>...27