<whitequark>
yes, that does seem related to the amount of code
<rjo>
well. not if you are stricken down with flu
<whitequark>
i feel better already anyway...
<rjo>
whitequark: ok. could you also quickly confirm that the two commits in phaser after the master merge are "correct" (or at least needed as a work around for now)
<rjo>
i.e. 8eff858 and 2a1e529
<whitequark>
yes, seems ok
<rjo>
whitequark: ack.
kaaliakahn has joined #m-labs
<sb0>
sigh, the mentor graphics garbage just crashes on startup in wine
<sb0>
pretty sure the DRM crippleware would be the next issue if it didn't anyway
<sb0>
rjo, what about the artiq-hardware repos?
rohitksingh has quit [Ping timeout: 260 seconds]
FabM has quit [Quit: ChatZilla 0.9.92 [Firefox 45.4.0/20160921204512]]
rohitksingh has joined #m-labs
<rjo>
i tried wine and it doesn't look easy either. (they actually bundle wine....)
<rjo>
sb0: i'll roll that thing back when greg has committed to sinara.
<sb0>
ah I was trying visECAD, which is windows-only
rohitksingh has quit [Ping timeout: 256 seconds]
rohitksingh has joined #m-labs
mithro has quit [Ping timeout: 256 seconds]
<whitequark>
rjo: ImportError: No module named 'jesd204b'
<whitequark>
rjo: cargo/or1k-unknown-none/debug/libksupport.a(ksupport.0.o):(.data.rel.ro.ref4384+0x380): undefined reference to `ad9154_init'
<whitequark>
hm
<whitequark>
oh I should be using the phaser gateware
rohitksingh has quit [Ping timeout: 256 seconds]
<rjo>
whitequark: also use the other/aux kc705. i can see a few problems with the phaser gateware on the buildbot kc705.
<rjo>
"can see" in the sense of "i'd be worried about"
<whitequark>
ack
<sb0>
rjo, I'm not sure about the "low noise" clocking plan. are we just using another PLL on Sayma instead of the one built into the 7044, or do we distribute 2.4GHz from an off-crate oscillator into the RF backplane?
<whitequark>
rjo: somethings screwy with the DNS
<whitequark>
$ ping kc705aux
<whitequark>
PING web.serverraum.org (213.133.101.245) 56(84) bytes of data.
rohitksingh has joined #m-labs
<whitequark>
rerunning dhclient fixed that
<whitequark>
now kc705aux simply has no record...
<whitequark>
rjo: what's its IP?
<rjo>
whitequark: yes. i don't know how you git that to work for the other kc705. ip is ends in 51
<whitequark>
rjo: oh. i went into the openwrt configuration thing and added a static hostname
<rjo>
whitequark: iirc i did that.
<whitequark>
hrm
<rjo>
sb0: we are using a 100->2000 MHz pll on sayma (the lock mezzanine) that's (significantly) better than a HMC7044. and we have the option of ignoring the pll mezzanine on sayma and feedint 2 GHz directly into the hmc7044/3.
<rjo>
there is no high frequency on the backplane IIRC.
<rjo>
whitequark: the dns setup is a bit weird. having lab.m-labs.hk be a public record _and_ having private hosts under that is tricky IME.
<rjo>
because you'd want the search domain to be lab.m-labs.hk then.
<rjo>
but anyway. that's a minor issue.
<whitequark>
rjo: cat /etc/resolv.conf
<whitequark>
that's exactly how it's set up
<whitequark>
anyway uh I seem to be able to run $ artiq_run artiq/examples/phaser/repository/test_ad9154_status.py ?
<rjo>
whitequark: then something changed. before it was frequently hitting the public wildcard cname.
<whitequark>
rjo: there seems to be some problem where that resolv.conf is replaced with the IPv6 name of the router
<rjo>
whitequark: let me check my toolchain versions...
<whitequark>
rjo: hang on. it doesn't seem to poke the right kc705
<whitequark>
ok I see, which ttyUSB is kc705aux on?