-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Wed, 2025-01-29 at 10:03 -0600, Tom Rini wrote: > On Wed, Jan 29, 2025 at 03:25:25PM +0100, Martin Schwan wrote: > > Add a bootmeth driver which supports booting A/B system with RAUC > > as > > their update client. > > > > Signed-off-by: Martin Schwan <[email protected]> > > --- > > boot/Kconfig | 11 ++ > > boot/Makefile | 1 + > > boot/bootmeth_rauc.c | 408 > > +++++++++++++++++++++++++++++++++++++++++++++++++++ > > 3 files changed, 420 insertions(+) > > I'm curious, what would be required to have this work for any block > device, rather than just "mmc" ? Just a lack of time / testing / this > is > v1 and that's a future idea? Or is there something more fundamental > required within bootstd/bootmeths ? Thanks! >
Besides MMC, RAUC supports updating SSDs and raw NAND flash [1]. I guess there should be very little to no adjustments necessary to support SSDs (probably only adjust checks). For raw NAND flash and using UBI volumes, this would require some additional code calling the correct read operations, but is definitely possible. I did not implement it yet because of lack of time and verification, as you correctly guessed. Network devices are not supported for obvious reasons. Regards, Martin [1]: https://rauc.readthedocs.io/en/latest/integration.html#partitioning-your-device -----BEGIN PGP SIGNATURE----- iQFHBAEBCAAxFiEEvRVVC1N5GoUWk9IrDQIuwQKeD4IFAmebSuITHG0uc2Nod2Fu QHBoeXRlYy5kZQAKCRANAi7BAp4PgoiuB/0QYPrKrpo+1ev+PuKDwt2811zr0nP9 0HUmz4Nv56CJj8Qc9S4NL2yyYrHgFAQ0xPcuYem20NEZZYcctKzX5pYrtu4vYOBm WUsoj1+3TVIbQ+c2i/4NuKBPAgsad1wZcQY04cTrtAXzBWzNxI56kGP0PfLYV4ls /O/xF0QamnjXQRtHUrv4kQOnqi+RBvQIxD7ICZ/7oiNfV4vK7hU8Vu7TnoOSZKCG qNr5znXZgT8axLSdkE9VjX2IwpTm+ihuDe94/BrLg4E/54yBBcfKwPeYszFyDoXV o8HNd1eyT137B9e3EHK2PC2hVhc5C/1V6RKG0SRI1bTTrdYNlSL0rfci =gPis -----END PGP SIGNATURE-----
