xref: /rk3399_ARM-atf/docs/change-log.md (revision dc98e5370ac81965ebcc322a279b8aad51258d9a)
1ARM Trusted Firmware
2====================
3
4Detailed changes since last release
5-----------------------------------
6
7*   Support for Foundation FVP Version 2.0 added.
8    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.
11    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.
17
18*   Fixed various GCC compiler warnings.
19
20*   Unmask SError and Debug exceptions in the trusted firmware.
21    Also route external abort and SError interrupts to EL3.
22
23*   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
27*   Build products are now created in a separate build directory tree.
28
29*   Analyze at link-time whether bootloader images will fit in memory and won't
30    overlap each other at run time. If it is not the case then image linking
31    will now fail.
32
33*   Reduce the size of the bootloader images by cutting some sections out of
34    their disk images and allocating them at load time, whenever possible.
35
36*   Properly initialise the C runtime environment. C code can now safely assume
37    that global variables are initialised to 0 and that initialised data holds
38    the correct value.
39
40*   General changes on the memory layout: some sections have been moved, some of
41    them have been merged together, and some alignment constraints on sections
42    have changed.
43
44*   Enable third party contributions. Add a new contributing.md containing
45    instructions for how to contribute and update copyright text in all files to
46    acknowledge contributors.
47
48*   The wake up enable bit in the FVP power controller is cleared when a cpu is
49    physically powered up to prevent a spurious wake up from a subsequent cpu
50    off state.
51
52*   Definitions of some constants related to the PSCI api calls AFFINITY_INFO
53    and CPU_SUSPEND have been corrected.
54
55*   A bug which triggered an error condition in the code executed after a cpu
56    is powered on, if a non zero context id parameter was passed in the PSCI
57    CPU_ON and CPU_SUSPEND api calls has been corrected.
58
59*   A restriction in the FVP code which did not allow the non-secure entrypoint
60    to lie outside the DRAM has been removed.
61
62*   The PSCI CPU_SUSPEND api has been stabilised to an extent where it can be
63    used for entry into power down states with the following restrictions:
64    -   Entry into standby states is not supported.
65    -   The api is only supported on the AEMv8 Base FVP.
66
67
68*   The PSCI AFFINITY_INFO api has undergone limited testing on the AEMv8 Base
69    FVP to allow experimental use.
70
71*   Locks corresponding to each affinity level are acquired and released in
72    the correct sequence in the PSCI implementation. Invocation of the PSCI
73    CPU_SUSPEND and CPU_OFF apis simultaneously across cpus & clusters should
74    not result in unexpected behaviour.
75
76ARM Trusted Firmware - version 0.2
77==================================
78
79New features
80------------
81
82*   First source release.
83
84*   Code for the PSCI suspend feature is supplied, although this is not enabled
85    by default since there are known issues (see below).
86
87
88Issues resolved since last release
89----------------------------------
90
91*   The "psci" nodes in the FDTs provided in this release now fully comply
92    with the recommendations made in the PSCI specification.
93
94
95Known issues
96------------
97
98The following is a list of issues which are expected to be fixed in the future
99releases of the ARM Trusted Firmware.
100
101*   The TrustZone Address Space Controller (TZC-400) is not being programmed
102    yet. Use of model parameter `-C bp.secure_memory=1` is not supported.
103
104*   No support yet for secure world interrupt handling or for switching context
105    between secure and normal worlds in EL3.
106
107*   GICv3 support is experimental. The Linux kernel patches to support this are
108    not widely available. There are known issues with GICv3 initialization in
109    the ARM Trusted Firmware.
110
111*   Dynamic image loading is not available yet. The current image loader
112    implementation (used to load BL2 and all subsequent images) has some
113    limitations. Changing BL2 or BL3-1 load addresses in certain ways can lead
114    to loading errors, even if the images should theoretically fit in memory.
115
116*   Although support for PSCI `CPU_SUSPEND` is present, it is not yet stable
117    and ready for use.
118
119*   PSCI API calls `AFFINITY_INFO` & `PSCI_VERSION` are implemented but have not
120    been tested.
121
122*   The ARM Trusted Firmware make files result in all build artifacts being
123    placed in the root of the project. These should be placed in appropriate
124    sub-directories.
125
126*   The compilation of ARM Trusted Firmware is not free from compilation
127    warnings. Some of these warnings have not been investigated yet so they
128    could mask real bugs.
129
130*   The ARM Trusted Firmware currently uses toolchain/system include files like
131    stdio.h. It should provide versions of these within the project to maintain
132    compatibility between toolchains/systems.
133
134*   The PSCI code takes some locks in an incorrect sequence. This may cause
135    problems with suspend and hotplug in certain conditions.
136
137*   The Linux kernel used in this release is based on version 3.12-rc4. Using
138    this kernel with the ARM Trusted Firmware fails to start the file-system as
139    a RAM-disk. It fails to execute user-space `init` from the RAM-disk. As an
140    alternative, the VirtioBlock mechanism can be used to provide a file-system
141    to the kernel.
142
143
144Detailed changes since last release
145-----------------------------------
146
147First source release - not applicable.
148
149- - - - - - - - - - - - - - - - - - - - - - - - - -
150
151_Copyright (c) 2013, ARM Limited and Contributors. All rights reserved._
152