blob: ca3cb7f63ed51ea4332b68f2ada43b8e0298c358 [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
James Morrisseyeaaeece2013-11-01 13:56:59 +000027* Build products are now created in a separate build directory tree.
28
Harry Liebelcff4e292013-11-05 18:00:38 +000029
Achin Gupta4f6ad662013-10-25 09:08:21 +010030ARM Trusted Firmware - version 0.2
31==================================
32
33New features
34------------
35
36* First source release.
37
38* Code for the PSCI suspend feature is supplied, although this is not enabled
39 by default since there are known issues (see below).
40
41
42Issues resolved since last release
43----------------------------------
44
45* The "psci" nodes in the FDTs provided in this release now fully comply
46 with the recommendations made in the PSCI specification.
47
48
49Known issues
50------------
51
52The following is a list of issues which are expected to be fixed in the future
53releases of the ARM Trusted Firmware.
54
55* The TrustZone Address Space Controller (TZC-400) is not being programmed
56 yet. Use of model parameter `-C bp.secure_memory=1` is not supported.
57
58* No support yet for secure world interrupt handling or for switching context
59 between secure and normal worlds in EL3.
60
61* GICv3 support is experimental. The Linux kernel patches to support this are
62 not widely available. There are known issues with GICv3 initialization in
63 the ARM Trusted Firmware.
64
65* Dynamic image loading is not available yet. The current image loader
66 implementation (used to load BL2 and all subsequent images) has some
67 limitations. Changing BL2 or BL3-1 load addresses in certain ways can lead
68 to loading errors, even if the images should theoretically fit in memory.
69
70* Although support for PSCI `CPU_SUSPEND` is present, it is not yet stable
71 and ready for use.
72
James Morrisseyba3155b2013-10-29 10:56:46 +000073* PSCI API calls `AFFINITY_INFO` & `PSCI_VERSION` are implemented but have not
Achin Gupta4f6ad662013-10-25 09:08:21 +010074 been tested.
75
76* The ARM Trusted Firmware make files result in all build artifacts being
77 placed in the root of the project. These should be placed in appropriate
78 sub-directories.
79
80* The compilation of ARM Trusted Firmware is not free from compilation
81 warnings. Some of these warnings have not been investigated yet so they
82 could mask real bugs.
83
84* The ARM Trusted Firmware currently uses toolchain/system include files like
85 stdio.h. It should provide versions of these within the project to maintain
86 compatibility between toolchains/systems.
87
88* The PSCI code takes some locks in an incorrect sequence. This may cause
89 problems with suspend and hotplug in certain conditions.
90
91* The Linux kernel used in this release is based on version 3.12-rc4. Using
92 this kernel with the ARM Trusted Firmware fails to start the file-system as
93 a RAM-disk. It fails to execute user-space `init` from the RAM-disk. As an
94 alternative, the VirtioBlock mechanism can be used to provide a file-system
95 to the kernel.
96
97
98Detailed changes since last release
99-----------------------------------
100
101First source release not applicable.
102
103- - - - - - - - - - - - - - - - - - - - - - - - - -
104
105_Copyright (c) 2013 ARM Ltd. All rights reserved._