summaryrefslogtreecommitdiffstats
path: root/arch/sandbox/board/Makefile
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2021-06-29 08:37:30 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2021-07-03 22:06:15 +0200
commit5bf59d3f2baa0f98ab93ddb4ea8a3b37986db608 (patch)
treea1fcde704ba8a88a2ef6133fc27af341994a03bf /arch/sandbox/board/Makefile
parentd4efa05303408d84a347c1c560ea860cf9ad953c (diff)
downloadbarebox-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 'arch/sandbox/board/Makefile')
-rw-r--r--arch/sandbox/board/Makefile2
1 files changed, 2 insertions, 0 deletions
diff --git a/arch/sandbox/board/Makefile b/arch/sandbox/board/Makefile
index ffb1dbc21e..59fece60ef 100644
--- a/arch/sandbox/board/Makefile
+++ b/arch/sandbox/board/Makefile
@@ -10,3 +10,5 @@ obj-y += watchdog.o
obj-$(CONFIG_LED) += led.o
extra-y += barebox.lds
+
+extra-y += stickypage.o