subject:"\[U\-Boot\] \[PATCH 20\/27\] image\: Use ram_top, not bi_memsize, in getenv_bootm_size"

Re: [U-Boot] [PATCH 20/27] image: Use ram_top, not bi_memsize, in getenv_bootm_size

2016-10-03 Thread Simon Glass

Hi Paul, On 1 October 2016 at 08:19, Paul Burton wrote: > When determining the region of memory to allow for use by bootm, using > bi_memstart & adding bi_memsize can cause problems if that leads to an > integer overflow. For example on some MIPS systems bi_memstart would

[U-Boot] [PATCH 20/27] image: Use ram_top, not bi_memsize, in getenv_bootm_size

2016-10-01 Thread Paul Burton

When determining the region of memory to allow for use by bootm, using bi_memstart & adding bi_memsize can cause problems if that leads to an integer overflow. For example on some MIPS systems bi_memstart would be 0x8000 (ie. the start of the MIPS ckseg0 region) and if the system has