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