From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Rename aarch64_efi_defconfig to qemu_aarch64_virt_efi_defconfig
Date: Sat, 11 Jul 2020 15:12:14 +0200 [thread overview]
Message-ID: <20200711151214.44b2b74a@windsurf.home> (raw)
In-Reply-To: <39be97c6-9569-e206-ebe5-a49ca65015af@gmail.com>
On Sat, 11 Jul 2020 15:08:27 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> Not really just testing this defconfig under Qemu, but having ACPI tables and
> other features enabled by EFI and grub when booting the system under Qemu.
>
> The current qemu_aarch64_virt_defconfig boot with just the kernel, so ACPI
> tables are missing and the plig and play support is disabled.
>
> dmesg:
> ACPI: Interpreter disabled.
> [...]
> pnp: PnP ACPI: disabled
>
> For example, ACPI and hotplug support is required to use QEMU Virtual NVDIMM
>
> -device nvdimm,id=nvdimm1,memdev=mem1
>
> Instead of renaming aarch64_efi_defconfig, we can enable UEFI and grub in the
> qemu_aarch64_virt_defconfig itself.
Seems like a good idea.
> But it still require the QEMU_EFI.fd firmware, either built by
> Buildroot (complex hand written build system) or fetched from Linaro.
Of course, it's always better to build things from source, but if it's
really too horrible, we can have a package that fetches pre-compiled
binaries from Linaro.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-07-11 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 23:02 [Buildroot] Rename aarch64_efi_defconfig to qemu_aarch64_virt_efi_defconfig Romain Naour
2020-07-11 10:59 ` Thomas Petazzoni
2020-07-11 13:08 ` Romain Naour
2020-07-11 13:12 ` Thomas Petazzoni [this message]
2020-07-11 13:34 ` Romain Naour
2020-07-13 13:18 ` Erico Nunes
2020-07-13 20:36 ` Romain Naour
2020-07-15 13:49 ` Thomas Petazzoni
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=20200711151214.44b2b74a@windsurf.home \
--to=thomas.petazzoni@bootlin.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.