On 17.03.2019, at 15:12, Simon Glass sjg@chromium.org wrote:
Well, my thinking is that GD is actually a set of pointers, with the actual data stored elsewhere. The nice thing about bloblist is that it is a contiguous block of a set size, which holds data used by different parts of U-Boot (e.g. could be drivers, arch-specific code, vboot, features like android boot, EFI, etc.). Some of the pointers in GD could move to bloblist, like bootstage as already discussed.
But if you want one solution, then it has to be GD I think. Perhaps we can defer this until the GD work is done and we have a few more users?
For some RK33xx devices, we inject the original boot-location into the FDT passed to the full U-Boot stage. While this requires FIT in SPL (and may thus not be generally applicable), it is one convenient way for such use-cases today.
Thanks, Philipp.