aboutsummaryrefslogtreecommitdiff
path: root/kernel_stage1.ld
diff options
context:
space:
mode:
authorvetch <vetch97@gmail.com>2020-01-04 19:37:32 +0100
committervetch <vetch97@gmail.com>2020-01-04 19:37:32 +0100
commit615e3302c9dd358bb64cd56d1f3814ad8d5df84d (patch)
tree07b0469807eb3bff7ff7d3f3576858642bc66675 /kernel_stage1.ld
parent885a097da42317f48cead2d91c0e0240066943a8 (diff)
downloadrpi-MMU-example-615e3302c9dd358bb64cd56d1f3814ad8d5df84d.tar.gz
rpi-MMU-example-615e3302c9dd358bb64cd56d1f3814ad8d5df84d.zip
rearranged files, updated makefile
Diffstat (limited to 'kernel_stage1.ld')
-rw-r--r--kernel_stage1.ld27
1 files changed, 0 insertions, 27 deletions
diff --git a/kernel_stage1.ld b/kernel_stage1.ld
deleted file mode 100644
index 3130634..0000000
--- a/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 = .;
-}