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 /arch/sandbox/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 'arch/sandbox/Makefile')
| -rw-r--r-- | arch/sandbox/Makefile | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/arch/sandbox/Makefile b/arch/sandbox/Makefile index 5fc7e227be..ba2614ea5f 100644 --- a/arch/sandbox/Makefile +++ b/arch/sandbox/Makefile @@ -75,3 +75,10 @@ common-y += $(BOARD) arch/sandbox/os/ arch/sandbox/lib/ common-$(CONFIG_OFTREE) += arch/sandbox/dts/ CLEAN_FILES += $(BOARD)/barebox.lds + +OBJCOPYFLAGS_stickypage.bin = -O binary + +stickypage.bin: arch/sandbox/board/stickypage.o + $(call if_changed,objcopy) + +all: stickypage.bin |