How zipleix/alpha-os works
Main Components
• Bootloader: Represented by the contents in src/boot (boot.asm) which initializes hardware and loads the kernel.
• Kernel Core: Comprised of src/kernel (kernel.asm, kernel.c, kernel.h) where the main control logic resides.
• Configuration: Highlight src/config.h, which holds configuration settings used across the kernel.
• Disk Management: Encapsulate the disk I/O logic from src/disk.
• File System: Include the file operations from src/fs; note the FAT implementation in src/fs/fat.
• Memory Management: Detail components from src/memory (heap, paging) that handle dynamic allocation, paging, and general memory tasks.
• I/O Operations: From src/io, illustrate routines for interacting with hardware I/O.
• System Call Handling: Capture the functionality in src/isr80h, which implements system call entry points (IO, memory, process, and misc routines).
• Task Management: Represent the process and task management elements found in src/task.
• Utilities: Denote additional fundamental services such as string handling (src/string) and status codes (src/status.h).
• Linker Script: Include the linker scripts (src/linker.ld, programs/*/linker.ld) to show the build and linking process.
• User-space Programs (Optional): The “programs” directory (with subdirectories like “shell”, “stdlib”, and “blank”) contains user-space programs and libraries that run on or interact with the kernel. Although secondary in purpose, they complete the ecosystem by demonstrating how applications are built to run on Alpha OS.
Relationships and Interactions
• From the Kernel Core, illustrate internal communication:
• Configuration file (src/config.h) as a component that feeds into several modules (kernel, memory, and I/O) to emphasize its global relevance.
Architectural Patterns and Design Principles
• Then, indicate how higher-level functionalities (file system, task management, and user processes) are built on top of these layers.
• Modularity since each directory (e.g., src/fs, src/memory) represents a module with clear responsibilities.
• Mention the separation of concerns, especially between hardware initialization (bootloader, GDT/IDT) and system services (kernel, memory, task scheduling).
Technologies, Frameworks, and Tools
• That GCC cross-compilation, Makefiles, and build scripts (Makefile, build.sh) are integral to the compilation and setup process.
• Mention that QEMU is used for emulation/testing. You might show an external “Emulator Environment (QEMU)” block that interacts with the compiled kernel image.
Final Touches
• Every component is connected logically, and highlight any feedback loops (e.g., hardware interrupts looping into IDT routines).