sb0_ changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
proteusguy has quit [Ping timeout: 246 seconds]
m4ssi has quit [Remote host closed the connection]
proteusguy has joined #m-labs
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<sb0> hartytp: let's make a block diagram of the whole clock recovery/PLL/DDMTD system
_whitelogger has joined #m-labs
proteusguy has quit [Ping timeout: 245 seconds]
proteusguy has joined #m-labs
futarisIRCcloud has joined #m-labs
m4ssi has joined #m-labs
mumptai_ has joined #m-labs
mumptai has quit [Ping timeout: 240 seconds]
proteusguy has quit [Ping timeout: 245 seconds]
proteusguy has joined #m-labs
m4ssi has quit [Remote host closed the connection]
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<sb0> rjo: are the user_led really important in VLBAIMaster and VLBAISatellite?
proteusguy has quit [Ping timeout: 255 seconds]
early` has joined #m-labs
early has quit [Ping timeout: 1042 seconds]
<bb-m-labs> build #2467 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2467
<bb-m-labs> build #2943 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2943 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
kuldeep has quit [Read error: Connection reset by peer]
kuldeep has joined #m-labs
hartytp has joined #m-labs
<hartytp> sb0: yes, I'll try to do that this weekend
<hartytp> related, I'd like to write up my notes on DRTIO clocking somewhere upstream (otherwise I have to keep going back to the source code and UGs to remind myself how it works each time I have an issue)
<hartytp> maybe add a BD as well
<hartytp> where would you want to see that kind of thing? Master manual? Wiki?
hartytp has quit [Quit: Page closed]
<rjo> sb0: can go if the sfp leds are there
<sb0> rjo: the SFP LEDs indicate DRTIO link status
<sb0> hartytp: thanks
<sb0> hartytp: in the manual
<sb0> hartytp: by the way, have you looked at the current DRTIO synchronization performance with the Si5324?
hartytp has joined #m-labs
<hartytp> sb0: may be able to do that on monday
<hartytp> usual snafu with sayma: none of our boards work in the rack right now
<hartytp> joe sent me two AMCs, one has a sticker saying 3v3 broken but seems to work fine
<hartytp> the other one doesn't turn on even out of the rack
<hartytp> need to upgrade vivado
<hartytp> etc
<sb0> yeah, that's still going on...
<hartytp> what do you think about the idea of unifying "sayma on a eurocard" with "fast Kasli servo"?
<sb0> we need to get WUT to identify the exact causes of those broken boards, I suspect not all of it is "damaged during transport" and it'll bite us again in v2
<hartytp> yes
<hartytp> but, there comes a point when it's best to just get on with v2.0
<hartytp> even if it has bugs
<hartytp> debugging on v2.0 and then moving quickly onto 2.1 may be more efficient than debugging onto v1.0
<sb0> hmm... those problems have been wasting a lot of dev time
<hartytp> yes
<hartytp> fwiw, I've been really impressed with how creotech are handling booster
<hartytp> that gives me some hope that they will find and fix at least some of the remaining issues before shipping sayma to us
hartytp has quit [Quit: Page closed]
proteusguy has joined #m-labs
kc5tja has quit [Quit: leaving]
davidc__ has quit [Ping timeout: 250 seconds]
m4ssi has joined #m-labs
m4ssi has quit [Remote host closed the connection]
<_whitenotifier-9> [nmigen] alsrgv commented on commit 4948162f33d2b083acdbeb72e528438f5d27a7c1 - https://git.io/fhbmN
davidc__ has joined #m-labs
cr1901_modern has quit [Ping timeout: 250 seconds]