"But where should I put my SoC's boot up code to initialize shit and read the boot device?"
In a ROM chip mapped to address 0 and unmapped when jumping to the boot sector, you dumb dumb
@sir If you don't mind I am going to formalize this all into a 1-2 page specification.
@alexbuzzbee please do
@sir Okay, took a little longer than expected to get it up on the server. I ended up having to complicate the "stash useful information in registers" step somewhat because there is no universal fixed set of useful values or register names. I made an in-memory data structure for information like host controller addresses and memory maps and "which boot device." Also I gave the boot block a fixed length of 4K so you can fit enough code. Thoughts?
@alexbuzzbee can you post your draft in the form of an email to ~firstname.lastname@example.org, for easier reviewing?
@sir There are tables and stuff that really don't render well in plain text. I've tried my hardest to keep my HTML as simple as possible. Do you want me to send an HTML email or try to bludgeon it into plain?
@alexbuzzbee bludgeon it into plain would be great. It's not a big deal if some of the formatting is lost, it's just a better medium for discussion.
@sir I get that. Working on getting it somewhat readable...
@sir Okay there's a little ragged alignment in the tables but it's pretty much okay.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!