| /openbmc/linux/drivers/zorro/ |
| H A D | zorro.ids | 18 0000 Golem RAM Box 2MB [RAM Expansion]
37 2000 A560 [RAM Expansion]
75 4400 VXL RAM*32 [RAM Expansion]
85 0100 [RAM Expansion]
86 0200 [RAM Expansion]
199 0100 [RAM Expansion]
200 2000 [RAM Expansion]
214 0000 [RAM Expansion]
234 e000 RAM Works [RAM Expansion]
252 be00 [RAM Expansion]
[all …]
|
| /openbmc/u-boot/drivers/ram/ |
| H A D | Kconfig | 1 config RAM config
2 bool "Enable RAM drivers using Driver Model"
12 bool "Enable RAM support in SPL"
13 depends on RAM && SPL_DM
18 setting up RAM (e.g. SDRAM / DDR) within SPL.
21 bool "Enable RAM support in TPL"
22 depends on RAM && TPL_DM
27 setting up RAM (e.g. SDRAM / DDR) within TPL.
31 depends on RAM
39 depends on RAM
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/arch/arm/ |
| H A D | Booting | 40 1、设置和初始化 RAM。
47 1、设置和初始化 RAM
53 引导装载程序应该找到并初始化系统中所有内核用于保持系统变量数据的 RAM。
55 RAM，或可能使用对这个设备已知的 RAM 信息，还可能使用任何引导装载程序
117 标签列表应该保存在系统的 RAM 中。
120 建议放在 RAM 的头 16KiB 中。
126 RAM 中，并用启动数据初始化它。dtb 格式在文档
146 zImage 也可以被放在系统 RAM（任意位置）中被调用。注意：内核使用映像
147 基地址的前 16KB RAM 空间来保存页表。建议将映像置于 RAM 的 32KB 处。
157 r2 = 标签列表在系统 RAM 中的物理地址，或
[all …]
|
| /openbmc/qemu/tests/tcg/nios2/ |
| H A D | 10m50-ghrd.ld | 16 RAM PT_LOAD;
30 } >ram :RAM
34 } > ram :RAM
39 } >ram :RAM
42 } >ram :RAM
47 } >ram :RAM
53 } >ram :RAM
57 } >ram :RAM
67 } >ram :RAM
|
| /openbmc/linux/Documentation/admin-guide/blockdev/ |
| H A D | ramdisk.rst | 2 Using the RAM disk block device with Linux
10 4) An Example of Creating a Compressed RAM Disk
26 The RAM disk supports up to 16 RAM disks by default, and can be reconfigured
35 The new RAM disk also has the ability to load compressed RAM disk images,
48 This parameter tells the RAM disk driver to set up RAM disks of N k size. The
84 4) An Example of Creating a Compressed RAM Disk
87 To create a RAM disk image, you will need a spare block device to
88 construct it on. This can be the RAM disk device itself, or an
90 example, we will use the RAM disk device, "/dev/ram0".
111 d) Compress the contents of the RAM disk. The level of compression
[all …]
|
| /openbmc/u-boot/board/synopsys/iot_devkit/ |
| H A D | u-boot.lds | 11 RAM : ORIGIN = RAM_DATA_BASE, LENGTH = RAM_DATA_SIZE
45 /* Mark RAM's LMA */
51 /* Mark RAM's VMA */
56 * copied from ROM to RAM in board_early_init_f().
63 } > RAM AT > ROM
70 } > RAM
|
| /openbmc/u-boot/board/keymile/km_arm/ |
| H A D | kwbimage_256M8_1.cfg | 63 # bit 0-1: 2, Tag RAM RTC RAM0
64 # bit 3-2: 1, Tag RAM WTC RAM0
66 # bit 9-8: 2, Valid RAM RTC RAM
67 # bit 11-10: 1, Valid RAM WTC RAM
68 # bit 13-12: 2, Dirty RAM RTC RAM
69 # bit 15-14: 1, Dirty RAM WTC RAM
70 # bit 17-16: 2, Data RAM RTC RAM0
71 # bit 19-18: 1, Data RAM WTC RAM0
72 # bit 21-20: 2, Data RAM RTC RAM1
81 # bit 17-16: 2, ECC RAM RTC RAM0
[all …]
|
| H A D | kwbimage_128M16_1.cfg | 63 # bit 0-1: 2, Tag RAM RTC RAM0
64 # bit 3-2: 1, Tag RAM WTC RAM0
66 # bit 9-8: 2, Valid RAM RTC RAM
67 # bit 11-10: 1, Valid RAM WTC RAM
68 # bit 13-12: 2, Dirty RAM RTC RAM
69 # bit 15-14: 1, Dirty RAM WTC RAM
70 # bit 17-16: 2, Data RAM RTC RAM0
71 # bit 19-18: 1, Data RAM WTC RAM0
72 # bit 21-20: 2, Data RAM RTC RAM1
81 # bit 17-16: 2, ECC RAM RTC RAM0
[all …]
|
| /openbmc/u-boot/board/cobra5272/ |
| H A D | README | 41 16 MB RAM
51 # u-boot FLASH version & RAM version
56 1. as a standalone bootloader residing in flash & relocating itself to RAM on
59 2. as a RAM version which will not load from flash automatically as it needs a
60 prestage bootloader ("chainloading") & is running only from the RAM address it
61 is linked to => "RAM version"
110 RAM version
128 => u-boot as RAM version, chainloaded by another bootloader or using bdm cable
135 => target linking address for RAM
153 If the m68k-elf-toolchain & the m68k-bdm-gdb is installed you can run the RAM
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/net/can/ |
| H A D | bosch,m_can.yaml | 24 - description: message RAM
55 Message RAM configuration data.
56 Multiple M_CAN instances can share the same Message RAM
58 in Message RAM is also configurable, so this property is
59 telling driver how the shared or private Message RAM are
64 The 'offset' is an address offset of the Message RAM where
66 0x0 if you're using a private Message RAM. The remain cells
78 Please refer to 2.4.1 Message RAM Configuration in Bosch
82 - description: The 'offset' is an address offset of the Message RAM where
84 you're using a private Message RAM.
|
| /openbmc/u-boot/board/coreboot/coreboot/ |
| H A D | Kconfig | 23 hex "Board specific Cache-As-RAM (CAR) address"
26 This option specifies the board specific Cache-As-RAM (CAR) address.
29 hex "Board specific Cache-As-RAM (CAR) size"
32 This option specifies the board specific Cache-As-RAM (CAR) size.
|
| /openbmc/qemu/docs/system/ |
| H A D | vm-templating.rst | 39 Supply VM RAM via memory-backend-file, with ``share=on`` (modifications go
43 In the following command-line example, a 2GB VM is created, whereby VM RAM
56 leaving the current state of VM RAM reside in the file.
59 configure VM RAM to be based on a template VM RAM file; however, the VM
62 Supply VM RAM via memory-backend-file, with ``share=off`` (modifications
86 cannot be modified to discard VM RAM, or to actually share memory with
100 virtio-balloon inflation and "free page reporting" cannot discard VM RAM
102 for template VMs (e.g., report VM RAM stats), "free page reporting"
108 virtio-mem cannot discard VM RAM that is managed by the virtio-mem
119 RAM on the migration source to free up migrated RAM, and will
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/filesystems/ |
| H A D | tmpfs.rst | 22 一个东西是RAM磁盘（/dev/ram*），可以在物理RAM中模拟固定大小的硬盘，并在
56 size tmpfs实例分配的字节数限制。默认值是不swap时物理RAM的一半。
60 (有高端内存的机器)低端内存RAM的页数，二者以较低者为准。
64 size参数也接受后缀％用来限制tmpfs实例占用物理RAM的百分比：
135 /mytmpfs上挂载tmpfs实例，分配只能由root用户访问的10GB RAM/SWAP，可以有10240个
|
| /openbmc/linux/Documentation/translations/zh_TW/filesystems/ |
| H A D | tmpfs.rst | 23 一個東西是RAM磁碟（/dev/ram*），可以在物理RAM中模擬固定大小的硬碟，並在
57 size tmpfs實例分配的字節數限制。默認值是不swap時物理RAM的一半。
61 (有高端內存的機器)低端內存RAM的頁數，二者以較低者為準。
65 size參數也接受後綴％用來限制tmpfs實例占用物理RAM的百分比：
136 /mytmpfs上掛載tmpfs實例，分配只能由root用戶訪問的10GB RAM/SWAP，可以有10240個
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | raspi.rst | 8 ARM1176JZF-S core, 512 MiB of RAM
10 Cortex-A7 (4 cores), 1 GiB of RAM
12 Cortex-A53 (4 cores), 512 MiB of RAM
14 Cortex-A53 (4 cores), 1 GiB of RAM
|
| /openbmc/u-boot/arch/mips/mach-bmips/ |
| H A D | Kconfig | 135 of RAM and 128 MB of flash (nand).
145 Comtrend AR-5315u boards have a BCM6318 SoC with 64 MB of RAM and 16
178 Comtrend VR-3032u boards have a BCM63268 SoC with 64 MB of RAM and
189 Comtrend WAP-5813n boards have a BCM6369 SoC with 64 MB of RAM and
200 Huawei EchoLife HG556a boards have a BCM6358 SoC with 64 MB of RAM
211 Netgear CG3100D boards have a BCM3380 SoC with 64 MB of RAM and 8 MB
222 Netgear DGND3700v2 boards have a BCM6362 SoC with 64 MB of RAM and
233 Sagem F@ST1704 boards have a BCM6338 SoC with 16 MB of RAM and 4 MB
244 SFR NeufBox 4 (Sercomm) boards have a BCM6358 SoC with 32 MB of RAM
256 bool "RAM boot"
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/arch/arm64/ |
| H A D | booting.txt | 47 1、设置和初始化 RAM
53 1、设置和初始化 RAM
58 引导装载程序应该找到并初始化系统中所有内核用于保持系统变量数据的 RAM。
60 RAM，或可能使用对这个设备已知的 RAM 信息，还可能是引导装载程序设计者
154 x0 = 系统 RAM 中设备树数据块（dtb）的物理地址。
|
| /openbmc/linux/drivers/dax/ |
| H A D | Kconfig | 43 "System RAM" pool.
48 tristate "CXL DAX: direct access to CXL RAM regions"
52 CXL RAM regions are either mapped by platform-firmware
53 and published in the initial system-memory map as "System RAM", mapped
58 converted to "System RAM" via the dax_kmem facility.
65 tristate "KMEM DAX: map dax-devices as System-RAM"
71 differentiated memory as if it were System RAM. This allows
|
| /openbmc/linux/Documentation/translations/zh_TW/arch/arm64/ |
| H A D | booting.txt | 51 1、設置和初始化 RAM
57 1、設置和初始化 RAM
62 引導裝載程序應該找到並初始化系統中所有內核用於保持系統變量數據的 RAM。
64 RAM，或可能使用對這個設備已知的 RAM 信息，還可能是引導裝載程序設計者
158 x0 = 系統 RAM 中設備樹數據塊（dtb）的物理地址。
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-coresight-devices-etb10 | 16 Description: (RW) Disables write access to the Trace RAM by stopping the
19 into the Trace RAM following the trigger event is equal to the
26 Description: (Read) Defines the depth, in words, of the trace RAM in powers of
40 Description: (Read) Shows the value held by the ETB RAM Read Pointer register
41 that is used to read entries from the Trace RAM over the APB
49 Description: (Read) Shows the value held by the ETB RAM Write Pointer register
51 the CoreSight bus into the Trace RAM. The value is read directly
|
| /openbmc/linux/Documentation/arch/arm/ |
| H A D | porting.rst | 25 to be located in RAM, it can be in flash or other read-only or
30 This must be pointing at RAM. The decompressor will zero initialise
43 Physical address to place the initial RAM disk. Only relevant if
48 Virtual address of the initial RAM disk. The following constraint
62 Physical start address of the first bank of RAM.
65 Virtual start address of the first bank of RAM. During the kernel
101 last virtual RAM address (found using variable high_memory).
105 between virtual RAM and the vmalloc area. We do this to allow
113 `pram` specifies the physical start address of RAM. Must always
|
| H A D | booting.rst | 19 1. Setup and initialise the RAM.
27 1. Setup and initialise RAM
35 The boot loader is expected to find and initialise all RAM that the
38 to automatically locate and size all RAM, or it may use knowledge of
39 the RAM in the machine, or any other method the boot loader designer
120 The tagged list should be stored in system RAM.
124 it. The recommended placement is in the first 16KiB of RAM.
158 be loaded just above the 128MiB boundary from the start of RAM as
174 The zImage may also be placed in system RAM and called there. The
194 - r2 = physical address of tagged list in system RAM, or
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/cache/ |
| H A D | baikal,bt1-l2-ctl.yaml | 16 to change the Tag, Data and Way-select RAM access latencies. Baikal-T1
29 description: Cycles of latency for Way-select RAM accesses
36 description: Cycles of latency for Tag RAM accesses
43 description: Cycles of latency for Data RAM accesses
|
| /openbmc/qemu/docs/ |
| H A D | memory-hotplug.txt | 9 Basic RAM hotplug
21 - "megs" is the startup RAM. It is the RAM the guest will boot with
23 - "maxmem" is the maximum RAM size the guest can have
50 Besides basic RAM hotplug, QEMU also supports using files as a memory
66 comes from regular RAM, 1GB is a 1GB hugepage page and 256MB is from
77 RAM hot-unplug
|
| /openbmc/u-boot/arch/mips/mach-mt7620/ |
| H A D | Kconfig | 30 Gardena Smart Gateway boards have a MT7688 SoC with 128 MiB of RAM
38 Seeed LinkIt Smart 7688 boards have a MT7688 SoC with 128 MiB of RAM
50 bool "RAM boot"
53 This builds an image that is linked to a RAM address. It can be used
55 booted from RAM by other bootloaders using a BIN image.
|