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 <[email protected]> --- @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 <[email protected]> --- 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
