andybui01/owos

💾 another hobby OS

owOS

check out:

• https://wiki.osdev.org/
• /r/osdev
• osdev forums
• i386 programmer's manual

Prerequisites (needs updating)

• vnc
• cross compiler: https://wiki.osdev.org/GCC_Cross-Compiler

Current Features

• Basic terminal support
• Keyboard inputs
• Paging
• Heap management (malloc/free)
• Userspace

Coming soon

• Graphics
• Multiprocessing
• File system

Debug

Run QEMU and listen for GDB connections via ./gdb.sh. Then, in another terminal instance, execute ./debug.sh. This opens gdb and connects to localhost:1234, as well as loads the symbol file generated by gdb.sh. Set break points with break before running the OS via continue (it automatically stops at the start).

NOTE: This is all for a VNC setup, so if you're using VNC, make sure to boot into the OS on VNC after you enter continue in gdb, to get the OS running, for real.

owos's Issues

sort out integer sizes to allow flexiblity for 32-bit PAE or 64-bit

Currently everything is done using uint32_t, while this is fine for 32-bit systems, there is zero flexibility for PAE or 64-bit address spaces. Perhaps better to use vaddr_t, paddr_t, etc. and then typedef according to system...

switch to VESA and use a framebuffer

Create auto config

Ideally, it'll include these constants:

• KMEM_BASE
• KMEM_EXT
• Some debugging levels?
• etc.

refactor

refactor and follow the linux kernel style.

some stuff to think about:

• function signatures with void parameters should be function(void) not function()
• change all ints to clearer typedefs in stdint.h, use smaller sized ints if possible

create standardized way to test OS functionality

Some good stuff to have:

• assert
• test scripts?
• easy-to-write unit tests

Consolidate scripts under makefile

Currently there are too many scripts, and they can be moved inside the Makefile, allowing for a much cleaner build interface.