From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@busybox.net, Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [Buildroot] [PATCH 1/2] qemu_arm_versatile: switch to in-kernel defconfig + fragment
Date: Sat, 8 Jan 2022 15:13:42 +0100 [thread overview]
Message-ID: <20220108151342.063a9bc6@windsurf> (raw)
In-Reply-To: <8bfdc46b-bfbe-2470-0068-ca3a5d72fd89@smile.fr>
On Sat, 8 Jan 2022 15:09:56 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> We use a custom kernel defconfig for this defconfig since it was added to
> Buildroot [1].
>
> I guess the aim of having a custom kernel defconfig is to reduce the build time.
Most likely yes, but when I see the fragment, it indeed disables a lot
of things, which is nice as it speed up the build. Just like on x86,
you could build the full defconfig to have something that boots under
qemu, but having a stripped down configuration is a lot more
useful/practical;
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-08 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 14:38 [Buildroot] [PATCH 1/2] qemu_arm_versatile: switch to in-kernel defconfig + fragment Masahiro Yamada
2021-03-16 14:38 ` [Buildroot] [PATCH 2/2] qemu_arm_versatile_nommu: " Masahiro Yamada
2021-03-16 14:55 ` [Buildroot] [PATCH 1/2] qemu_arm_versatile: " Masahiro Yamada
2022-01-08 14:09 ` Romain Naour
2022-01-08 14:13 ` Thomas Petazzoni [this message]
2022-01-08 14:16 ` Arnout Vandecappelle
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=20220108151342.063a9bc6@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
--cc=masahiroy@kernel.org \
--cc=romain.naour@smile.fr \
/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