From d9ac897bd8aa7a8b6471bca1eb8a2bd314fdb133 Mon Sep 17 00:00:00 2001 From: Wojtek Kosior Date: Thu, 26 Dec 2019 19:06:18 +0100 Subject: minor changes (comments, whitespace) --- linker.ld | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) (limited to 'linker.ld') diff --git a/linker.ld b/linker.ld index a0ad1ae..33ac68c 100644 --- a/linker.ld +++ b/linker.ld @@ -2,16 +2,17 @@ ENTRY(_boot) /* defined in boot.S; qemu needs it to run elf file */ SECTIONS { - /* 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! */ + /* 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 out bootloader to load the kernel at 0x8000 */ - /* 2. We compile kernel with -fPIC, so it should be able to work with */ - /* any load addr. + /* 1. We can use our bootloader to load the kernel at 0x8000 */ + /* 2. We compile kernel with -fPIC, so it should be able to */ + /* work with any load addr. */ /* 3. In qemu, we can load kernel.elf instead of raw binary */ - /* (qemu will do the loading then) */ + /* (qemu will do the right thing then) */ . = 0x8000; @@ -38,7 +39,6 @@ SECTIONS __libkernel_size = __libkernel_end - __libkernel_start; - .interrupts : { __interrupts_start = .; @@ -47,7 +47,6 @@ SECTIONS interrupts.o __interrupts_end = .; } - __interrupts_size = __interrupts_end - __interrupts_start; __end = .; -- cgit v1.2.3