On Wed, 15 Nov 2023 17:15:35 +0000 Leif Lindholm quic_llindhol@quicinc.com wrote:
Hi,
(I should remember to respond to this as well.)
Hi André,
On Mon, Nov 13, 2023 at 17:23:58 +0000, Andre Przywara wrote:
We need to change make_helpers/arch_features.mk to stop enabling mandatory features as "present, no need to check" (value '1') but to use runtime check (value '2') instead. This way any platform which contains CPU not
But using runtime checking *for flexible platforms* was the plan all along. We did the groundwork for the FVP, feature by feature, check commit 6503ff2910ae5ed for an example. For all flexible platforms, the idea is that the default architecture revision stays at v8.0 (to cover "-cpu cortex-a57", for instance), but all(?) features get promoted to a runtime check (=2). Check the current version of plat/arm/board/fvp/platform.mk.
Ah, that intended usage-pattern was not clear to me.
Yeah, sorry, I wanted to communicate this to people caring about the QEMU port, but this was somehow missed.
Would it be worth adding a sentence to the FEATURE_DETECTION section of build-options.rst?
Mmh, skimming over this makes me think this stanza deserves some rewrite anyway. I will try to send a patch after the release. But I am not sure this is the right place for the explanation, since FEATURE_DETECTION is only a loosely related debug feature, and you get the runtime detection when setting something to =2 regardless. Will try to address this.
Thanks, Andre
Thanks for explaining!
Regards,
Leif
The same problem hits the Arm FPGA, which is a very simple platform sporting the newest cores in development. Check commit b321c243423b93, which enabled all relevant features to do a runtime check.
So please just push a patch similar to that, and we should be good?
Cheers, Andre
yet fully developed can boot TF-A. Or platform where one firmware can boot different cpu models.
I am sorry that I bring it so late in release cycle but was unable to use computer for a development for some time.