diff options
author | Rafał Miłecki <rafal@milecki.pl> | 2016-07-22 17:26:33 +0200 |
---|---|---|
committer | Rafał Miłecki <rafal@milecki.pl> | 2016-08-19 11:38:44 +0200 |
commit | 5e885c09c625c22d2995d477ef6cc8ee7595a817 (patch) | |
tree | c8efeb4bfa4ab69745d6b21c9357fe01de9a4719 /target/linux/x86/base-files | |
parent | d22ae5e888f4905ba843670181587bf201e1b14d (diff) | |
download | upstream-5e885c09c625c22d2995d477ef6cc8ee7595a817.tar.gz upstream-5e885c09c625c22d2995d477ef6cc8ee7595a817.tar.bz2 upstream-5e885c09c625c22d2995d477ef6cc8ee7595a817.zip |
bcm53xx: switch back to standalone ASM entry flushing cache
Over a year ago in a commit ac96a1665ac7 ("bcm53xx: update Disable MMU
and Dcache during decompression") we switched to Florian's patch for
workarounding CFE bug. The main difference was using a part of existing
__armv7_mmu_cache_flush instead of implementing flushing separately.
This worked well for Northstar devices but doesn't work for BCM53573 as
these devices simply don't start booting with Florian's patch. It's
because of the ldmfd ASM instruction in the __armv7_mmu_cache_flush.
So this commit switches back to using standalone implementation. This
time instead of copying Broadcom's copy of cache-v7.S, we just make a
copy of the original file on our own. Unfortunately we can't cross-dir
compile cache-v7.S from ../../mm/ as that one also adds __INITDATA with
define_cache_functions v7 which would just trigger
> Error: unrecognized/unsupported machine ID (r1 = 0x0000007f).
The only real change Broadcom did in copied .S file was modifying mcr
instruction to use c6 instead of c14. It isn't clear to me if we really
need it, but let's use it for now.
By the way we also update commit message of the
[PATCH] ARM: BCM5301X: Disable MMU and Dcache during decompression
This makes kernel booting on BCM53573 successfully.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Diffstat (limited to 'target/linux/x86/base-files')
0 files changed, 0 insertions, 0 deletions