Does anyone have any bright ideas on how to know what the BSS size of the kernel will be from a uImage. It seems we just hope and pray that u-boot doesn't load things (ramdisk, bd_t, device tree, etc).

Clearly the new uImage work should encompass this information, but I'm looking for ideas on how to possibly handle this with the existing format.

- k