Re: [U-Boot] [PATCH v2 03/18] bootvx: x86: Explicitly clear the bootloader image size

2018-04-16 Thread Bin Meng
On Fri, Apr 13, 2018 at 12:41 AM, Simon Glass wrote: > On 11 April 2018 at 23:02, Bin Meng wrote: >> VxWorks bootloader stores its size at a pre-defined offset @ 0x5004. >> Later when VxWorks kernel boots up and system memory information is >> retrieved

Re: [U-Boot] [PATCH v2 03/18] bootvx: x86: Explicitly clear the bootloader image size

2018-04-12 Thread Simon Glass
On 11 April 2018 at 23:02, Bin Meng 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

[U-Boot] [PATCH v2 03/18] bootvx: x86: Explicitly clear the bootloader image size

2018-04-11 Thread Bin Meng
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.