Limine Bare Bones: Difference between revisions
m
Wording fix.
[unchecked revision] | [unchecked revision] |
mNo edit summary |
m (Wording fix.) |
||
(47 intermediate revisions by 7 users not shown) | |||
Line 3:
{{Template:Kernel designs}}
The Limine Boot Protocol is the native boot protocol provided by the [[Limine]] bootloader.
It provides cutting edge features such as 5-level paging support, 64-bit [[Long Mode]] support, and direct higher half kernel loading.
The Limine boot protocol is firmware and architecture agnostic. The Limine bootloader supports x86-64,
This article will demonstrate how to write a small Limine-compliant x86-64
For this example, we will create these 2 files
*
* linker.ld
As one may notice, there is no "entry point" assembly stub, as one is not necessary with the Limine protocol when using a language which can make use of a standard SysV x86 [[Calling Conventions|calling convention]].
Furthermore, we will download the header file '''limine.h''' which defines structures and constants that we will use to interact with the bootloader from [https://
Obviously, this is just a bare bones example, and one should always refer to the [https://github.com/limine-bootloader/limine/blob/trunk/PROTOCOL.md Limine protocol specification] for more details and information.
===
This is the kernel "main".
<
#include <stdint.h>
#include <stddef.h>
#include <stdbool.h>
#include <limine.h>
// Set the base revision to 2, this is recommended as this is the latest
// base revision described by the Limine boot protocol specification.
// See specification for further info.
__attribute__((used, section(".requests")))
static volatile LIMINE_BASE_REVISION(2);
// The Limine requests can be placed anywhere, but it is important that
// the compiler does not optimise them away, so, usually, they should
// be made volatile or equivalent
// once or marked as used with the "used" attribute as done here.
__attribute__((used, section(".requests")))
static volatile struct limine_framebuffer_request framebuffer_request = {
.id = LIMINE_FRAMEBUFFER_REQUEST,
.revision = 0
};
// Finally, define the start and end markers for the Limine requests.
// These can also be moved anywhere, to any .c file, as seen fit.
__attribute__((used, section(".requests_start_marker")))
static volatile LIMINE_REQUESTS_START_MARKER;
__attribute__((used, section(".requests_end_marker")))
static volatile LIMINE_REQUESTS_END_MARKER;
// GCC and Clang reserve the right to generate calls to the following
Line 98 ⟶ 117:
return 0;
}
Line 121 ⟶ 131:
// linker script accordingly.
void _start(void) {
// Ensure
if (
hcf();
}
// Ensure we got a framebuffer.
if (framebuffer_request.response == NULL
|| framebuffer_request.response->framebuffer_count < 1) {
hcf();
}
// Fetch the first framebuffer.
struct limine_framebuffer *framebuffer = framebuffer_request.response->framebuffers[0];
// Note: we assume the framebuffer model is RGB with 32-bit pixels.
for (size_t i = 0; i < 100; i++) {
volatile uint32_t *fb_ptr = framebuffer->address;
fb_ptr[i * (framebuffer->pitch / 4) + i] = 0xffffff;
}
// We're done, just hang...
Line 138 ⟶ 155:
}
</syntaxhighlight>
===linker.ld===
Line 146 ⟶ 161:
This is going to be our linker script describing where our sections will end up in memory.
<
/* Tell the linker that we want an x86_64 ELF64 output file */
OUTPUT_FORMAT(elf64-x86-64)
Line 158 ⟶ 173:
PHDRS
{
text PT_LOAD FLAGS(
rodata PT_LOAD FLAGS(
data PT_LOAD FLAGS(
dynamic PT_DYNAMIC FLAGS(0x06); /* Dynamic PHDR for relocations */
}
Line 176 ⟶ 192:
/* Move to the next memory page for .rodata */
.
.rodata : {
Line 183 ⟶ 199:
/* Move to the next memory page for .data */
.
.data : {
*(.data .data.*)
/* Place the sections that contain the Limine requests as part of the .data */
/* output section. */
KEEP(*(.requests_start_marker))
KEEP(*(.requests))
KEEP(*(.requests_end_marker))
} :data
/* Dynamic section for relocations, both in its own PHDR and inside data PHDR */
.dynamic : {
*(.dynamic)
} :data :dynamic
/* NOTE: .bss needs to be the last thing mapped to :data, otherwise lots of */
Line 194 ⟶ 221:
/* above this. */
.bss : {
*(.bss .bss.*)
*(COMMON)
} :data
/* Discard .note.* and .eh_frame* since they may cause issues on some hosts. */
/* Also discard the program interpreter section since we do not need one. This is */
/* more or less equivalent to the --no-dynamic-linker linker flag, except that it */
/* works with ld.gold. */
/DISCARD/ : {
*(.eh_frame*)
*(.note .note.*)
*(.interp)
}
}
</syntaxhighlight>
==Building the kernel and creating an image==
Line 215 ⟶ 246:
GNU make will process it.
<
# Nuke built-in rules and variables.
override MAKEFLAGS += -rR
Line 221 ⟶ 252:
# This is the name that our final kernel executable will have.
# Change as needed.
override KERNEL := myos
# Convenience macro to reliably declare user overridable variables.
Line 233 ⟶ 264:
endef
# It is
# We are
# the host system's toolchain, but this is not guaranteed.
override DEFAULT_KCC := cc
$(eval $(call DEFAULT_VAR,KCC,$(DEFAULT_KCC)))
# Same thing for "ld" (the linker).
override DEFAULT_KLD := ld
$(eval $(call DEFAULT_VAR,KLD,$(DEFAULT_KLD)))
# User controllable
override DEFAULT_KCFLAGS := -g -O2 -pipe
$(eval $(call DEFAULT_VAR,KCFLAGS,$(DEFAULT_KCFLAGS)))
# User controllable C preprocessor flags. We set none by default.
override DEFAULT_KCPPFLAGS :=
$(eval $(call DEFAULT_VAR,KCPPFLAGS,$(DEFAULT_KCPPFLAGS)))
# User controllable nasm flags.
override DEFAULT_KNASMFLAGS := -F dwarf -g
$(eval $(call DEFAULT_VAR,KNASMFLAGS,$(DEFAULT_KNASMFLAGS)))
# User controllable linker flags. We set none by default.
override DEFAULT_KLDFLAGS :=
$(eval $(call DEFAULT_VAR,KLDFLAGS,$(DEFAULT_KLDFLAGS)))
# Internal C flags that should not be changed by the user.
override
-
-
-std=gnu11 \
-ffreestanding \
-fno-stack-protector \
-fno-stack-check
-fno-lto
-
-
-
-
-
-mno-
-mno-
-mno-
# Internal C preprocessor flags that should not be changed by the user.
override KCPPFLAGS := \
-MMD \
-MP
# Internal linker flags that should not be changed by the user.
override
-
-
-
-z text \
-z max-page-size=0x1000 \
-T linker.ld
# Internal nasm flags that should not be changed by the user.
override
-Wall \
-f elf64
# Use "find" to glob all *.c, *.S, and *.asm files in the
# object and header dependency file names.
override
override
override
override
override HEADER_DEPS := $(addprefix obj/,$(CFILES:.c=.c.d) $(ASFILES:.S=.S.d))
# Default target.
.PHONY: all
all: bin/$(KERNEL)
# Link rules for the final kernel executable.
# The magic printf/dd command is used to force the final ELF file type to ET_DYN.
# GNU binutils, for silly reasons, forces the ELF type to ET_EXEC even for
# relocatable PIEs, if the base load address is non-0.
# See https://sourceware.org/bugzilla/show_bug.cgi?id=31795 for more information.
bin/$(KERNEL): GNUmakefile linker.ld $(OBJ)
mkdir -p "$$(dirname $@)"
$(KLD) $(OBJ) $(KLDFLAGS) -o $@
printf '\003' | dd of=$@ bs=1 count=1 seek=16 conv=notrunc
# Include header dependencies.
Line 313 ⟶ 355:
# Compilation rules for *.c files.
obj/%.c.o: src/%.c GNUmakefile
mkdir -p "$$(dirname $@)"
$(KCC) $(KCFLAGS) $(KCPPFLAGS) -c $< -o $@
# Compilation rules for *.S files.
obj/%.S.o: src/%.S GNUmakefile
mkdir -p "$$(dirname $@)"
$(KCC) $(KCFLAGS) $(KCPPFLAGS) -c $< -o $@
# Compilation rules for *.asm (nasm) files.
obj/%.asm.o: src/%.asm GNUmakefile
mkdir -p "$$(dirname $@)"
nasm $(KNASMFLAGS) $< -o $@
# Remove object files and the final executable.
.PHONY: clean
clean:
rm -rf
</syntaxhighlight>
===limine.cfg===
Line 334 ⟶ 379:
This file is parsed by Limine and it describes boot entries and other bootloader configuration variables. Further information [https://github.com/limine-bootloader/limine/blob/trunk/CONFIG.md here].
<
# Timeout in seconds that Limine will use before automatically booting.
TIMEOUT=5
# The entry name that will be displayed in the boot menu.
:myOS
#
PROTOCOL=limine
# Disable KASLR (it is enabled by default for relocatable kernels)
KASLR=no
# Path to the kernel to boot. boot:/// represents the partition on which limine.cfg is located.
KERNEL_PATH=boot:///boot/myos
# Same thing, but with KASLR.
:myOS (with KASLR)
PROTOCOL=limine
KERNEL_PATH=boot:///boot/myos
</syntaxhighlight>
===Compiling the kernel===
We can now build our example kernel by running '''make'''. This command, if successful, should generate, inside the '''bin''' directory, a file called '''myos
===Compiling the kernel on macOS===
''If you are not using macOS, you can skip this section.''
The macOS Xcode toolchain uses Mach-O binaries, and not the ELF binaries required for this Limine-compliant kernel. A solution is to build a [[GCC Cross-Compiler]], or to obtain one from [https://brew.sh homebrew] by installing the '''x86_64-elf-gcc''' package. After one of these is done, build using '''make CC=x86_64-elf-gcc LD=x86_64-elf-ld'''.
===Creating the image===
Line 363 ⟶ 423:
These are shell commands. They can also be compiled into a script or Makefile.
<
# Download the latest Limine binary release for the 7.x branch.
git clone https://github.com/limine-bootloader/limine.git --branch=
# Build "limine
make -C limine
Line 374 ⟶ 434:
# Copy the relevant files over.
mkdir -p iso_root/boot
cp -v
mkdir -p iso_root/boot/limine
cp -v limine.cfg limine/limine-bios.sys limine/limine-bios-cd.bin \
limine/limine-uefi-cd.bin iso_root/boot/limine/
# Create the EFI boot tree and copy Limine's EFI executables over.
mkdir -p iso_root/EFI/BOOT
cp -v limine/BOOTX64.EFI iso_root/EFI/BOOT/
cp -v limine/BOOTIA32.EFI iso_root/EFI/BOOT/
# Create the bootable ISO.
xorriso -as mkisofs -b boot/limine/limine-bios-cd.bin \
-no-emul-boot -boot-load-size 4 -boot-info-table \
--efi-boot boot/limine/limine-
-efi-boot-part --efi-boot-image --protective-msdos-label \
iso_root -o image.iso
# Install Limine stage 1 and 2 for legacy BIOS boot.
./limine/limine bios-
</syntaxhighlight>
====Creating a hard disk/USB drive image====
In this example, we'll create a [[GPT]] partition table using '''
This example is more involved and is made up of more steps than creating an ISO image.
Line 396 ⟶ 464:
These are shell commands. They can also be compiled into a script or Makefile.
<
# Create an empty zeroed
dd if=/dev/zero bs=1M count=0 seek=64 of=image.hdd
# Create a GPT partition table.
# Download the latest Limine binary release for the 7.x branch.
git clone https://github.com/limine-bootloader/limine.git --branch=v7.x-binary --depth=1
# Build "limine" utility.
make -C limine
# Install the Limine BIOS stages onto the image.
./limine/limine bios-
#
# Make relevant subdirectories.
mmd -i image.hdd@@1M ::/EFI ::/EFI/BOOT ::/boot ::/boot/limine
# Copy over the relevant files.
mcopy -i image.hdd@@1M bin/myos ::/boot
mcopy -i image.hdd@@1M limine.cfg limine/limine-bios.sys ::/boot/limine
mcopy -i image.hdd@@1M limine/BOOTX64.EFI ::/EFI/BOOT
mcopy -i image.hdd@@1M limine/BOOTIA32.EFI ::/EFI/BOOT
</syntaxhighlight>
==Conclusions==
If everything above has been completed successfully, you should now have a bootable ISO or hard drive/USB image containing your 64-bit higher half Limine protocol-compliant kernel and Limine to boot it. Once the kernel is successfully booted, you should see
== See Also ==
Line 451 ⟶ 507:
* [https://github.com/limine-bootloader/limine/blob/trunk/PROTOCOL.md Limine protocol specification]
* [https://github.com/limine-bootloader/limine-
[[Category:Bare bones tutorials]]
[[Category:Bootloaders]]
[[Category:C]]
|