The architecture of recent 12-STABLE for RPi2 (32 bit) is armv7, rather than armv6 on 11-STABLE. This means that there is a chance that the same build can run also on RPi2 v1.2 equipped with the newer ARMv8 based BCM2837 SoC.
Actually, the build works almost perfectly on v1.2 board except one big issue, that only 1 CPU logical core is used/assigned to all processes and the remaining 3 cores are completely ignored, despite all 4 cores are listed in top, for example.
This doesn't happen on v1.1 board. The same microSD (just pulled out from v1.2 board) runs fine on v1.1 board. I can't see any significant differences between both boards in top, dmesg or sysctl output.
The OS is r341492, rpi-firmware is 1.20180619 or the GIT rev. 077fbe8 (as of 6th Dec. 2018) and u-boot is 2018.11.
Created attachment 200941 [details]
Created attachment 200942 [details]
Created attachment 200943 [details]
Created attachment 200944 [details]
Created attachment 200945 [details]
Created attachment 200946 [details]
That's weird that I've never seen that.
We would need to support the "brcm,bcm2836-smp" enable method to bring up the others cpus.
I have plan to work on enable methods (as we need psci for armv7 when booting in hyp mode) but I don't know when I will have time.
Reply to myself. This issue is likely relating to the following upstream bug,
and may be fixed in the following raspberrypi/firmware commit.
I'll give it a try in the near future.
Can you report if the fix mentioned fixed the issue?
As a point of interest this bug seems to also indicate similar behaviour
(In reply to Tom Jones from comment #9)
Sorry for my late reply.
12-STABLE as of 20200727 w/ u-boot-rpi2-2020.07 and the recent firmware (*), I can't reproduce the issue I mentioned earlier. All 4 cores are detected, enabled and used correctly.