[U-Boot] [PATCH 1/1] zynq: Kconfig: extend the bootstrap malloc() pool

[Anton Gerasimov]

Hi Michal,

> I understand all of this but will be good to know what consumes that
> 0x5xx space and if we mark nodes properly that maybe something is not
> used and we should remove that marking.
>
> It means expected data is that uarts consumes 0xXXX, axi 0xXXX, sd
> 0xXXX, etc.

measuring only the memory consumed in device_bind_common, I've got
the following results (in decimal):

   root_driver:               108
   mod_exp_sw:                108
   amba:                      120
   serial at e0000000 aka uart0: 112
   serial at e0001000 aka uart1: 88
   spi at e000d000 aka qspi:     120
   sdhci at e0100000 aka mmc0:   455
   sdhci at e0100000.blk:        208
   slcr at f8000000:             96
   clkc at 100:                  72
   (total)                    1487 = 0x5cf of 0x600

So the most memory is being consumed by mmc0 (not quite sure what is
this '.blk' device, but it is probably also required), but it's not
dominating, other seemingly useful devices also have a decent share.

Thanks,
Anton