diff options
| author | Ahmad Fatoum <a.fatoum@pengutronix.de> | 2021-06-29 08:37:30 +0200 |
|---|---|---|
| committer | Sascha Hauer <s.hauer@pengutronix.de> | 2021-07-03 22:06:15 +0200 |
| commit | 5bf59d3f2baa0f98ab93ddb4ea8a3b37986db608 (patch) | |
| tree | a1fcde704ba8a88a2ef6133fc27af341994a03bf /Makefile | |
| parent | d4efa05303408d84a347c1c560ea860cf9ad953c (diff) | |
| download | barebox-5bf59d3f2baa0f98ab93ddb4ea8a3b37986db608.tar.gz barebox-5bf59d3f2baa0f98ab93ddb4ea8a3b37986db608.tar.xz | |
sandbox: ship sample environment
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>
Link: https://lore.barebox.org/20210629063730.7001-1-a.fatoum@pengutronix.de
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'Makefile')
| -rw-r--r-- | Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1123,7 +1123,7 @@ endif # CONFIG_MODULES # Directories & files removed with 'make clean' CLEAN_DIRS += $(MODVERDIR) -CLEAN_FILES += barebox System.map include/generated/barebox_default_env.h \ +CLEAN_FILES += barebox System.map stickypage.bin include/generated/barebox_default_env.h \ .tmp_version .tmp_barebox* barebox.bin barebox.map \ .tmp_kallsyms* barebox.ldr compile_commands.json \ scripts/bareboxenv-target barebox-flash-image \ |