Hi Raymond,
Isn't it also worth to check if existing CONTROL_FDT has enough space inside
that new overlay can fit there before resizing it?
By default each entry only contains the actual size since bloblist
(aka transfer list) is designed as a compact data structure and there
should not be a waiver for CONTROL_FDT to carry additional spare
spaces.
Right but you can build dtb via dtc -S/-p to add additional padding. It means
dtb will be bigger which goes to TL and should be possible to fit overlay there.
Yes, a developer knows exactly how big the merged DT should be...but
it is only DT specific and not a common case for applying other blob
data.
Maybe I can add a DT Kconfig for skipping resizing for the use case
you mentioned if all reviewers agree.
What I am saying is free space calculation should start with looking at free
space in base DTB. If it is enough (with pad) do nothing. If there is not enough
space then call your code.
Thanks,
Michal
