the way it'd probably work is, i'd make a super simple processor design and then see what we can do with it, then explore how we can make richer software by adding in more hardware features

and during that we'd be talking about what decisions we're making and what effect they have

i've taken a digital logic class and an OS class but they didn't approach those topics from first principles like this. it might be helpful

or it might be trash since i have zero education training :^)

heck, now i wanna get started with this

@typhlosion Can I make games for it

@typhlosion CAN I MAKE THE OS GRAPHIC AND SOUND DESIGN

@typhlosion I would certainly watch the hell out of that

@typhlosion i could maybe help? if you're interested. i've spent a lot of time working with small computer designs at the circuit level, and i've at least fiddled with making an OS. i actually started making a fantasy processor a while back but got bogged down in opcode formats

@trashbyte i've already started on a fantasy processor thing so i think i've got it locked down there... might need some help making sensible decisions on how to design other hardware components like for graphics and such. do you have any strong opinions about how interrupts should work?

and once i have the hardware, figuring out how to go about building an os on top is half the fun

@typhlosion vectored interrupts are cool, but that depends very much on the processor and peripheral design

@trashbyte my current/old fantasy processor has a 32-entry interrupt table with a special register pointing to it. i'm gonna probably scrap that whole processor design and remake it, and i'll probably just have a single vector pointing to a single handler that can check a register to see which interrupt it is

i was mainly wondering edge-triggered vs level-triggered and how the PIC should work