diff options
| author | Jiong Wang <jiong.wang@foss.arm.com> | 2016-03-24 17:32:04 +0300 |
|---|---|---|
| committer | Corinna Vinschen <corinna@vinschen.de> | 2016-03-26 14:45:07 +0300 |
| commit | 18b47e05d3a971656ebb2306c205d0a6b36e6b91 (patch) | |
| tree | 35a622c6b818e7d48c64159bf3b2af2d25358f1d /newlib/libc | |
| parent | 4799377456ff1c702dc6cb71505c0d90bb204ed4 (diff) | |
Initializing TTBR0 to inner/outer WB
While running tests on internal systems, we identified an issue in the
startup code for newlib on AArch32 systems with Multiprocessor
Extensions to the architecture.
The issue is we were configuring page table flags to be Inner
cacheable/Outer non-cacheable, while for at least architectures with
Multiprocessor Extension, we'd configure it to Inner/Outer write-back, no
write-allocate, and cacheable.
The attached patch fixes this, and no regression on arm-none-eabi
bare-metal tests.
Adopted suggestion given by Richard offline to avoid using jump.
libgloss/
* arm/cpu-init/rdimon-aem.S: Set TTBR0 to inner/outer
cacheable WB, and no allocate on WB for arch with multiprocessor
extension.
Diffstat (limited to 'newlib/libc')
0 files changed, 0 insertions, 0 deletions