What's the state of u-boot v2023.10 for ASPEED SoCs?

[Andrew Jeffery]

On Mon, 2025-03-31 at 21:48 +0200, Tan Siewert wrote:
> We've been working on bringing some of our systems to OpenBMC, but the 
> MAC address is stored in an EEPROM rather than being branded somewhere else.
> In Linux, we're using `nvmem-cells` to reference the EEPROM and the 
> offset for the `mac-address` cell via the device tree.
> Unfortunately, the nvmem API in U-Boot was introduced in v2022.10, and 
> we are still on v2019.04.
> 
> The commit chain required to backport this feature appears to be quite 
> big, and to be honest, I'm not sure if it makes sense to backport such 
> non-trivial changes that don’t fix existing issues but rather introduce 
> new functionality.
> 
> So my question is: what’s the current state of the v2023.10 branch? Is 
> it still a work in progress, or is it in a state where it could be 
> tested on non-AST2700 SoCs and possibly submitted to openbmc/u-boot?

I think the main thing I'll say here is that any help with u-boot
maintenance is appreciated :)

I see you've had some discussion with Milton on discord as well[1].

[1]: https://discord.com/channels/775381525260664832/775694683589574659/1357374850318209034

Andrew