[PATCH 03/16] image: Take entry point as an output of setup_booti
Tom Rini
trini at konsulko.com
Tue Jun 11 15:52:09 CEST 2024
On Tue, Jun 11, 2024 at 02:29:38PM +0100, Jiaxun Yang wrote:
>
>
> 在2024年6月11日六月 下午2:02,Heinrich Schuchardt写道:
> > On 22.05.24 17:34, Jiaxun Yang wrote:
> >> For LoongArch the start of the image is not the entry
> >> point to the image.
> >
> > Looking at arch/loongarch/kernel/head.S there seem to be two cases:
> >
> > * The kernel has an EFI stub (CONFIG_EFI_STUB=y).
> > The legacy physical entry point is available at offset 0x08 of the
> > header.
> > * The kernel has no EFI stub.
> > The kernel entry point matches the start of the image.
> >
> > Where do you differentiate between the cases?
>
> Hi Heinrich,
>
> In case there is no EFI stub LoongArch would use elf format vmlinux, there
> is no real "raw" image for us.
>
> bootelf can't be used at the moment as it doesn't setup FDT and other environments
> properly.
>
> I'm planning to implement a bootlinuxelf command for this case, as MIPS, LoongArch,
> xtensa are all using ELF as default kernel image format.
Please note that we have CONFIG_CMD_ELF_FDT_SETUP already, so adjusting
things so that bootelf works for this case should be doable without a
new command.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20240611/4039c8c5/attachment.sig>
More information about the U-Boot
mailing list