Data Structure for Cartridges

[PHenegan]

Cartridges need some sort of data structure, since there are multiple types of possible memory controllers on them, so implementing them isn't as simple as an array of u8 values.

This website goes over each of the different cartridge types pretty well (though it is kind of hard to read): https://www.devrs.com/gb/files/gbspec.txt (there are 26 types listed there, though some of them might be niche enough to ignore for now, or maybe be merged into one data type)

[PHenegan]

Things to prioritize:

• MBC3 and MBC5 seem like the most common for games that didn't fit use a regular 32KiB + 8KiB combination
• I should maybe add some stubs for the saving feature since that will likely go through the cartridge RAM.
• Thinks like Rumble can probably be done in a later commit if at all since it isn't too necessary
• Is the Game boy printer/camera something even worth emulating?

[PHenegan]

Another good link: https://gbdev.io/pandocs/MBC1.html

[PHenegan]

Worth noting that the constructor for these data types will kind of get into #5 - How do I want to load a ROM in through a constructor? Is it worth doing some sort of abstracted builder system? This seems like I might be making it overly complex

[PHenegan]

Closing this once I write a builder that parses the cartridge header and creates the cartridges