Add Booting Docs

[Sploder12]

Description

Adds documentation about the booting process

Issue #13

Type of change

• Documentation

Testing

Github's .md renderer likes it.

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[emilkovacev]

Would diagrams be out of the question? Not a must-have, but definitely useful for visualizing memory locations and how much memory each section has. We can then adopt additional diagrams when we get to allocating memory in more complex ways!

[emilkovacev]

Just a couple of small things, maybe something to keep in mind if we want to standardize docs in the future.

[emilkovacev]

I added a few small suggestions.

For some reason it seems like single \n characters are rendering in markdown (when I thought only \n\n would), stylistically I think it's easier to read as singular paragraphs.

Also, some standards suggestions:

• Registers like l0 should be put in backticks
• When referring to the size in bits or bytes, we should use the format: num-bytes or num-bits: Ex: 32-bit x86 linux

[Sploder12]

For some reason it seems like single \n characters are rendering in markdown (when I thought only \n\n would), stylistically I think it's easier to read as singular paragraphs.

\ns are not being rendered! But s are! (I really don't know why markdown decided two spaces was a good way to signify new line)

[emilkovacev]

Ah ok, that makes slightly more sense. I think we should remove those double spaces so it's formatted in paragraphs.

[emilkovacev]

Good stuff! I think this is ready for merging.