<jason1>
rjo, sb0: from 2019-01-29: "<rjo> and can you ping other devices in the same (ip and vlan) network as the kc705? 21:50 <rjo> jason1_: a couple suggestions: make sure the router interface is gigabit. make sure the router interface is up. did you check the leds as requested yesterday? what were the results? do you see arp responses? did you check the uart as suggested yesterday? what were the results there? try connecting the rj45 cable
<jason1>
I can ping kc705 now. Thanks!
<jason1>
I went through process of upgrading my interface driver so that it could do 1Gbit. But as I read Sebastien later on it is not necessary. It worked with both speed settings.
hartytp has quit [Quit: Page closed]
<sb0>
_florent_: SYNCOUT is a differential signal, no?
<sb0>
LVDS
<sb0>
_florent_: with that patch the different links will see different SYNC. is that not a problem? also (but less importantly) duplicating MultiReg uses some resources for nothing.
<sb0>
_florent_: i.e. sometimes, some links will begin ILAS one SYSREF period earlier than others. this sounds like a recipe for insufferable intermittent DAC initialization bugs.
m4ssi has joined #m-labs
jason1 has quit [Ping timeout: 256 seconds]
m4ssi has quit [Remote host closed the connection]
zng_ has quit [Ping timeout: 272 seconds]
zng has joined #m-labs
<_florent_>
sb0: for SYNCOUT, i was just saying that the polarity is inverted internally, that's why you were suspecting an issue, but it's fine
<_florent_>
sb0: you can mode the MultiReg in Core and pass it the to the LinkTX modules
<_florent_>
sb0: but the potential issue with that is not a variation of one SYSREF but a Device cycle
<_florent_>
sb0: i still don't explain with that the variation you see
zng has quit [Quit: ZNC 1.8.x-nightly-20181211-72c5f57b - https://znc.in]