1 comment:
File src/arch/x86/early_ram.ld:
Patch Set #22, Line 23: . = CONFIG_X86_RESET_VECTOR - ARCH_POINTER_ALIGN_SIZE - _STACK_SIZE - _CONSOLE_SIZE - _TIMESTAMPS_SIZE - _FMAP_SIZE;
It encompasses this area, and not the other way around.
I don't think that is true. On previous platforms, C_ENV_BOOTBLOCK_SIZE basically captured the read-only data and code which was just XIP from memory-mapped SPI flash.
I think any problem w/C_ENV_BOOTBLOCK_SIZE here would be a similar problem in a traditional platform too.
I don't think so. These regions would be in the CAR which had a different base. Now, you are calculating the base of this data region using RESET_VECTOR in DRAM. I believe this would result in overlap of .earlyram.data region with the code region.
To view, visit change 35035. To unsubscribe, or for help writing mail filters, visit settings.