Home
last modified time | relevance | path

Searched refs:RAM (Results 1 – 25 of 228) sorted by relevance

12345678910

/linux-3.4.99/drivers/zorro/
Dzorro.ids18 0000 Golem RAM Box 2MB [RAM Expansion]
22 1300 Warp Engine [Accelerator, SCSI Host Adapter and RAM Expansion]
24 0200 Megamix 2000 [RAM Expansion]
36 0a00 A590/A2052/A2058/A2091 [RAM Expansion]
37 2000 A560 [RAM Expansion]
40 5000 A2620 68020 [Accelerator and RAM Expansion]
41 5100 A2630 68030 [Accelerator and RAM Expansion]
51 0200 EXP8000 [RAM Expansion]
64 0100 AX2000 [RAM Expansion]
68 0000 StarBoard II [RAM Expansion]
[all …]
/linux-3.4.99/Documentation/blockdev/
Dramdisk.txt1 Using the RAM disk block device with Linux
9 4) An Example of Creating a Compressed RAM Disk
15 The RAM disk driver is a way to use main system memory as a block device. It
21 The RAM disk dynamically grows as more space is required. It does this by using
22 RAM from the buffer cache. The driver marks the buffers it is using as dirty
25 The RAM disk supports up to 16 RAM disks by default, and can be reconfigured
26 to support an unlimited number of RAM disks (at your own risk). Just change
30 To use RAM disk support with your system, run './MAKEDEV ram' from the /dev
31 directory. RAM disks are all major number 1, and start with minor number 0
34 The new RAM disk also has the ability to load compressed RAM disk images,
[all …]
/linux-3.4.99/drivers/staging/ramster/
DKconfig2 bool "Cross-machine RAM capacity sharing, aka peer-to-peer tmem"
8 RAMster allows RAM on other machines in a cluster to be utilized
11 while minimizing total RAM across the cluster. RAMster, like
12 zcache, compresses swap pages into local RAM, but then remotifies
/linux-3.4.99/Documentation/arm/
DBooting17 1. Setup and initialise the RAM.
24 1. Setup and initialise RAM
30 The boot loader is expected to find and initialise all RAM that the
33 to automatically locate and size all RAM, or it may use knowledge of
34 the RAM in the machine, or any other method the boot loader designer
104 The tagged list should be stored in system RAM.
108 it. The recommended placement is in the first 16KiB of RAM.
123 overwrite it. The recommended placement is in the first 16KiB of RAM
139 The zImage may also be placed in system RAM (at any location) and
140 called there. Note that the kernel uses 16K of RAM below the image
[all …]
DPorting21 to be located in RAM, it can be in flash or other read-only or
26 This must be pointing at RAM. The decompressor will zero initialise
39 Physical address to place the initial RAM disk. Only relevant if
44 Virtual address of the initial RAM disk. The following constraint
58 Physical start address of the first bank of RAM.
61 Virtual start address of the first bank of RAM. During the kernel
98 last virtual RAM address (found using variable high_memory).
102 between virtual RAM and the vmalloc area. We do this to allow
110 `pram' specifies the physical start address of RAM. Must always
Dtcm.txt6 This is usually just a few (4-64) KiB of RAM inside the ARM
30 place you put it, it will mask any underlying RAM from the
31 CPU so it is usually wise not to overlap any physical RAM with
53 - Idle loops where all external RAM is set to self-refresh
54 retention mode, so only on-chip RAM is accessible by
59 the external RAM controller.
70 - Have the remaining TCM RAM added to a special
132 printk("Hello TCM executed from ITCM RAM\n");
Dmemory.txt63 PAGE_OFFSET high_memory-1 Kernel direct-mapped RAM region.
64 This maps the platforms RAM, and typically
65 maps all platform RAM in a 1:1 relationship.
/linux-3.4.99/drivers/staging/zram/
DKconfig2 tristate "Compressed RAM block device support"
23 bool "Compressed RAM block device debug support"
28 RAM block device driver.
Dzram.txt1 zram: Compressed RAM based block devices
8 The zram module creates RAM based block devices named /dev/zram<id>
29 of RAM is used.
/linux-3.4.99/drivers/staging/zcache/
DKconfig10 Zcache doubles RAM efficiency while providing a significant
13 memory to store clean page cache pages and swap in RAM,
/linux-3.4.99/Documentation/
Dinitrd.txt1 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
58 Loads the specified file as the initial RAM disk. When using LILO, you
59 have to specify the RAM disk image file in /etc/lilo.conf, using the
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
[all …]
/linux-3.4.99/Documentation/devicetree/bindings/arm/
Dl2cc.txt20 - arm,data-latency : Cycles of latency for Data RAM accesses. Specifies 3 cells of
23 - arm,tag-latency : Cycles of latency for Tag RAM accesses. Specifies 3 cells of
25 should use 0. Controllers without separate read and write Tag RAM latency
/linux-3.4.99/arch/m68k/
DKconfig.machine452 comment "RAM configuration"
455 hex "Address of the base of RAM"
458 Define the address that RAM starts at. On many platforms this is
460 platforms choose to setup their RAM at other addresses within the
464 hex "Size of RAM (in bytes), or 0 for automatic"
467 Define the size of the system RAM. If you select 0 then the
468 kernel will try to probe the RAM size at runtime. This is not
476 put at the start of RAM, but it doesn't have to be. On ColdFire
507 of RAM, but usually some small offset from it. Define the start
509 processor vectors at the base of RAM and then the start of the
[all …]
/linux-3.4.99/Documentation/filesystems/
Dtmpfs.txt14 you gain swapping and limit checking. Another similar thing is the RAM
16 RAM, where you have to create an ordinary filesystem on top. Ramdisks
22 RAM+swap use of a tmpfs instance with df(1) and du(1).
60 default is half of your physical RAM without swap. If you
65 is half of the number of your physical RAM pages, or (on a
66 machine with highmem) the number of lowmem RAM pages,
71 to limit this tmpfs instance to that percentage of your physical RAM:
140 RAM/SWAP in 10240 inodes and it is only accessible by root.
/linux-3.4.99/Documentation/sound/oss/
DREADME.modules80 DMA buffers for ISA cards on machines with more than 16MB RAM. This is
88 wasteful of RAM, but it guarantees that sound always works.
96 If you have 16MB or less RAM or a PCI sound card, this is wasteful and
97 unnecessary. It is possible that machine with 16MB or less RAM will find
99 cannot find a 64K block free, you will be wasting even more RAM by keeping
101 needed. The proper solution is to upgrade your RAM. But you do also have
/linux-3.4.99/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dcpm.txt34 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.
/linux-3.4.99/drivers/video/console/
DKconfig23 bool "Enable Scrollback Buffer in System RAM"
28 the VGA RAM. The size of this RAM is fixed and is quite small.
30 System RAM which is dynamically allocated during initialization.
31 Placing the scrollback buffer in System RAM will slightly slow
35 RAM to allocate for this buffer. If unsure, say 'N'.
43 Enter the amount of System RAM to allocate for the scrollback
/linux-3.4.99/arch/arm/mm/
Dproc-arm740.S79 ldr r0, =(CONFIG_DRAM_BASE & 0xFFFFF000) @ base[31:12] of RAM
80 ldr r1, =(CONFIG_DRAM_SIZE >> 12) @ size of RAM (must be >= 4KB)
87 mcr p15, 0, r0, c6, c1 @ set area 1, RAM
/linux-3.4.99/Documentation/vm/
Dcleancache.txt105 saved in transcendent memory (RAM that is otherwise not directly
111 fast kernel-directly-addressable RAM and slower DMA/asynchronous devices.
115 balancing for some RAM-like devices). Evicted page-cache pages (and
116 swap pages) are a great use for this kind of slower-than-RAM-but-much-
123 virtual machines. This is really hard to do with RAM and efforts to
127 of flexibility for more dynamic, flexible RAM multiplexing.
129 "fallow" hypervisor-owned RAM to not only be "time-shared" between multiple
131 optimize RAM utilization. And when guest OS's are induced to surrender
132 underutilized RAM (e.g. with "self-ballooning"), page cache pages
139 the proposed "RAMster" driver shares RAM across multiple physical
[all …]
/linux-3.4.99/Documentation/networking/
Diphase.txt80 The (i)Chip boards have 3 different packet RAM size variants: 128K, 512K and
81 1M. The RAM size decides the number of buffers and buffer size. The default
84 Total Rx RAM Tx RAM Rx Buf Tx Buf Rx buf Tx buf
85 RAM size size size size size cnt cnt
/linux-3.4.99/arch/sh/include/mach-ecovec24/mach/
Dpartner-jet-setup.txt5 LIST "zImage (RAM boot)"
6 LIST "This script can be used to boot the kernel from RAM via JTAG:"
/linux-3.4.99/arch/frv/kernel/
Dhead-uc-fr451.S67 # need to tile the remaining IAMPR/DAMPR registers to cover as much of the RAM as possible
87 # GR8 = base of uncovered RAM
88 # GR9 = top of uncovered RAM
/linux-3.4.99/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/cpm/
Di2c.txt8 Parameter RAM itself, but the I2C_BASE field of the CPM2 Parameter RAM
/linux-3.4.99/arch/unicore32/configs/
Dunicore32_defconfig8 # Initial RAM filesystem and RAM disk (initramfs/initrd) support
81 # RAM/ROM/Flash chip drivers
/linux-3.4.99/arch/arm/mach-realview/
DKconfig101 RealView boards other than PB1176 have the RAM available at
103 the board supports 512MB of RAM, this option allows the
106 RAM to be used with SPARSEMEM.

12345678910