avOS

[vestal halo]

my little non-unix and non-nt OS from scratch with a 2 stage BIOS bootloader https://github.com/kevinalavik/avOS

currently doing logging rework

its 64bitr higher half kernel

[silver patrol]

cool

[vestal halo]

repo is currently private

i might make it puiblic once the code is clean enough lol

the kernel and stage2 is loaded of a FAT32 image

[tall bolt]

not to minimod but it is a rule you can't show off closed-source stuff

[vestal halo]

ah well, i just made it private by mistake, i realised that yesterday when i made the repo. I will make it public asap

aka after logging rework

thanks, i didnt know that

[vestal halo]

im doing acpi now, i got the rsdp so thats cool

[tall bolt]

Also reminder that there's no real reason to keep things like this private aside from that, being "good enough" is arbitrary

[vestal halo]

yeye, it was a bad excuse for my lazyness

[vestal halo]

supports both text mode aswell as VESA framebuffer (havent tested on real hw)

therre we goo

here is it with framebuffer and flanterm

boot loader logging (disabled by default)

[vestal halo]

https://github.com/kevinalavik/avOS

there we go

now imma parse rsdp to get the xsdt and jfor now eonly print the acpi tables

there we go

[uncut hollow]

nice lol

[vestal halo]

soo i did some work today, not updating this thread becuz im stupid

but now i got IRQs (apic) and a vfs aswell as ATA driver (fat32, read-only) and a kernel shell (yes ik, kill me)

the vfs follows a design i made up in my head

im doing a kernel shell becuz im activly avoiding smp and scheduiling

[plucky summit]

is this AI again 😭

some comments are sus

[vestal halo]

no?

[vestal halo]

what

[plucky summit]

idk man i just think its weird there are no comments at all in the entire codebase then there's this

and when you compare to handwritten comments its quite different

I dont want to put out accusations or something tho, but I think you can understand how I am skeptical

[vestal halo]

becuz thats harder things

[vestal halo]

and yes the pit thing was partially fixed by ai (sadly)

[vestal halo]

i understand

[vestal halo]

but everything else is my work

[vestal halo]

so to make sure i actually understand the lba stuff and ata things i comment things. But i like a clean codebase, i clear up most comments before committing xD

idk why

its bad

becuz sometimes i come back to a piece off code wondering wtf does this do

[vestal halo]

doing graphics using the Device syscalls

also this OS is non posix (expect printf lmaoo) non unix and non nt

whole custom thing

therefore my goal is not to port things

but rather write my own thing

also devices are not on the file system

no proper mounts

i have volumes instead

boot drive gets "mounted" as volume a the ATA slave gets volume b if presenmt

which works btw :^)

[vestal halo]

im doing a wm now

and graphics toolkit

well

i got the basics

now im just trying to make so i can create apps which is acrtually managed by the wm

but i need some kind of IPC

and i need a basic font renderer

imma make a basic message system for IPC

[vestal halo]

ipc and font renderer works

[vestal halo]

with some help from codex (sadly) i figured out the best way to design the wm protocol

but it works

[vestal halo]

Adk (the graphics toolkit ive made) has two window types, one Raw (which is just a raw buffer, over shared memory) and one Text. which is used for terminal and the test app

and like a notepad and shit in the future