[...] > >>>> > >>>> Pretty much this patch is bringing back old behavior before these two > >>>> patches > >>>> have been applied to the repo. > >>> > >>> It doesn't make sense to update to or run a firmware that won't be > >>> able to use capsule updates ever again. > >> > >> It means that can be consider as misconfiguration. Which ends up today in > >> forever loop (1/2 will at least tell now what it is happening). > >> > >> , eth1: ethernet@ed920000 > >> Cannot find fwu device > >> Cannot find fwu device > >> Cannot find fwu device > >> Cannot find fwu device > >> Cannot find fwu device > >> Cannot find fwu device > >> Cannot find fwu device > >> Cannot find fwu device > >> Cannot find fwu device > >> Cannot find fwu device > >> > >> But shouldn't be there different action? Go back to second image or reset > >> for > >> example? > > > > At this point, either your metadata is gone, in which case you can > > either try to recreate them and hope for the best or an update broke > > the fwu mechanism indeed. > > In theory the board will automatically revert to the secondary > > partition after X reboots since no one is providing an acceptance > > capsule (or variable) so reseting should be fine. > > It just means that I should drop this patch right?
Yes please. Thanks /Ilias > > Thanks, > Michal
