Hello Alexander,
regarding your patch itself, please check indentation in Kconfig help.
Maybe run `ptxdist lint` before submitting, IIRC that problem is
checked by the linter. The indentation is strange there with tabs
first and two spaces then.
Thanks for the feedback, i'll keep it in mind with the next patch i'll
send in.
Interesting. So this env image does not stay standalone, but will be
integrated in some other packaging? I'm pretty sure U-Boot itself
does not care about those padding bytes at runtime. Maybe it's a
thing the flashing tool checks?
It doesn't stay standalone, no, it's bundled together with various other images
into a "full-firmware" image (i.e. env, SPL, FIT image, config) which then get's
flashed onto the device.
Probably not. If you let a raw NAND flash chip erase itself with the
proper command, you get all 0xFF afterwards. An intelligent flash
tool would recognize larger blocks of 0xFF in an image and then just
not touch the flash in that areas. Writing 0xFF on already erased
blocks gains nothing. Writing non 0xFF padding is just useless write
operations and will only decrease the lifetime of the flash.
The padding stops existing inside of the firmware image, so it doesn't
actually get to the point where it would try to write 0x00 onto the NAND
flash.
I honestly thought it's less of a obscure hacky parameter considering
it's one of the few mkenvimage provides but i'll take that it's not of
much use to most people.
Regards,
Sebastian
