- Large RAM-disks may have trouble starting with 2GB of memory.
- Increase from 2GB to 4GB in FDT.
Change-Id: I12c1b8e5db41114b88c69c48621cb21247a6a6a7
* Unmask SError and Debug exceptions in the trusted firmware.
Also route external abort and SError interrupts to EL3.
+* The amount of physical RAM available to Linux as specified in the FDTs for
+ Base FVPs have been increased from 2GB to 4GB. This resolves the issue of
+ failing to start user-space when using a RAM-disk file-system.
+
ARM Trusted Firmware - version 0.2
==================================
##### Prepare RAM-disk
-NOTE: The RAM-disk option does not currently work with the Linux kernel version
-described above; use the VirtioBlock method instead. For further information
-please see the "Known issues" section in the [Change Log].
-
To prepare a RAM-disk root file-system, do the following:
1. Download the file-system image:
memory@80000000 {
device_type = "memory";
- reg = <0x00000000 0x80000000 0 0x80000000>;
- /*
+ reg = <0x00000000 0x80000000 0 0x80000000>,
<0x00000008 0x80000000 0 0x80000000>;
- */
};
gic: interrupt-controller@2f000000 {
memory@80000000 {
device_type = "memory";
- reg = <0x00000000 0x80000000 0 0x80000000>;
- /*
+ reg = <0x00000000 0x80000000 0 0x80000000>,
<0x00000008 0x80000000 0 0x80000000>;
- */
};
gic: interrupt-controller@2c001000 {
memory@80000000 {
device_type = "memory";
- reg = <0x00000000 0x80000000 0 0x80000000>;
- /*
+ reg = <0x00000000 0x80000000 0 0x80000000>,
<0x00000008 0x80000000 0 0x80000000>;
- */
};
gic: interrupt-controller@2f000000 {