I've been thinking since [the start of this discussion yesterday](https://discord.com/channels/754950670175436841/754950670175436848/1258738135026765977) about how difficult it would be to add a BMC feature called "hosted RK1 boot" (or similar), which uses FORCE_RECOVERY plus a local (built into the BMC firmware) bootloader image to bypass the eMMC altogether. Could have a few advantages: - There is no need to image anything to the RK1 - ...which also means RK1 modules with worn-out eMMC are still usable - ...users who netboot generally don't care about eMMC, and will further appreciate needing no per-RK1 setup - The bootloader is also the RK1 "platform firmware" responsible for things like RAM init; keeping that up to date is good for performance and stability. If this comes from the BMC on every boot, then updates to this are included with BMC firmware updates - A U-Boot script can be supplied by the BMC, which allows fine control over the boot method and can easily be tweaked by the user