timeless11 has quit [Remote host closed the connection]
Guest84957 is now known as felix_
Nazca has joined #m-labs
Nazca has quit [Remote host closed the connection]
early has quit [Quit: Leaving]
early has joined #m-labs
mentifis19 has joined #m-labs
mentifis19 has quit [Killed (Sigyn (Spam is off topic on freenode.))]
ohama has quit [Ping timeout: 272 seconds]
ohama has joined #m-labs
richardjohn10 has joined #m-labs
richardjohn10 has quit [Read error: Connection reset by peer]
<rjo>
d_n|a: if it is indeed what I was alluding to and what sb0 was elaborating on, (the rtio_counter-as-viewed-from-kernel racing the input latency), it is just software and the gateware behavior to be documented.
<rjo>
d_n|a: the other potential pitfal (on top of the two you have hit) might be that there are input events with timestamps just outside the gate timestamps. without looking at the gatgeware i don't know whether that is in fact possible but i can see how it can happen.
<rjo>
d_n|a: ah. you might be seeing that as well. that is the only latency i would correct for in gateware here.