On Tue, Jun 29, 2021 at 08:37:30AM +0200, Ahmad Fatoum wrote: > The idea of the stickypage was to have a 4K memory region persistent > over resets. This region was implemented as mmap of a temporary hostfile, > which was created on first barebox start and maintained over resets. > > Usability was a bit lacking however: > - The temporary files weren't deleted > - state always showed warnings and errors on first boot. The banner > telling users to ignore this wasn't best user experience > - In the same vein, the power driver had logic to handle a fresh > (zeroed) stickypage and interpret that as POR boot > > We can avoid all that, by just shipping a default stickypage and > referencing that from DT. Do that. > > Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> > --- > v1 -> v2: > - compile stickypage at build time instead of shipping it in binary > form. Sascha reports issues with binary patche handling outside git. > --- Applied, thanks Sascha -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
