Re: RISC-V FIT image type

2023-04-05 Thread Simon Glass
Hi Bin, On Sun, 2 Apr 2023 at 15:33, Bin Meng wrote: > > Hi Simon, > > On Sat, Apr 1, 2023 at 2:31 PM Simon Glass wrote: > > > > Hi Bin, > > > > On Fri, 31 Mar 2023 at 19:22, Bin Meng wrote: > > > > > > On Fri, Mar 31, 2023 at 5:36 AM Simon Glass wrote: > > > > > > > > Hi, > > > > > > > > I

Re: RISC-V FIT image type

2023-04-01 Thread Bin Meng
Hi Simon, On Sat, Apr 1, 2023 at 2:31 PM Simon Glass wrote: > > Hi Bin, > > On Fri, 31 Mar 2023 at 19:22, Bin Meng wrote: > > > > On Fri, Mar 31, 2023 at 5:36 AM Simon Glass wrote: > > > > > > Hi, > > > > > > I notice that in image.h we have IH_ARCH_RISCV but no mention of > > >

Re: RISC-V FIT image type

2023-04-01 Thread Simon Glass
Hi Bin, On Fri, 31 Mar 2023 at 19:22, Bin Meng wrote: > > On Fri, Mar 31, 2023 at 5:36 AM Simon Glass wrote: > > > > Hi, > > > > I notice that in image.h we have IH_ARCH_RISCV but no mention of > > IH_ARCH_RISCV64. Should we not have two separate image types, as we do > > with ARM and x86?

Re: RISC-V FIT image type

2023-03-31 Thread Bin Meng
On Fri, Mar 31, 2023 at 5:36 AM Simon Glass wrote: > > Hi, > > I notice that in image.h we have IH_ARCH_RISCV but no mention of > IH_ARCH_RISCV64. Should we not have two separate image types, as we do > with ARM and x86? Otherwise, how would a loader know the word size of > the target machine? I

RISC-V FIT image type

2023-03-30 Thread Simon Glass
Hi, I notice that in image.h we have IH_ARCH_RISCV but no mention of IH_ARCH_RISCV64. Should we not have two separate image types, as we do with ARM and x86? Otherwise, how would a loader know the word size of the target machine? Regards, Simon