Uboot mystery value up to date, but not using it?

Is the problem that you see both values “2025-05-06” as well as “2024.10-g424c714eb247-dirty” and you conclude they must be different u-boot versions? The first version is the git tag. The second version is the version of u-boot used by that git tag. Ideally, when building u-boot, the version string would include the MNT git tag as well to cause less confusion.

For example, would it be more helpful to let the u-boot version be something like this: 2024.10-MNT20250506-g424c714eb247-dirty

@minute I have a local patch which is able to inject the git tag into the u-boot version string – do you want it that way or any different?

1 Like