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