Like I said: blobs in EL3, the highest privilege level.
We've been getting these "almost there" announcements quarterly for multiple years at this point.
We've been getting these "almost there" announcements quarterly for multiple years at this point.
OSS TF-A at EL3 + OSS DDR training (RK3399)
OSS TF-A at EL3 + closed DDR training (RK3588)
OSS uboot + closed TF-A
closed uboot + closed TF-A
Those who don't need the features of RK3588 can use the older and fully open RK3399.
That should be "blob which does stuff, including DDR training, at EL3".
That blob certainly does DDR training. Maybe it does other stuff. But all of it is done at EL3.
> In decreasing order of preference
"Warning! Diagram is not drawn to scale."
If someone wants to find out, they can load it in IDA/Ghidra?
Looks like Collabora is already monitoring the blob, so it's not entirely a mystery:
At the moment of writing this article, we have identified a few differences from the binary blob previously used, which we can highlight as following:
Binary BL31 contains some unknown code to get HDMI-RX PHY access working.
The cpufreq support in binary BL31 is different from TF-A.
There could be more issues that are unknown at the moment and users should be aware of it.Project Ortega did it to an entire gigabit ethernet controller for the princely sum of zero dollars:
https://media.ccc.de/v/37c3-11781-adventures_in_reverse_engi...
https://wiki.raptorcs.com/wiki/Project_Ortega
> Binary BL31 contains some unknown code to get HDMI-RX PHY access working.
That doesn't sound like DDR training to me. Maybe now you see the problem?
It is absolutely a problem, but it's bounded by the ability to inspect and question code/behavior outside the officially claimed rationale. We can prefer open systems and also shine a bright light on the behavior of closed systems.