| /linux/drivers/zorro/ |
| 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 …]
|
| /linux/Documentation/translations/zh_CN/arm/ |
| 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 …]
|
| /linux/Documentation/admin-guide/blockdev/ |
| 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 …]
|
| /linux/Documentation/devicetree/bindings/net/can/ |
| A D | bosch,m_can.yaml | 21 - description: message RAM
52 Message RAM configuration data.
53 Multiple M_CAN instances can share the same Message RAM
55 in Message RAM is also configurable, so this property is
56 telling driver how the shared or private Message RAM are
61 The 'offset' is an address offset of the Message RAM where
63 0x0 if you're using a private Message RAM. The remain cells
75 Please refer to 2.4.1 Message RAM Configuration in Bosch
80 - description: The 'offset' is an address offset of the Message RAM where
82 you're using a private Message RAM.
|
| /linux/Documentation/translations/zh_CN/filesystems/ |
| 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个
|
| /linux/Documentation/translations/zh_TW/filesystems/ |
| 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個
|
| /linux/Documentation/translations/zh_CN/arm64/ |
| A D | booting.txt | 47 1、设置和初始化 RAM
53 1、设置和初始化 RAM
58 引导装载程序应该找到并初始化系统中所有内核用于保持系统变量数据的 RAM。
60 RAM，或可能使用对这个设备已知的 RAM 信息，还可能是引导装载程序设计者
154 x0 = 系统 RAM 中设备树数据块（dtb）的物理地址。
|
| /linux/Documentation/translations/zh_TW/arm64/ |
| A D | booting.txt | 51 1、設置和初始化 RAM
57 1、設置和初始化 RAM
62 引導裝載程序應該找到並初始化系統中所有內核用於保持系統變量數據的 RAM。
64 RAM，或可能使用對這個設備已知的 RAM 信息，還可能是引導裝載程序設計者
158 x0 = 系統 RAM 中設備樹數據塊（dtb）的物理地址。
|
| /linux/Documentation/arm/ |
| 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
|
| 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 …]
|
| A D | tcm.rst | 8 This is usually just a few (4-64) KiB of RAM inside the ARM
32 place you put it, it will mask any underlying RAM from the
33 CPU so it is usually wise not to overlap any physical RAM with
55 - Idle loops where all external RAM is set to self-refresh
56 retention mode, so only on-chip RAM is accessible by
61 the external RAM controller.
72 - Have the remaining TCM RAM added to a special
138 printk("Hello TCM executed from ITCM RAM\n");
|
| /linux/Documentation/ABI/testing/ |
| 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
|
| A D | sysfs-bus-coresight-devices-tmc | 5 Description: (RW) Disables write access to the Trace RAM by stopping the
14 Description: (Read) Defines the size, in 32-bit words, of the local RAM buffer.
28 Description: (Read) Shows the value held by the TMC RAM Read Pointer register
29 that is used to read entries from the Trace RAM over the APB
37 Description: (Read) Shows the value held by the TMC RAM Write Pointer register
39 the CoreSight bus into the Trace RAM. The value is read directly
|
| /linux/Documentation/devicetree/bindings/memory-controllers/ |
| 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
|
| /linux/Documentation/vm/ |
| A D | frontswap.rst | 9 swapped pages are saved in RAM (or a RAM-like device) instead of a swap disk.
23 in-kernel compressed memory, aka "zcache", or future RAM-like devices);
24 this pseudo-RAM device is not directly accessible or addressable by the
90 but-much-faster-than-disk "pseudo-RAM device" and the frontswap (and
95 provides a huge amount of flexibility for more dynamic, flexible RAM
100 that can be safely kept in RAM. Zcache essentially trades off CPU
108 as in zcache, but then "remotified" to another system's RAM. This
109 allows RAM to be dynamically load-balanced back-and-forth as needed,
114 how much of the RAM is available for each of the clients!
125 underutilized RAM (e.g. with "selfballooning"), sudden unexpected
[all …]
|
| A D | cleancache.rst | 122 saved in transcendent memory (RAM that is otherwise not directly
128 fast kernel-directly-addressable RAM and slower DMA/asynchronous devices.
132 balancing for some RAM-like devices). Evicted page-cache pages (and
133 swap pages) are a great use for this kind of slower-than-RAM-but-much-
140 virtual machines. This is really hard to do with RAM and efforts to
144 of flexibility for more dynamic, flexible RAM multiplexing.
148 optimize RAM utilization. And when guest OS's are induced to surrender
149 underutilized RAM (e.g. with "self-ballooning"), page cache pages
156 the proposed "RAMster" driver shares RAM across multiple physical
201 or for real kernel-addressable RAM, it makes perfect sense for
[all …]
|
| /linux/Documentation/admin-guide/ |
| A D | initrd.rst | 1 Using the initial RAM disk (initrd)
8 initrd provides the capability to load a RAM disk by the boot loader.
9 This RAM disk can then be mounted as the root file system and programs
27 1) the boot loader loads the kernel and the initial RAM disk
28 2) the kernel converts initrd into a "normal" RAM disk and
64 initrd data is preserved but it is not converted to a RAM disk and
77 with the RAM disk mounted as root.
117 Second, the kernel has to be compiled with RAM disk support and with
128 - a RAM disk (fast, but allocates physical memory)
220 - unmounting the initrd file system and de-allocating the RAM disk
[all …]
|
| A D | ramoops.rst | 11 Ramoops is an oops/panic logger that writes its logs to RAM before the system
13 needs a system with persistent RAM so that the content of that area can
54 to life (i.e. a watchdog triggered). In such cases, RAM may be somewhat
121 You can specify either RAM memory or peripheral devices' memory. However, when
122 specifying RAM, be sure to reserve the memory by issuing memblock_reserve()
140 a stored record from RAM, simply unlink the respective pstore file.
|
| /linux/Documentation/arm/keystone/ |
| A D | knav-qmss.rst | 12 processors(PDSP), linking RAM, descriptor pools and infrastructure
18 Linking RAM registers are used to link the descriptors which are stored in
19 descriptor RAM. Descriptor RAM is configurable as internal or external memory.
20 The QMSS driver manages the PDSP setups, linking RAM regions,
|
| /linux/arch/m68k/ |
| A D | Kconfig.machine | 351 comment "RAM configuration"
354 hex "Address of the base of RAM"
363 hex "Size of RAM (in bytes), or 0 for automatic"
366 Define the size of the system RAM. If you select 0 then the
367 kernel will try to probe the RAM size at runtime. This is not
375 put at the start of RAM, but it doesn't have to be. On ColdFire
406 of RAM, but usually some small offset from it. Define the start
408 processor vectors at the base of RAM and then the start of the
421 regions being copied out to RAM at startup.
463 bool "RAM"
[all …]
|
| /linux/Documentation/networking/devlink/ |
| A D | iosm.rst | 49 * - ``PSI RAM``
56 PSI RAM and EBL are the RAM images which are injected to the device when the
70 1) When modem is in Boot ROM stage, user can use below command to inject PSI RAM
112 device (RAM dump).
|
| /linux/Documentation/devicetree/bindings/soc/ti/ |
| A D | keystone-navigator-qmss.txt | 6 processors(PDSP), linking RAM, descriptor pools and infrastructure
12 Linking RAM registers are used to link the descriptors which are stored in
13 descriptor RAM. Descriptor RAM is configurable as internal or external memory.
14 The QMSS driver manages the PDSP setups, linking RAM regions,
38 - Queue status RAM.
109 - PDSP internal RAM region.
|
| /linux/arch/arm/mach-socfpga/ |
| A D | Kconfig | 24 bool "Suspend to RAM on SOCFPGA"
26 Select this if you want to enable Suspend-to-RAM on SOCFPGA
|
| /linux/Documentation/devicetree/bindings/mips/img/ |
| A D | xilfpga.txt | 20 - 128Mbyte DDR RAM at 0x0000_0000
21 - 8Kbyte RAM at 0x1000_0000
69 The BootRAM is a writeable "RAM" in FPGA at 0x1FC0_0000.
|
| /linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| A D | cpm.txt | 34 parameter RAM region (if it has one).
36 * Multi-User RAM (MURAM)
38 The multi-user/dual-ported RAM is expressed as a bus under the CPM node.
|