Viewing profile — noone_youknow

This is open-source hardware, caveat emptor is implied. At this stage in a project like this, I’d expect the people who were getting boards fabbed to also have the skills to sanity…

For me, one of the saddest side-effects of modern generative AI is this apparent rise in an attitude of “I don’t know how to do this, therefore anyone who does this must have just …

It isn’t, actually.

There would likely be value in a POSIX layer as you describe, at least from the point of view of porting existing programs. And perhaps it will happen, if I get far enough along, b…

Thank you! A project like this is all about compounding small wins for sure, just building one thing on top of the previous thing until (hopefully) one day it’s a complete thing :D…

I agree that for it to be generally useful, it’ll need to be easy to port existing software to. But I don’t think I’ll need a translation layer at the syscall level (unless I want …

Haha that quote felt pretty much obligatory :D Non-POSIX is definitely keeping things fun, letting me explore different ideas without having to fit into an existing interface desig…

Thanks! I haven't thought much about long term to be honest, right now my immediate goal is to get enough USB HID to be able to make it interactive, with the medium term goal of po…

> We live in an age of AI overinvestment. I would reserve judgement until they prove they actually have something. Haha yes, that's a very fair comment!

There's ideas in here from various other kernels - some of the capability stuff is inspired by (but simpler than) seL4, and the message passing IPC and how I'll avoid priority inve…

That's a good way to look at it, and on reflection I feel the same way. It's certainly useful _to me_ and has helped me really nail down concepts I thought I already understood, bu…

Ahem, well, that's embarrassing! :D

I pretty much always have a kernel project going on, and have been that way for decades. Over the past couple of years, that's been Anos, which has gotten further along than any of…

It is hard, and things are messy in some areas. But in my experience it’s less hard than writing a lot of the existing documentation would’ve been (because good datasheets and docu…

This is really great work! Always impressed to see hobby OS projects that get this far, well done. That said, I’m once again reminded that we sorely need some updated resources for…

Well put! This succinctly sums up the crux of my argument in my other comments.

Even taking only x86_64 as an example, going from real to long modes is primarily of concern to those writing firmware these days - a modern operating system will take over from UE…

While I agree this might be a fun resource and useful example code for various aspects of legacy x86 interfacing, I would urge anyone who hopes to actually get into OS development …

Sorry for the confusion, I was referring to the putchar not being implemented in OPs code, I got yours working right away (nice work btw). What you mention about VGA being common o…

Thanks! I see that you’re using the SBI routines, which is what I was expecting here but couldn’t find - the reference to “output text to VGA” in the post made me curious. I did se…

Nice work! Looks like most of the basics are covered, and meanwhile in my current kernel the RISC-V entrypoint is >700 lines (of C) just to get to the arch-independent entrypoint! …

Same here. I got a Bambu X1C and have been very happy with it.

Thank you! At this early stage, the filesystem exists only to prove the disk drivers and the IPC interfaces connecting them. I chose FAT32 for this since there has to be a FAT part…

> It's a bit disappointing that every time somebody decides to write their own kernel, the first thing they do is implement some subset of the POSIX spec. Well, not quite _every_ t…