On Thu Jul 9, 2026 at 12:48 PM CEST, Carlo Caione wrote: > With CONFIG_FIT_BEST_MATCH, fit_conf_find_compat() selects the > configuration matching the most specific U-Boot compatible string; on > equal matches the first listed configuration wins and the configurations > node 'default' property is never consulted. > > A FIT whose configurations all share the same base devicetree compatible > (e.g. one manifest carrying a base tree plus overlay combinations for a > single board) therefore always boots the first configuration, silently > ignoring the default chosen by the manifest author. > > Break score ties in favour of the default configuration. A strictly > better compatible match still wins over it, and FITs without a default > keep the current first-listed behaviour. > > Reviewed-by: Simon Glass <[email protected]> > Reviewed-by: Tom Rini <[email protected]> > Signed-off-by: Carlo Caione <[email protected]>
Hi Simon and Tom, any chance you can pick this up for the next release? Thanks, -- Carlo Caione
