Event JSON
{
"id": "ea2d150e0caa7bca12929980d5b3fbe783f86499ea1640ce944dad4f19128e92",
"pubkey": "dad113f50e47d6bffb79f9a69006ffd969c26e636e5aed2ae597b0407093175f",
"created_at": 1723925155,
"kind": 1,
"tags": [
[
"e",
"b5ff3bf72338cb706e93b314e01e265f9a3c64c61dfcf1649d1ab4718ac8df7d",
"",
"reply",
"04f8915424c713657ad6ce59443d28dbdcf5832687c9af560ae388f59276a137"
],
[
"p",
"dad113f50e47d6bffb79f9a69006ffd969c26e636e5aed2ae597b0407093175f"
],
[
"p",
"04f8915424c713657ad6ce59443d28dbdcf5832687c9af560ae388f59276a137"
],
[
"e",
"77ba25bd8c3ce6cb748702bc3130c078db0af0c24a5a562695ced00e95bd3073",
"",
"root",
"dad113f50e47d6bffb79f9a69006ffd969c26e636e5aed2ae597b0407093175f"
],
[
"proxy",
"https://hachyderm.io/@danderson/112979159021329385",
"web"
],
[
"proxy",
"https://hachyderm.io/users/danderson/statuses/112979159021329385",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://hachyderm.io/users/danderson/statuses/112979159021329385",
"pink.momostr"
],
[
"-"
]
],
"content": "Depends a lot on the bus timing requirements from the CPU. Roughly, with an async bus, the fastest the FPGA can turn around a read request is 3 cycles of its main clock (2 for clock domain crossing, 1 for memory access assuming no contention). I think ideally 4 cycles would be better, that'd allow for another layer of registers on the output to shorten the data paths.\n\nOn the 65C816, looks like reads need to be turned around in 0.5 PHI2 cycles. So, 3-4 cycles per half-PHI2.",
"sig": "6eada7a9cea26fea4b919edec6e6aa23e8bcfac6db10426072ccb4777f4d7e70d7fa153a61bf6fae2a80089097b38781e401e68e5a14baf4b85269bfd63053b9"
}