sb0 changed the topic of #m-labs to: https://m-labs.hk :: Mattermost https://chat.m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
daveshah has quit [Ping timeout: 240 seconds]
rohitksingh has joined #m-labs
daveshah has joined #m-labs
airwoodix1 has joined #m-labs
airwoodix has quit [Ping timeout: 256 seconds]
airwoodix1 is now known as airwoodix
rohitksingh has quit [Ping timeout: 260 seconds]
<mtrbot-ml> [mattermost] <sb10q> @rjo 600MHz DDS clock
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 260 seconds]
rohitksingh has joined #m-labs
mumptai_ has joined #m-labs
mumptai has quit [Ping timeout: 260 seconds]
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
rohitksingh has quit [Ping timeout: 260 seconds]
rohitksingh has joined #m-labs
plonk has quit [Read error: Connection reset by peer]
plonk has joined #m-labs
plonk has quit [Read error: Connection reset by peer]
plonk has joined #m-labs
plonk has quit [Read error: Connection reset by peer]
plonk has joined #m-labs
<rjo> sb0: maybe the io_update tuning range with the oserdes is not sufficient for that configuration. since t_sync_clk/t_rtio is not 2 but 1.
<mtrbot-ml> [mattermost] <sb10q> @rjo that's just using the RTIO PHY, no? it should handle going to the next coarse cycle
<mtrbot-ml> [mattermost] <sb10q> @rjo on the other hand there's this comment "assumes a maximum t_SYNC_CLK period" in measure_io_update_alignment()
<mtrbot-ml> [mattermost] <sb10q> what is that maximum and is it met with 600MHz DDS clock?
<rjo> sb0: i don't remember. please read the code.
<mtrbot-ml> [mattermost] <sb10q> there's also this "t = now_mu() + 8 & ~7" that looks hardcoded for a certain frequency ratio
<mtrbot-ml> [mattermost] <sb10q> in the same function ...
<mtrbot-ml> [mattermost] <sb10q> @astro what's the verdict, should I replace the flash chips on the first zc706?
Eldra has joined #m-labs
rohitksingh has quit [Ping timeout: 260 seconds]
mumptai_ has quit [Read error: Connection reset by peer]
mumptai_ has joined #m-labs
zkms is now known as __builtin_trap
ohsix_ has joined #m-labs
ohsix has quit [Ping timeout: 265 seconds]
plonk has quit [Ping timeout: 265 seconds]
plonk has joined #m-labs
plonk has quit [Ping timeout: 265 seconds]
plonk has joined #m-labs
plonk has quit [Ping timeout: 260 seconds]
plonk has joined #m-labs
plonk has quit [Ping timeout: 258 seconds]
plonk has joined #m-labs
lkcl_ has quit [Quit: Leaving]
lkcl_ has joined #m-labs
plonk has quit [Ping timeout: 256 seconds]
plonk has joined #m-labs
plonk has quit [Read error: Connection reset by peer]
plonk has joined #m-labs
nengel has quit [Ping timeout: 240 seconds]
plonk has quit [Quit: ZNC - 1.6.0 - http://znc.in]
plonk has joined #m-labs
Eldra has quit [Ping timeout: 256 seconds]
Eldra has joined #m-labs
Stormwind_mobile has quit [Remote host closed the connection]
proteus-guy has quit [Ping timeout: 256 seconds]
Stormwind_mobile has joined #m-labs
nengel has joined #m-labs
rohitksingh has joined #m-labs
proteus-guy has joined #m-labs
proteus-guy has quit [Max SendQ exceeded]
proteusguy has quit [Ping timeout: 265 seconds]
awygle is now known as awygle_working
proteusguy has joined #m-labs
proteus-guy has joined #m-labs
awygle_working is now known as awygle
rohitksingh has quit [Remote host closed the connection]
rohitksingh has joined #m-labs
rohitksingh has quit [Remote host closed the connection]
rohitksingh has joined #m-labs
rohitksingh has quit [Remote host closed the connection]