| /OK3568_Linux_fs/kernel/drivers/zorro/ |
| H A D | zorro.ids | 18 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 …]
|
| /OK3568_Linux_fs/u-boot/drivers/ram/ |
| H A D | Kconfig | 1 config RAM config
2 bool "Enable RAM drivers using Driver Model"
5 This allows drivers to be provided for SDRAM and other RAM
7 tree. Generally some parameters are required to set up the RAM and
8 the RAM size can either be statically defined or dynamically
12 bool "Enable RAM support in SPL"
13 depends on RAM && SPL_DM
15 The RAM subsystem adds a small amount of overhead to the image.
16 If this is acceptable and you have a need to use RAM drivers in
18 setting up RAM (e.g. SDRAM / DDR) within SPL.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/translations/zh_CN/arm/ |
| H A D | Booting | 40 1、设置和初始化 RAM。
47 1、设置和初始化 RAM
53 引导装载程序应该找到并初始化系统中所有内核用于保持系统变量数据的 RAM。
55 RAM，或可能使用对这个设备已知的 RAM 信息，还可能使用任何引导装载程序
117 标签列表应该保存在系统的 RAM 中。
120 建议放在 RAM 的头 16KiB 中。
126 RAM 中，并用启动数据初始化它。dtb 格式在文档
132 dtb 必须置于内核自解压不会覆盖的内存区。建议将其放置于 RAM 的头 16KiB
146 zImage 也可以被放在系统 RAM（任意位置）中被调用。注意：内核使用映像
147 基地址的前 16KB RAM 空间来保存页表。建议将映像置于 RAM 的 32KB 处。
[all …]
|
| /OK3568_Linux_fs/kernel/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
16 The RAM disk driver is a way to use main system memory as a block device. It
22 The RAM disk dynamically grows as more space is required. It does this by using
23 RAM from the buffer cache. The driver marks the buffers it is using as dirty
26 The RAM disk supports up to 16 RAM disks by default, and can be reconfigured
27 to support an unlimited number of RAM disks (at your own risk). Just change
31 To use RAM disk support with your system, run './MAKEDEV ram' from the /dev
32 directory. RAM disks are all major number 1, and start with minor number 0
35 The new RAM disk also has the ability to load compressed RAM disk images,
[all …]
|
| /OK3568_Linux_fs/u-boot/board/keymile/km_arm/ |
| H A D | kwbimage_128M16_1.cfg | 62 DATA 0xFFD20134 0x66666666 # L2 RAM Timing 0 Register
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
[all …]
|
| H A D | kwbimage_256M8_1.cfg | 64 DATA 0xFFD20134 0x66666666 # L2 RAM Timing 0 Register
65 # bit 0-1: 2, Tag RAM RTC RAM0
66 # bit 3-2: 1, Tag RAM WTC RAM0
68 # bit 9-8: 2, Valid RAM RTC RAM
69 # bit 11-10: 1, Valid RAM WTC RAM
70 # bit 13-12: 2, Dirty RAM RTC RAM
71 # bit 15-14: 1, Dirty RAM WTC RAM
72 # bit 17-16: 2, Data RAM RTC RAM0
73 # bit 19-18: 1, Data RAM WTC RAM0
74 # bit 21-20: 2, Data RAM RTC RAM1
[all …]
|
| /OK3568_Linux_fs/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 …]
|
| /OK3568_Linux_fs/u-boot/arch/mips/mach-bmips/ |
| H A D | Kconfig | 92 Comtrend AR-5387un boards have a BCM6328 SoC with 64 MB of RAM and 16
103 Comtrend CT-5361 boards have a BCM6348 SoC with 16 MB of RAM and 4 MB
114 Comtrend VR-3032u boards have a BCM63268 SoC with 64 MB of RAM and
125 Huawei EchoLife HG556a boards have a BCM6358 SoC with 64 MB of RAM
136 Netgear CG3100D boards have a BCM3380 SoC with 64 MB of RAM and 8 MB
147 Sagem F@ST1704 boards have a BCM6338 SoC with 16 MB of RAM and 4 MB
158 SFR NeufBox 4 (Sercomm) boards have a BCM6358 SoC with 32 MB of RAM
170 bool "RAM boot"
173 This builds an image that is linked to a RAM address. It can be used
175 booted from RAM by other bootloaders using a BIN image.
|
| /OK3568_Linux_fs/kernel/Documentation/translations/zh_CN/arm64/ |
| H A D | booting.txt | 47 1、设置和初始化 RAM
53 1、设置和初始化 RAM
58 引导装载程序应该找到并初始化系统中所有内核用于保持系统变量数据的 RAM。
60 RAM，或可能使用对这个设备已知的 RAM 信息，还可能是引导装载程序设计者
154 x0 = 系统 RAM 中设备树数据块（dtb）的物理地址。
|
| /OK3568_Linux_fs/kernel/Documentation/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.
142 A safe location is just above the 128MiB boundary from start 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
[all …]
|
| H 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");
|
| /OK3568_Linux_fs/kernel/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
|
| H 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
|
| /OK3568_Linux_fs/u-boot/board/coreboot/coreboot/ |
| H A D | Kconfig | 43 hex "Board specific Cache-As-RAM (CAR) address"
46 This option specifies the board specific Cache-As-RAM (CAR) address.
49 hex "Board specific Cache-As-RAM (CAR) size"
52 This option specifies the board specific Cache-As-RAM (CAR) size.
|
| /OK3568_Linux_fs/kernel/Documentation/vm/ |
| H A D | frontswap.rst | 9 swapped pages are saved in RAM (or a RAM-like device) instead of a swap disk.
21 a synchronous concurrency-safe page-oriented "pseudo-RAM device" conforming
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
88 useful for write-balancing for some RAM-like devices). Swap pages (and
89 evicted page-cache pages) are a great use for this kind of slower-than-RAM-
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
[all …]
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.ramboot-ppc85xx | 15 1. Load the RAM based bootloader onto DDR via JTAG/BDI interface. And then
22 2. Load the RAM based bootloader onto DDR using already existing bootloader on
32 support for example AMP boot. In this case also RAM boot loader can be
36 RAM based bootloader can offer an updated bootloader on the system.
45 - In case of the pure RAM based bootloaders we have to do it by JTAG manually or already existing b…
55 Load the RAM based boot loader to the proper location in DDR/L2SRAM.
61 execute the RAM based bootloader.
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H 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
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 …]
|
| H 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.
|
| /OK3568_Linux_fs/kernel/Documentation/arm/keystone/ |
| H 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,
|
| /OK3568_Linux_fs/kernel/arch/m68k/ |
| H A D | Kconfig.machine | 338 comment "RAM configuration"
341 hex "Address of the base of RAM"
344 Define the address that RAM starts at. On many platforms this is
346 platforms choose to setup their RAM at other addresses within the
350 hex "Size of RAM (in bytes), or 0 for automatic"
353 Define the size of the system RAM. If you select 0 then the
354 kernel will try to probe the RAM size at runtime. This is not
362 put at the start of RAM, but it doesn't have to be. On ColdFire
393 of RAM, but usually some small offset from it. Define the start
395 processor vectors at the base of RAM and then the start of the
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/soc/qcom/ |
| H A D | qcom,aoss-qmp.txt | 6 SoC has it's own block of message RAM and IRQ for communication with the AOSS.
7 The protocol used to communicate in the message RAM is known as Qualcomm
27 Definition: the base address and size of the message RAM for this
67 The following example represents the AOSS side-channel message RAM and the
|
| /OK3568_Linux_fs/buildroot/fs/cpio/ |
| H A D | Config.in | 2 bool "cpio the root filesystem (for use as an initial RAM filesystem)"
5 used for an initial RAM filesystem that is passed to the
15 If you use the cpio archive as an initial RAM filesystem, make
|
| /OK3568_Linux_fs/u-boot/board/imgtec/xilfpga/ |
| H A D | README | 20 - 128Mbyte DDR RAM at 0x0000_0000
21 - 8Kbyte RAM at 0x1000_0000
34 The BootRAM is a writeable "RAM" in FPGA at 0x1FC0_0000.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/soc/ti/ |
| H 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.
|