On Thu, Nov 02, 2023 at 06:27:37PM +0800, Yong-Xuan Wang wrote:
> Hi Tom,
>
> On Tue, Oct 31, 2023 at 7:54 PM Tom Rini wrote:
> >
> > On Tue, Oct 31, 2023 at 03:56:45PM +0800, Yong-Xuan Wang wrote:
> >
> > > Hi Tom,
> > >
> > > 0x8020 comes from the result of the relocated_addr in booti_setup
Hi Tom,
On Tue, Oct 31, 2023 at 7:54 PM Tom Rini wrote:
>
> On Tue, Oct 31, 2023 at 03:56:45PM +0800, Yong-Xuan Wang wrote:
>
> > Hi Tom,
> >
> > 0x8020 comes from the result of the relocated_addr in booti_setup()
> > on HiFive Unmatched board. If we load the Kernel Image to this address,
> >
On Tue, Oct 31, 2023 at 03:56:45PM +0800, Yong-Xuan Wang wrote:
> Hi Tom,
>
> 0x8020 comes from the result of the relocated_addr in booti_setup()
> on HiFive Unmatched board. If we load the Kernel Image to this address,
> it will not be moved. Currently one of the first two 8-byte of RISC-V
>
Hi Tom,
0x8020 comes from the result of the relocated_addr in booti_setup()
on HiFive Unmatched board. If we load the Kernel Image to this address,
it will not be moved. Currently one of the first two 8-byte of RISC-V
Kernel Image is j _start_kernel instruction, so it's OK to execute the
heade
On Thu, Oct 26, 2023 at 03:22:52AM +, Yong-Xuan Wang wrote:
> U-boot initially loads the kernel image to the kernel_addr_r, and
> subsequently relocates it to memory address 0x8020. Setting
> kernel_addr_r to 0x8020 can eliminate one copy operation.
>
> Signed-off-by: Yong-Xuan Wang
5 matches
Mail list logo
