@linmob Small mistake: link to "Lemmy - linuxphones: Tow-Boot release[...]" links to the previous link location.

@linmob being a reply guy about your Tow-Boot commentary: currently the boot order ends-up in practice "locked" to the default one due to one main issue: no way to interact with the platform firmware other than the volume keys and no feed back other than LED. In addition to the following.

The goal with Tow-Boot (before it accidentally ended-up being useful for phones) was that it acts mostly like your boring old laptop firmware. Including a menu for options, and those options being persistent across reboots. As such, OS boot order is planned to be one of those options with tangible "items" you can move around, and save whichever one you prefer. It is why I ported a curses implementation to U-Boot, so that building more complex UIs is possible.

There still are a few things to build to get to there, and also there was a large question mark left by the new "standard"[sic] boot concept from U-Boot, before the hiatus.

It would be nice if within a few months I could evaluate when that is happening for devices with display support.

In the mean time, if you can get to the console (e.g. serial) you can save the environment with devices with SPI, and thus you *currently already* can save a modified environment with the OS boot order changed!