On 2025-03-05 14:33, Daniel Golle wrote:
On Wed, Mar 05, 2025 at 02:13:04PM +0100, Martin Schiller wrote:
CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY was disabled with commit
6b007d2512ad (treewide: disable spectre mitigation on unaffected Arm64
targets) for all targets in target/linux/mediatek/filogic folder, but
the Arm Cortex-A73 in the Filogic 880 are affected [0].
So should we enable CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY for this
subtarget again?
On the other hand, the target.mk in this subtarget folder states it is
CPU_TYPE:=cortex-a53, which is not correct for all the supported
systems
in this subtarget.
Do we have to split this subtarget into filogic830, filogic880, etc.?
Imho it would make most sense to merge all the A53 subtargets, ie. no
longer treat MT7622 separately. Afaik there is no real reason to do
this.
Then we can have a new A73 subtarget for MT7988 (and potentially other
future SoC).
OK, so maybe we should name the subtargets like it is done for the mvebu
or sunxi target. (cortexa<X>)
Regards,
Martin
[0]
https://developer.arm.com/Arm%20Security%20Center/Speculative%20Processor%20Vulnerability
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
