aca2cc11d2
Added RTC |
||
---|---|---|
.github/workflows | ||
grub | ||
src | ||
test | ||
.gitignore | ||
build.zig | ||
hello.jpg | ||
link.ld | ||
makeiso.sh | ||
README.md |
Pluto
Pluto is a kernel written almost entirely in Zig and supports x86, with aarch64 and x64 backends being planned.
Goals
- Should be written in Zig as much as possible. Assembly should only be used where required for functionality or performance reasons.
- Light and performant. The kernel should be usable both on embedded and desktop class CPUs, made possible by it being lightweight and modular.
- Basic utilities will be written in Zig. This includes a basic text editor and shell, and will be part of the filesystem external to the kernel itself.
- Easy to port. The kernel is oblivious to the underlying architecture, meaning that ports only need to implement the defined interface and they should work without a hitch.
All of these goals will benefit from the features of Zig.
Build
Requires a master build of Zig (downloaded or built from source) xorriso and the grub tools (such as grub-mkrescue). A qemu-system binary compatible with your chosen target is required to run the kernel (e.g. qemu-system-i386).
zig build
Run
zig build run
or if you want to wait for a gdb connection:
zig build debug-run
Debug
Launch a gdb instance and connect to qemu.
zig build debug
Test
Run the unit tests or runtime tests.
zig build test
Options
-Drt-test=
: Boolean (defaultfalse
).- build: Build with runtime testing enabled. Makes the kernel bigger and slower but tests important functionality.
- test: Run the runtime testing script instead of the unittests. Checks for the expected log statements and fails if any are missing.
-D[build-mode]=
: Boolean (defaultfalse
).- build: Build a certain build mode (release-safe, release-fast, release-small). Don't set in order to use the debug build mode.
- test: Test a certain build mode (release-safe, release-fast, release-small). Don't set in order to use the debug build mode.
Contribution
We welcome all contributions, be it bug reports, feature suggestions or pull requests. We follow the style mandated by zig fmt so make sure you've run zig fmt
on your code before submitting it.
We also like to order a file's members (public after non-public):
- imports
- type definitions
- constants
- variables
- inline functions
- functions
- entry point/init function
More styling information is available on the wiki