Hi Bin, On Thu, 13 Apr 2023 at 04:06, Bin Meng <[email protected]> wrote: > > On Mon, Apr 10, 2023 at 3:25 PM Rick Chen <[email protected]> wrote: > > > > > From: Simon Glass <[email protected]> > > > Sent: Monday, April 03, 2023 4:28 AM > > > To: U-Boot Mailing List <[email protected]> > > > Cc: Sean Anderson <[email protected]>; Bin Meng <[email protected]>; > > > Rick Jian-Zhi Chen(陳建志) <[email protected]>; Leo Yu-Chi Liang(梁育齊) > > > <[email protected]>; Simon Glass <[email protected]>; Andre Przywara > > > <[email protected]>; Marc Kleine-Budde <[email protected]>; > > > SESA644425 <[email protected]>; Samuel Holland > > > <[email protected]>; Steven Lawrance <[email protected]> > > > Subject: [PATCH] riscv: Add a 64-bit image type > > > > > > At present it is not possible to know whether an image can be booted by a > > > 32- or 64-bit bootloader. This means that U-Boot may attempt to boot the > > > wrong image. This may cause a crash which might be hard to debug. > > > > > > Add a new property to make this explicit. > > > > > > The existing 'RISC-V' is now taken to mean 32-bit. > > > > > > Signed-off-by: Simon Glass <[email protected]> > > > --- > > > > > > boot/image.c | 3 ++- > > > include/image.h | 3 ++- > > > 2 files changed, 4 insertions(+), 2 deletions(-) > > > > Reviewed-by: Rick Chen <[email protected]> > > This might create compatibility issues if the shipped host tool > (mkimage) does not match U-Boot version. Any idea how to avoid that?
If the images are created as 'riscv' then they will look like 32-bit images to U-Boot, so likely won't be allowed on a 64-bit machine. I don't think we can avoid that, but of course, the images could be updated to use the new type. Note that the type is a string in the image, so mkimage may in fact tolerate it. I haven't checked though. Regards, Simon
