From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qemu_aarch64_virt: use the in-kernel defconfig
Date: Sat, 4 Jul 2020 23:01:36 +0200 [thread overview]
Message-ID: <20200704230136.086e2263@windsurf.home> (raw)
In-Reply-To: <affa122f-ca38-e1f8-7bba-79ece4e87024@gmail.com>
On Sat, 4 Jul 2020 17:41:39 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> Hi Masahiro,
>
> Le 04/07/2020 ? 16:18, Masahiro Yamada a ?crit?:
> > The defconfig file from the kernel tree works enough for the
> > qemu-system-aarch64 virt machine. Remove the custom config file.
>
> I'm agree that we should use the architecture's default configuration when
> possible and use a defconfig fragment to enable (or disable) additional options.
>
> Note: The default defconfig contain more option enabled that the defconfig
> provided by Buildroot. The kernel build time is slightly increased.
>
> Can you compare the diff between the two defconfig ?
> If some options enabled in the custom linux.conf but not in the architecture's
> default configuration, we need to consider adding them in a defconfig fragment file.
The arm64 defconfig is really huge, as it builds supports for all arm64
platforms. I think it makes sense to have a smaller defconfig that
builds a kernel just for the Qemu AArch64 virt platform.
More than a diff between the two configs, I'd be more interested in
having details on the build time of both (and perhaps the resulting
kernel image size).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-07-04 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 14:18 [Buildroot] [PATCH] qemu_aarch64_virt: use the in-kernel defconfig Masahiro Yamada
2020-07-04 15:41 ` Romain Naour
2020-07-04 17:07 ` Masahiro Yamada
2020-07-05 14:13 ` Romain Naour
2020-07-04 21:01 ` Thomas Petazzoni [this message]
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=20200704230136.086e2263@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox