#128OS
1 messages · Page 1 of 1 (latest)
but I would recommend not yet doing keyboard and instead first going for things like an allocator and paging
I’m gonna try doing that soon
anyway good luck on your project
not necessarily, you can take the keyboard input directly (but it's weird)
Long term you should really make it interrupt-based, otherwise it'll mess things up as you get further through
I see that you are using BIOS with text mode graphics. No clue how you manage to boot this. I can't find any scripts.
and it seems to be 32-bit
according to the readme there's a single command (cos it's all in one file atm?):
i686-elf-gcc -c kernel.c -o kernel.o -std=gnu99 -ffreestanding -O2 -Wall -Wextra
Yeah I am currently writing a bootloader for this, for now I used the OSDev one but I am currently finishing my own
What's the "OSDev one"? GRUB?
No no this wouldn't probably boot on GRUB yet cause I didn't write any boot code in the kernel, the OSDev one is from bare bones, I am going to show my new BL soon
I belive OSDev barebones uses GRUB? There's one with limine, does it use that??
I just use bare kernel.bin (kernel combined with boot.s) for testing
My bootloader goal for now is to turn this into an ISO and my own bootloader
128OS
does it have 128 bits
nuh uh
Currently:
Failed paging and allocating memory, gonna post the failed code on this repo
its posted on github, if you want to see it its there
most portable C build system: /j
i am actually thinking of porting this project to cpp
I've decided to switch to CPP since its easier for me to write with and I know more of it
Hello, huge changes to this project, 128OS now is in C++ and assembly, second thing we have a virtual memory test now! The last but the most important thing, we have a temporary keyboard driver which actually works! Thanks for all the support
All of it has been released on the GitHub repo
Thanks!