Initialize Interrupts

Create the framework for device interrupts and system calls.

Get interrupts to print a message onto the screen

changed milestone to %Initial Kernel

added Functionality Software labels

created branch 8-initialize-interrupts to address this issue

mentioned in merge request !48 (merged)

We need to create a handler for the IRQ which determins which interrupt to call, then jumps to that function in a jump table.

Along with RTC interrupt, we also need to support serial interrupts, like a keyboard.

Once we load into the kernel, we need to load the IRQ vector with the new address.

Perhaps we could map the IRQ and NMI vectors to the interrupt controller, since currently they are mapped to the ROM which we can't change.

Is there a better place to put this than in the big data mux?

Or should we just have this be a separate thing?

I think for now lets just have it as a separate thing, with only the IRQ vector for now, we can do nmi later.

we can hijack the reset vector as a write only control register, since the reset vector will always be from ROM.

Related quiestion, should the interrupt vectors be mapped? I don't think so.

Actually, don't do any of that. Just have the bios immediately jump to somewhere else

Pick a location and do a jmp (addr)

mentioned in commit 6bcce0d3

closed with merge request !48 (merged)