threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
25 lines
1.0 KiB
Plaintext
25 lines
1.0 KiB
Plaintext
Creation of the self-extracting compressed kernel image (vmlinuz)
|
|
-----------------------------------------------------------------
|
|
|
|
This can be slightly confusing because it's a process with many steps.
|
|
|
|
The kernel object built by the arch/etrax100/Makefile, vmlinux, is split
|
|
by that makefile into text and data binary files, vmlinux.text and
|
|
vmlinux.data.
|
|
|
|
Those files together with a ROM filesystem can be catted together and
|
|
burned into a flash or executed directly at the DRAM origin.
|
|
|
|
They can also be catted together and compressed with gzip, which is what
|
|
happens in this makefile. Together they make up piggy.img.
|
|
|
|
The decompressor is built into the file decompress.o. It is turned into
|
|
the binary file decompress.bin, which is catted together with piggy.img
|
|
into the file vmlinuz. It can be executed in an arbitrary place in flash.
|
|
|
|
Be careful - it assumes some things about free locations in DRAM. It
|
|
assumes the DRAM starts at 0x40000000 and that it is at least 8 MB,
|
|
so it puts its code at 0x40700000, and initial stack at 0x40800000.
|
|
|
|
-Bjorn
|