All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yao Zi <me@ziyao.cc>
To: Junhui Liu <junhui.liu@pigmoral.tech>, u-boot@lists.u-boot-project.org
Cc: Tom Rini <trini@konsulko.com>,
	Aristo Chen <aristo.chen@canonical.com>,
	Simon Glass <sjg@chromium.org>,
	Daniel Golle <daniel@makrotopia.org>,
	Tim Ouyang <tim609@andestech.com>,
	Leo Liang <leo.liang@sifive.com>, Yao Zi <me@ziyao.cc>,
	Igor Opaniuk <igor.opaniuk@oss.qualcomm.com>
Subject: Re: [PATCH] bootm: Relocate RISC-V Linux Images before booting
Date: Tue, 20 Oct 2026 00:10:06 +0000	[thread overview]
Message-ID: <ataxXt_iYw4fzR9Y@pie> (raw)
In-Reply-To: <20261020-bootm-riscv-image-relocation-v1-1-e583a2dd1d14@pigmoral.tech>

On Tue, Oct 20, 2026 at 12:13:03AM +0800, Junhui Liu wrote:
> RISC-V Linux requires the kernel Image to be loaded at a 2 MiB aligned
> address for RV64, or a 4 MiB aligned address for RV32 [1]. When booting
> a FIT image with a kernel_noload payload, or an Android boot image via
> fastboot boot, the kernel may be placed at an address that does not
> meet these alignment requirements and fail to boot.
> 
> As already done for ARM64, call booti_setup() for RISC-V Linux Images
> to obtain a suitable load address and relocate the kernel before
> booting. This reuses the existing RISC-V booti placement policy.
> 
> Link: https://docs.kernel.org/arch/riscv/boot.html#kernel-location [1]
> Signed-off-by: Junhui Liu <junhui.liu@pigmoral.tech>

Reviewed-by: Yao Zi <me@ziyao.cc>

Thanks,
Yao Zi

      parent reply	other threads:[~2026-10-20  0:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 16:13 [PATCH] bootm: Relocate RISC-V Linux Images before booting Junhui Liu
2026-10-19 18:03 ` Tom Rini
2026-10-20  0:10 ` Yao Zi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ataxXt_iYw4fzR9Y@pie \
    --to=me@ziyao.cc \
    --cc=aristo.chen@canonical.com \
    --cc=daniel@makrotopia.org \
    --cc=igor.opaniuk@oss.qualcomm.com \
    --cc=junhui.liu@pigmoral.tech \
    --cc=leo.liang@sifive.com \
    --cc=sjg@chromium.org \
    --cc=tim609@andestech.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.