On Fri, Sep 20, 2024 at 05:59:00PM +0200, Simon Glass wrote:
Hi Tom,
On Thu, 5 Sept 2024 at 00:25, Tom Rini trini@konsulko.com wrote:
On Thu, Aug 29, 2024 at 08:57:46AM -0600, Simon Glass wrote:
When the best-match feature fails to find something, use the provided config name as a fallback. The allows SPL to select a suitable config when best-match is enabled.
Signed-off-by: Simon Glass sjg@chromium.org
boot/image-fit.c | 19 ++++++++++--------- include/image.h | 4 +++- 2 files changed, 13 insertions(+), 10 deletions(-)
Don't we need a documentation update? If no, because this mechanism isn't well documented, can you please follow up with that? Thanks.
CONFIG_FIT_BEST_MATCH is mentioned in the spec [1]
But re the fallback, I'm not sure where that should be documented. Perhaps add a note at [2]?
Should we be using the mechanism that I'd swear the documentation build process has, to fetch an external document? I think we would have a better user/developer experience if our documentation explained how to use a feature, as that's where people will tend to look first.