sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
calle__ has joined #m-labs
mumptai_ has quit [Ping timeout: 240 seconds]
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
<sb0>
rjo, for grabber, are you sure you want an interface with a gate and events that get pushed into RTIO inputs at every frame?
<sb0>
this looks a bit fragile, e.g. if you don't read the correct number of input events (because there was more than one frame, or you miscounted the enabled ROI engines) then it'll silently return incorrect values
<sb0>
this can also delay the experiment until the end of a frame, waiting for new ROI values
<sb0>
rjo, what about an interface similar to the "sample TTL input" instead, where the kernel would request the latest value of ROI engine N, and then the gateware returns it immediately?
<sb0>
rjo, is it important that all ROI engine values correspond to the same frame? if not, requesting the values one by one makes things simpler, as well