From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/3] Compile boards only when firmware is present
Date: Wed, 26 Apr 2023 11:03:51 +0200 [thread overview]
Message-ID: <20230426090354.1350981-1-s.hauer@pengutronix.de> (raw)
We have recently introduced ARM multi_*_defconfig files to compile
for multiple SoC families in a single config. Before these can
successfully be compiled a bunch of firmware files need to be present
in the source tree. This can be inconvenient for users as they have
to grab the firmware files from several sources before they can
compile these configs, even though they might be only interested
in a single board.
To solve this make the boards depending on a firmware file selectable
only when the firmware is actually present. With this the
multi_*_defconfigs can always be built. Boards with missing firmware
files will be skipped from compilation automatically.
The next step might be to introduce a Kconfig option (or use existing
COMPILE_TEST option) to provide dummy files for the missing firmware
files which could help for compile testing.
Sascha
Sascha Hauer (3):
Kconfig: source Kconfig.include earlier
ARM: Rockchip: make boards only selectable when firmware is present
ARM: i.MX: make boards selectable only when firmware files are present
Kconfig | 2 +
arch/arm/mach-imx/Kconfig | 74 ++++++++++++++++++++++------------
arch/arm/mach-rockchip/Kconfig | 11 +++--
firmware/Kconfig | 21 ++++++++++
lib/kasan/Kconfig | 2 -
5 files changed, 80 insertions(+), 30 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-26 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 9:03 Sascha Hauer [this message]
2023-04-26 9:03 ` [PATCH 1/3] Kconfig: source Kconfig.include earlier Sascha Hauer
2023-04-26 9:03 ` [PATCH 2/3] ARM: Rockchip: make boards only selectable when firmware is present Sascha Hauer
2023-04-26 9:03 ` [PATCH 3/3] ARM: i.MX: make boards selectable only when firmware files are present Sascha Hauer
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=20230426090354.1350981-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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