04:32 <crb> d

12:58 <granquet> Hello.

12:58 <granquet> I'm trying to wrap my head around the fitImage + x86_64 combo to boot linux (at first).

12:58 <granquet> Am I correct in assuming that the kernel image should be `architecture = x86_64` but the setup.bin should be kept at `architecture = x86` ? (vmlinux is an elf 64 but setup.bin is an x86 boot executable) or is it irrelevant anyway as setup will switch to 64 bit mode?

12:58 <granquet> Also, wouldn't it be possible to directly boot a bzImage in the fitimage by using`type = kernel_noload` ? from what I understand this performs no load/relocations and just "executes" the image with it's embedded setup.bin (and all...).

13:03 <marex> sjg1: xypron: ^

18:47 <xypron> granquet: What is the bitness of your U-Boot? If your U-Boot is 64 bit, you should be able to boot straight into the kernel.

19:16 <granquet> xypron: it's a 64bit u-boot. so I should be able to use `architecture = x86_64` for the kernel and not use a setup?

19:42 <xypron> granquet: I buiild with `qemu-x86_64_defconfig acpi.config`. I can boot https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img by defining a boot option with the eficonfig command and booting it via `bootefi bootmgr. The boot option contains the vmlinuz and initrd and the command line parameter console=ttyS0 root=/dev/sda ro. No setup.bin used. You should be able to do the same via a FIT image and setting environment variable bootargs

19:42 <xypron> assuming that you use origin/next.

19:47 <xypron> granquet: FIT images can both be for EFI binary and for kernels without EFI stub. See CONFIG_BOOTM_EFI.

20:09 <granquet> IIRC I've tried booting directly the x86_64 vmlinux without a setup.cfg in a fit image and I got `Could not find a valid setup.bin for x86`.

20:09 <granquet> I see in the bootm_find_os() function that a setup.cfg is also expected for x86_64

20:10 <granquet> I specifically want a fitImage :)