summaryrefslogtreecommitdiffstats
path: root/Documentation/devel/background-execution.rst
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2021-03-08 20:32:14 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2021-03-22 10:16:45 +0100
commitdd73d94f47712d900f2e9b6531c9f6a061176b01 (patch)
treec0b8a401ef59c8fe2ad9b3ede26a6379fb9f7738 /Documentation/devel/background-execution.rst
parenta1cbfb3335213f76d2000c989fa8599933cf75ac (diff)
downloadbarebox-dd73d94f47712d900f2e9b6531c9f6a061176b01.tar.gz
barebox-dd73d94f47712d900f2e9b6531c9f6a061176b01.tar.xz
ARM64: board-dt-2nd: adopt kernel image header
The ARM64 generic DT image is meant to be interchangeable with a kernel image to aid in debugging and testing. To achieve this, it reuses an externally passed device tree in x0, just like Linux does. The ARM barebox image format used however imposes some limitations: - Commands verifying the header before boot, like U-Boot's booti won't boot the barebox image - The barebox image is not fully relocatable. It has the implicit assumption that the barebox stack can grow into the memory space preceding the barebox image while the /memory node is parsed from the FDT. Adopting the Linux ARM64 header solves both issues. booti won't be able to tell us apart and we can specify an image load offset to reserve a stack space that won't interfere with anything else. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'Documentation/devel/background-execution.rst')
0 files changed, 0 insertions, 0 deletions