6 comments:
Patch Set #2, Line 31: #if IS_ENABLED(CONFIG_VBOOT_STARTS_IN_BOOTBLOCK)
Can we push this as a separate change to keep things clear?
Patch Set #2, Line 162: asserted minimum
This is probably not relevant any more.
File src/security/vboot/Kconfig:
Patch Set #2, Line 95: VBOOT_WORKING_DATA_SIZE
Can we avoid having this Kconfig and simply use VB2_WORKBUF_RECOMMENDED_SIZE directly since it is exported in 2api.h via vb2_api.h?
File src/security/vboot/Makefile.inc:
Patch Set #2, Line 25: # When VBOOT_STARTS_IN_ROMSTAGE is selected, DRAM is already up by the time
Can we push this change as a separate CL just to keep things clearer?
File src/security/vboot/vboot_loader.c:
Also considering making this >=, but I'm not sure if there ever would be an actual case that only a […]
If we expect this CONFIG_VBOOT_WORKING_DATA_SIZE to always be same as VB2_WORKBUF_RECOMMENDED_SIZE, is there any advantage of defining that config? Can we just re-use the VB2_WORKBUF_RECOMMENDED_SIZE from 2api.h?
File src/soc/cavium/cn81xx/include/soc/memlayout.ld:
Actually, I'm still on the fence of whether hard-coding a number here is still a better option. […]
If we end up increasing the global config value, then the macros for REGION already take care of complaining about a region overlapping the previous one.
Reason I like having the size in here is just to make it easier when doing the math for different regions. But it is not very often that you would do that. So, I don't have a very strong opinion for/against this.
To view, visit change 31474. To unsubscribe, or for help writing mail filters, visit settings.