Update if anyone's curious,
I actually tried temporarily pulling the cape's corresponding overlay from
/lib/firmware (I think that's where it was) and booting up that way, and
SPI came back, so I believe that may solve my problem, otherwise I just
have to modify and re-build that cape.
--
For
OK, my possible understanding at this point is this:
Cape EEPROM has a name string on it.
BBB looks at that name string first and loads the matching file device tree.
For some reason, no other device tree overlays are loaded. SPI is not a
part of the overlay for this cape (confirmed by looking
