On Thu, Jan 30, 2025 at 09:48:19AM +0000, Martin Schwan wrote: > -----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.
Thanks for elaborating. -- Tom
signature.asc
Description: PGP signature
