Re: [PATCH 1/2] hw/core/loader: return image sizes as ssize_t

2022-06-01 Thread Alistair Francis
On Fri, Nov 12, 2021 at 12:12 AM Jamie Iles wrote: > > Various loader functions return an int which limits images to 2GB which > is fine for things like a BIOS/kernel image, but if we want to be able > to load memory images or large ramdisks then any file over 2GB would > silently fail to load. >

Re: [PATCH 1/2] hw/core/loader: return image sizes as ssize_t

2021-11-14 Thread Alistair Francis
On Fri, Nov 12, 2021 at 12:12 AM Jamie Iles wrote: > > Various loader functions return an int which limits images to 2GB which > is fine for things like a BIOS/kernel image, but if we want to be able > to load memory images or large ramdisks then any file over 2GB would > silently fail to load. >

Re: [PATCH 1/2] hw/core/loader: return image sizes as ssize_t

2021-11-12 Thread Luc Michel
On 14:11 Thu 11 Nov , Jamie Iles wrote: > Various loader functions return an int which limits images to 2GB which > is fine for things like a BIOS/kernel image, but if we want to be able > to load memory images or large ramdisks then any file over 2GB would > silently fail to load. > > Cc:

Re: [PATCH 1/2] hw/core/loader: return image sizes as ssize_t

2021-11-11 Thread Philippe Mathieu-Daudé
On 11/11/21 15:11, Jamie Iles wrote: > Various loader functions return an int which limits images to 2GB which > is fine for things like a BIOS/kernel image, but if we want to be able > to load memory images or large ramdisks then any file over 2GB would > silently fail to load. > > Cc: Luc

[PATCH 1/2] hw/core/loader: return image sizes as ssize_t

2021-11-11 Thread Jamie Iles
Various loader functions return an int which limits images to 2GB which is fine for things like a BIOS/kernel image, but if we want to be able to load memory images or large ramdisks then any file over 2GB would silently fail to load. Cc: Luc Michel Signed-off-by: Jamie Iles ---