Sean Cross

Those pins are only tri-stated when they're inputs. When they're outputs, they should reflect the value of MOSI. It's not ideal at all, but it shouldn't be an issue as...

The MMU shouldn't be an issue as long as `$satp` is 0. Even so, I'm not sure if I'll keep it in future builds. Are you running with the debug...

I feel that a lot of the platform-specific stuff could be added to the `Platform` constructor. Having it add the `crg`, and perhaps populating a `list` of all of the...

I think the intention of VID:PID is to identify a particular device, so it would make most sense to have each platform use its own. Similarly, it would make the...

That looks like a good approach. I look forward to being able to try it out.

Incidentally, and apropos of nothing, how does resource utilization change if you set the CSR width to 32 instead of the default of 8? ```patch --- a/hw/foboot-bitstream.py +++ b/hw/foboot-bitstream.py @@...

That's about what I expected. And does it change much when you mess around with `--seed`? In Fomu, they're basically indistinguishable.

Interesting, thanks for doing that! That's really good data.

I'm unsure of how to correctly handle this. We don't actually include Python. We include enough of Python to support nextpnr, which requires Python to support multiple clock domains. Unfortunately,...

I do think @mithro has a good idea here. `fpga-toolchain` has settled into a steady-state now and appears to be functional. And is certainly more up-to-date. Does that package have...