From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] sandbox: ship sample environment
Date: Sat, 3 Jul 2021 22:06:58 +0200 [thread overview]
Message-ID: <20210703200658.GY9782@pengutronix.de> (raw)
In-Reply-To: <20210629063730.7001-1-a.fatoum@pengutronix.de>
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@pengutronix.de>
> ---
> 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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2021-07-03 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 6:37 Ahmad Fatoum
2021-07-03 20:06 ` Sascha Hauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210703200658.GY9782@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox