aboutsummaryrefslogtreecommitdiff
path: root/src/boot/kernel_stage1.ld
diff options
context:
space:
mode:
authorvetch <vetch97@gmail.com>2020-01-13 12:40:38 +0100
committervetch <vetch97@gmail.com>2020-01-13 12:40:38 +0100
commit1af7591e37d09ddcd734ea07d0e999cf61c8bc5e (patch)
treea56c73c9eddeb148baffc3a31bf50edbbeb31074 /src/boot/kernel_stage1.ld
parent300cf770698142b636da867b7e04bf2d6ae9baa4 (diff)
downloadrpi-MMU-example-1af7591e37d09ddcd734ea07d0e999cf61c8bc5e.tar.gz
rpi-MMU-example-1af7591e37d09ddcd734ea07d0e999cf61c8bc5e.zip
Great Reorganisation, modify structure and makefile
Diffstat (limited to 'src/boot/kernel_stage1.ld')
-rw-r--r--src/boot/kernel_stage1.ld27
1 files changed, 0 insertions, 27 deletions
diff --git a/src/boot/kernel_stage1.ld b/src/boot/kernel_stage1.ld
deleted file mode 100644
index 3130634..0000000
--- a/src/boot/kernel_stage1.ld
+++ /dev/null
@@ -1,27 +0,0 @@
-ENTRY(_boot) /* defined in boot.S; qemu needs it to run elf file */
-
-/* Code starts at 0x8000 - that's where RPis in 32-bit mode load
- * kernel at. My experiments do, however, show, that qemu emulating
- * RPi2 loads the kernel at 0x10000! (took some pain to find out).
- * rpi-open-firmware, on the other hand, loads kernel at 0x2000000!
- * This is not really a problem, since:
- * 1. We can use our bootloader to load the kernel at 0x8000
- * 2. We've rewritten stage 1 of both bootloader and kernel in
- * careful assembly, so that they should work regardless of
- * where they are loaded.
- * 3. In qemu, we can load kernel.elf instead of raw binary
- * (qemu will do the right thing then)
- */
-
-SECTIONS
-{
-
- . = 0x8000;
-
- __start = .;
- .kernel_stage1 :
- {
- KEEP(kernel_stage1.o)
- }
- __end = .;
-}