blob: ee9be7758836b8c72daf3a2bf273b3a4f42ebc7a [file] [log] [blame] [view]
James Morrisseyba3155b2013-10-29 10:56:46 +00001ARM Trusted Firmware
2====================
Harry Liebelcff4e292013-11-05 18:00:38 +00003
4Detailed changes since last release
5-----------------------------------
6
James Morrisseyba3155b2013-10-29 10:56:46 +00007* Support for Foundation FVP Version 2.0 added.
Harry Liebelcff4e292013-11-05 18:00:38 +00008 The documented UEFI configuration disables some devices that are unavailable
9 in the Foundation FVP, including MMC and CLCD. The resultant UEFI binary can
10 be used on the AEMv8 and Cortex-A57-A53 FVPs, as well as the Foundation FVP.
James Morrisseyba3155b2013-10-29 10:56:46 +000011 NOTE: The software will not work on Version 1.0 of the Foundation FVP.
12
13* Regression-checked against latest Base FVPs (Version 5.2).
14
15* The supplied FDTs expose the Interrupt Translation Service (ITS) available
16 in GICv3.
Harry Liebelcff4e292013-11-05 18:00:38 +000017
Sandrine Bailleux204aa032013-10-28 15:14:00 +000018* Fixed various GCC compiler warnings.
19
Sandrine Bailleux37382742013-11-18 17:26:59 +000020* Unmask SError and Debug exceptions in the trusted firmware.
21 Also route external abort and SError interrupts to EL3.
22
Harry Liebel375ae682013-11-18 16:05:21 +000023* The amount of physical RAM available to Linux as specified in the FDTs for
24 Base FVPs have been increased from 2GB to 4GB. This resolves the issue of
25 failing to start user-space when using a RAM-disk file-system.
26
Harry Liebelcff4e292013-11-05 18:00:38 +000027
Achin Gupta4f6ad662013-10-25 09:08:21 +010028ARM Trusted Firmware - version 0.2
29==================================
30
31New features
32------------
33
34* First source release.
35
36* Code for the PSCI suspend feature is supplied, although this is not enabled
37 by default since there are known issues (see below).
38
39
40Issues resolved since last release
41----------------------------------
42
43* The "psci" nodes in the FDTs provided in this release now fully comply
44 with the recommendations made in the PSCI specification.
45
46
47Known issues
48------------
49
50The following is a list of issues which are expected to be fixed in the future
51releases of the ARM Trusted Firmware.
52
53* The TrustZone Address Space Controller (TZC-400) is not being programmed
54 yet. Use of model parameter `-C bp.secure_memory=1` is not supported.
55
56* No support yet for secure world interrupt handling or for switching context
57 between secure and normal worlds in EL3.
58
59* GICv3 support is experimental. The Linux kernel patches to support this are
60 not widely available. There are known issues with GICv3 initialization in
61 the ARM Trusted Firmware.
62
63* Dynamic image loading is not available yet. The current image loader
64 implementation (used to load BL2 and all subsequent images) has some
65 limitations. Changing BL2 or BL3-1 load addresses in certain ways can lead
66 to loading errors, even if the images should theoretically fit in memory.
67
68* Although support for PSCI `CPU_SUSPEND` is present, it is not yet stable
69 and ready for use.
70
James Morrisseyba3155b2013-10-29 10:56:46 +000071* PSCI API calls `AFFINITY_INFO` & `PSCI_VERSION` are implemented but have not
Achin Gupta4f6ad662013-10-25 09:08:21 +010072 been tested.
73
74* The ARM Trusted Firmware make files result in all build artifacts being
75 placed in the root of the project. These should be placed in appropriate
76 sub-directories.
77
78* The compilation of ARM Trusted Firmware is not free from compilation
79 warnings. Some of these warnings have not been investigated yet so they
80 could mask real bugs.
81
82* The ARM Trusted Firmware currently uses toolchain/system include files like
83 stdio.h. It should provide versions of these within the project to maintain
84 compatibility between toolchains/systems.
85
86* The PSCI code takes some locks in an incorrect sequence. This may cause
87 problems with suspend and hotplug in certain conditions.
88
89* The Linux kernel used in this release is based on version 3.12-rc4. Using
90 this kernel with the ARM Trusted Firmware fails to start the file-system as
91 a RAM-disk. It fails to execute user-space `init` from the RAM-disk. As an
92 alternative, the VirtioBlock mechanism can be used to provide a file-system
93 to the kernel.
94
95
96Detailed changes since last release
97-----------------------------------
98
99First source release not applicable.
100
101- - - - - - - - - - - - - - - - - - - - - - - - - -
102
103_Copyright (c) 2013 ARM Ltd. All rights reserved._