Import all CowBite Spec content

[exelotl]

This adds all the content from the original CowBite Spec.

• Cross references are all preserved correctly as far as I'm aware.
• Formatting is as good as I could get in a weekend, but note that I had to use a lot of HTML to get good results.
  • Markdown offers no mechanism for having anchor IDs that differ from their titles. We could probably fix this by switching to RST See note at bottom.
  • Markdown tables absolutely suck so I had to cram every row onto one line and use a lot of HTML. We could fix this by switching to RST or AsciiDoc.
  • Some preformatted text has been copied directly from the original document because it was the simplest way I could find to preserve the register layout diagrams. This makes heavy use of obsolete HTML tags (<FONT>) but it looks pretty decent for now. It could always be improved in the future.

The following changes to the CowBite content have been made:

• Replaced requests to email the original author with requests to send us a PR.
• Removed "Not yet implemented in cowbite" and similar annotations.
• Memory address hex values are now 8 digits instead of 7.
• Added the CowBite intro but removed or reworded some obsolete / irrelevant parts.
• Removed the CowBite "Links" and "Misc" pages.
• Renamed some registers to the names that Tonc and GBATEK use

Next steps following this PR:

• Move mid-page credits (e.g. "Thanks to Kay for supplying these transfer statistics!") into the Acknowledgements page.
• Figure out what to do with overview.md (I removed it from the TOC for now, but it seems to have a mix of content from intro.md and memory.md)
• Figure out what to do with the audio content (I removed it from the TOC for now, it overlaps heavily with the audio stuff in registers.md)
• Figure out if/how we want to move things around - for example, do we want to move the register descriptions into their respective pages? (e.g. DISPCNT goes in graphics, BGxOFS goes in backgrounds, sound registers go into audio section?)
• Clean up the HTML, figure out how to add custom stylesheets for colours.
• Add missing content - BIOS needs a lot of attention!
• Check for broken links.

Note: CowBite packs a lot of info into its headings which leads to ugly anchors such as #0x040000b0---reg_dma0sad-dma0-source-address-write-only. Besides HTML, AsciiDoc is the only format I saw that provides a solution for this (letting you choose exactly what anchor a heading gets). Is having short anchors such as #REG_DISPCNT important to us? Maybe the solution is just to come up with shorter headings.

[AntonioND]

do we want to move the register descriptions into their respective pages?

I think this can be useful, I can't think of anything that doesn't fit in one category.

Is having short anchors such as #REG_DISPCNT important to us?

I think so, normally I send links to gbatek with the right anchor to the part I'm interested in showing. Maybe we can remove the extra information from the title of the section? Not sure how it would look like.

[avivace]

Note: CowBite packs a lot of info into its headings which leads to ugly anchors such as #0x040000b0---reg_dma0sad-dma0-source-address-write-only. Besides HTML, AsciiDoc is the only format I saw that provides a solution for this (letting you choose exactly what anchor a heading gets). Is having short anchors such as #REG_DISPCNT important to us? Maybe the solution is just to come up with shorter headings.

Yes, I think we should have shorter titles (and anchors). Linking directly to a paragraph (e.g. a registry) is a basic feature I would expect from a documentation resource

[exelotl]

Yes, I think we should have shorter titles (and anchors). Linking directly to a paragraph (e.g. a registry) is a basic feature I would expect from a documentation resource

Should it be possible for a title like "Display Control Register" to have an anchor like #dispcnt (the actual name of the register), or would #display-control-register suffice?

[AntonioND]

Yes, I think we should have shorter titles (and anchors). Linking directly to a paragraph (e.g. a registry) is a basic feature I would expect from a documentation resource

Should it be possible for a title like "Display Control Register" to have an anchor like #dispcnt (the actual name of the register), or would #display-control-register suffice?

As long as it's not too long and with weird numbers and symbols, I think it's fine.

[avivace]

Yes, I think we should have shorter titles (and anchors). Linking directly to a paragraph (e.g. a registry) is a basic feature I would expect from a documentation resource

Should it be possible for a title like "Display Control Register" to have an anchor like #dispcnt (the actual name of the register), or would #display-control-register suffice?

I think #display-control-register is good enough. I'll start merging this and we can work on the anchors / h2/h3 names on another PR