[U-Boot] [PATCH v2 03/18] bootvx: x86: Explicitly clear the bootloader image size
Bin Meng
bmeng.cn at gmail.com
Mon Apr 16 09:15:42 UTC 2018
On Fri, Apr 13, 2018 at 12:41 AM, Simon Glass <sjg at chromium.org> wrote:
> On 11 April 2018 at 23:02, Bin Meng <bmeng.cn at gmail.com> wrote:
>> VxWorks bootloader stores its size at a pre-defined offset @ 0x5004.
>> Later when VxWorks kernel boots up and system memory information is
>> retrieved from the E820 table, the bootloader size will be subtracted
>> from the total system memory size to calculate the size of available
>> memory for the OS.
>>
>> Explicitly clear the bootloader image size otherwise if memory
>> at this offset happens to contain some garbage data, the final
>> available memory size for the kernel is insane.
>>
>> Signed-off-by: Bin Meng <bmeng.cn at gmail.com>
>> ---
>>
>> Changes in v2: None
>>
>> cmd/elf.c | 7 +++++++
>> include/vxworks.h | 9 +++++++++
>> 2 files changed, 16 insertions(+)
>
> Reviewed-by: Simon Glass <sjg at chromium.org>
applied to u-boot-x86, thanks!
More information about the U-Boot
mailing list