* [PATCH] common: fastboot: make CONFIG_FASTBOOT_SPARSE=y the default
@ 2026-07-09 13:10 Ahmad Fatoum
2026-07-10 21:33 ` Sascha Hauer
0 siblings, 1 reply; 2+ messages in thread
From: Ahmad Fatoum @ 2026-07-09 13:10 UTC (permalink / raw)
To: barebox; +Cc: Ahmad Fatoum
Back in 2018, sparse support was made optional as "[s]parse support
is not always desired" without further elaboration.
Arguably the majority of users would benefit from sparse support enabled,
so flip the Kconfig default to make it opt-out instead.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
@Sascha, do you recall what reasons would there be to disable sparse
support? As I can't think of any besides binary size, I chose not to
include a migration guide entry about the default changing.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
common/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/common/Kconfig b/common/Kconfig
index f7122d89c6e2..85df7f7daec6 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -1478,6 +1478,7 @@ config FASTBOOT_SPARSE
bool
select IMAGE_SPARSE
prompt "Enable Fastboot sparse image support"
+ default y
help
Sparse images are a way for the fastboot protocol to write
images that are bigger than the available memory. If unsure,
--
2.47.3
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-07-10 21:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-07-09 13:10 [PATCH] common: fastboot: make CONFIG_FASTBOOT_SPARSE=y the default Ahmad Fatoum
2026-07-10 21:33 ` Sascha Hauer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox