UEFI for Pine64

[z4v4l]

But the links are mostly about enabling an easier way for the virtualization stuff. It's not the monitor in its entirety.

Are you sure? Have you checked the MVBAR setup code?

No, I am not sure. I just read the abstracts given in those links. there virtualization was emphasized heavily.
If it deals with the Monitor handler part of the architecture, I definitely need to check it. It's just too much to check out now.)

So you say, with Allwinner SoC's, any 3rd party developer can implement its own Monitor and give their users all Secure world stack? Sounds too cool to be a reality.

Just get your Pine64 board and you will see it yourself. I'm pretty sure that you will like this hardware.

I am waiting to get it indeed.)
My love to arm sbc's would not hurt much, if the Monitor implementation on them isn't possible. UEFI doesn't need it, all in all (it might use those "secret" barely implemented by the vendor SMC calls). I just wanted to figure out this question. Because what I have learnt before was indicating there is no easy way to install it by the third parties, especially community/enthusiasts etc, what you are saying is that there is an open source implementation of something that looks like the Monitor software.
But there is a chain of trust established if the Secure extension is present (it is), and it cannot be easy to insert yourself into it. So, how that software gets verified and becomes a part of the chain-of-trust? How does it get its way into a SoC? You need vendor's bless for that. And that is not an easy thing, because why should they bother, right? they may just reject saying that is not needed for them. I was asking similar question yet another arm soc vendor and got silence. ah, well I asked allwinner too. they didn't answer as well. well they are busy and I am just having fun, a logical outcome.)
I thought that PSCI reference implementation is for vendors.