All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] configs/qemu_aarch64_virt_defconfig: boot with grub bootloader with efi
Date: Mon, 13 Jul 2020 23:21:54 +0200	[thread overview]
Message-ID: <daaa32d9-5da6-84c6-3546-6abb04542530@gmail.com> (raw)
In-Reply-To: <20200712212826.4025d0d5@windsurf.home>

Hello Thomas,

Le 12/07/2020 ? 21:28, Thomas Petazzoni a ?crit?:
> Hello,
> 
> On Sun, 12 Jul 2020 18:34:21 +0200
> Romain Naour <romain.naour@gmail.com> wrote:
> 
>> The current qemu_aarch64_virt_defconfig boot with just the kernel, so ACPI
>> tables are missing and the plug and play support is disabled.
>>
>> dmesg:
>> ACPI: Interpreter disabled.
>> [...]
>> pnp: PnP ACPI: disabled
>>
>> The ACPI support is already available in the kernel defconfig, the
>> memory hotplug support will be added by the next patch.
>>
>> Borrow the post image script, genimage and bootloader configuration from
>> aarch64_efi_defconfig to build the disk image used to boot the system
>> in efi mode.
>>
>> As a side effect, the bootloader grub2 is now runtime tested in the
>> Buildroot gitlab-ci while testing this defconfig.
>>
>> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> 
> But isn't this making qemu_aarch64_virt_defconfig too similar to
> aarch64_efi_defconfig ?

Well, that why I suggested to merge the two defconfig. But I'm fine having two
defconfig for different purpose.

> 
> Shouldn't we keep qemu_aarch64_virt_defconfig as-is, and simply add
> runtime testing for aarch64_efi_defconfig ?

I would like to continue enabling features in the qemu_aarch64_virt_defconfig
and some of them require ACPI support. That is why I borrowed the post-image
script, grub defconfig from aarch64_efi_defconfig and packaged the edk2-bin.

If we start enabling qemu runtime testing for other defconfig that the one named
qemu_* we could continue (for example) test the nitrogen6x_defconfig with
qemu-system-arm -M sabrelite. This can be interesting :)

For now, I would like to focus on qemu_* defconfigs.

Best regards,
Romain

> 
> Thomas
> 

  reply	other threads:[~2020-07-13 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12 16:34 [Buildroot] [PATCH 1/4] package/edk2-aarch64-bin: new package Romain Naour
2020-07-12 16:34 ` [Buildroot] [PATCH 2/4] board/qemu/aarch64-virt/linux.config: enable ACPI Romain Naour
2020-07-12 16:34 ` [Buildroot] [PATCH 3/4] configs/qemu_aarch64_virt_defconfig: boot with grub bootloader with efi Romain Naour
2020-07-12 19:28   ` Thomas Petazzoni
2020-07-13 21:21     ` Romain Naour [this message]
2020-07-12 16:34 ` [Buildroot] [PATCH 4/4] board/qemu/aarch64-virt/linux.config: enable memory hotplug Romain Naour
2020-07-12 19:27   ` Thomas Petazzoni
2020-07-13 21:24     ` Romain Naour
2021-05-17 16:23 ` [Buildroot] [PATCH 1/4] package/edk2-aarch64-bin: new package Yann E. MORIN

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=daaa32d9-5da6-84c6-3546-6abb04542530@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=buildroot@busybox.net \
    /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.