Hello Alex,
>
>
>> Am 14.04.2023 um 10:54 schrieb Alex Bennée :
>>
>>
>> Also could you not achieve the same thing using the guest-loader which
>> uses the multiboot spec and sets:
>>
>> const char *compat[2] = { "multiboot,module", "multiboot,ramdisk" };
>> if (qemu_fdt_setprop_
> Am 14.04.2023 um 10:54 schrieb Alex Bennée :
>
Hello Alex,
>
> Where are these DTB nodes documented?
Yes, it is currently missing.
>
> Also could you not achieve the same thing using the guest-loader which
> uses the multiboot spec and sets:
>
>const char *compat[2] = { "multiboo
Hello Peter,
I totally agree. We are developing a unikernel
(https://github.com/hermitcore/rusty-hermit). On x86, we are using the
multiboot specification. I thought that this specification is only available on
x86.
In principle, a unikernel is a single application, which runs directly on the
On Fri, 14 Apr 2023 at 08:35, Stefan Lankes
wrote:
>
> Currently, the flag `--initrd` is only support for Linux ARM kernels.
> However, also other ELF kernels could depend on an initial ramdisk.
> This PR loads also the initrd for ELF kernels and announce the
> location by the nodes "/chosen/initr
Stefan Lankes writes:
> Currently, the flag `--initrd` is only support for Linux ARM kernels.
> However, also other ELF kernels could depend on an initial ramdisk.
> This PR loads also the initrd for ELF kernels and announce the
> location by the nodes "/chosen/initrd-start" and
> "/chosen/init
Currently, the flag `--initrd` is only support for Linux ARM kernels.
However, also other ELF kernels could depend on an initial ramdisk.
This PR loads also the initrd for ELF kernels and announce the
location by the nodes "/chosen/initrd-start" and
"/chosen/initrd-end" within the device tree.
Sig
