00:47
rohitksingh-demo has joined #m-labs
00:53
rohitksingh has joined #m-labs
01:34
rohitksingh-demo has quit [Quit: Leaving.]
01:49
<
sb0 >
whitequark, because all sayma variants use the same rtm gateware.
01:50
<
sb0 >
whitequark, please don't merge them like this
02:49
futarisIRCcloud has joined #m-labs
03:11
rohitksingh has quit [Quit: Connection closed for inactivity]
04:00
<
GitHub173 >
[artiq] sbourdeauducq commented on issue #883: ``get_rtio_counter_mu`` seems to be working fine. Likely a runtime bug (parallel programming with async RPCs? core device memory corruption when dealing with the large array?) or miscompilation (though compilation is a pretty deterministic process and this bug is intermittent). @whitequark
https://github.com/m-labs/artiq/issues/883#issuecomment-361036588
04:03
Ultrasauce has quit [Quit: No Ping reply in 180 seconds.]
04:05
Ultrasauce has joined #m-labs
04:15
_whitelogger has joined #m-labs
10:29
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
11:55
<
whitequark >
sb0: I am not convinced
11:56
<
sb0 >
whitequark, what do you propose?
11:56
<
whitequark >
what I just did
11:56
<
whitequark >
building the RTM gateware is very quick
11:56
<
sb0 >
ship the same copy of the RTM bitstream in every package?
11:56
<
sb0 >
it's quick now because it doesn't do a lot, but it will get bigger
11:57
<
sb0 >
probably will take about the same time as the current kasli drtio satellite target
11:58
<
whitequark >
well okay but then there is no good way to make a single artiq_flash sayma target.
11:58
<
whitequark >
so I am not going to do that.
11:58
<
sb0 >
why do you want a single artiq_flash sayma target?
11:59
<
whitequark >
jbqubit insisted on one...
12:00
<
sb0 >
I can see two alternatives: 1. two commands to flash sayma 2. an ad-hoc option into artiq_flash that runs those same two commands in turn
12:00
<
whitequark >
you can't specify two --srcbuild options at once
12:00
<
sb0 >
sure, in that case don't use the ad-hoc option
12:00
<
sb0 >
go with the two artiq_flash invokations
12:01
<
whitequark >
what a pain in the ass
12:01
<
whitequark >
everything about sayma is user-hostile and you insist on making it worse
12:02
<
sb0 >
adding 15 minutes to every bitstream build for the RTM isn't nice either
12:03
<
whitequark >
oh, I have an idea
12:03
<
sb0 >
you could disable that build maybe, though
12:03
<
whitequark >
we can have the RTM package ship three copies of the bitstream
12:03
<
sb0 >
in which case that would be fine
12:03
<
whitequark >
and put it in the folders for every variant
12:03
<
whitequark >
that would be functionally equivalent to the current situation but faster
12:04
<
sb0 >
what annoys me the most with your proposal is the increased bitstream build times, not #the minor disk space bloat
12:04
<
sb0 >
having both flashable with a single --srcbuild is nice
12:05
<
sb0 >
and having an option to disable the RTM build would solve the increased compilation time problem in an acceptable way
12:07
<
sb0 >
multiple copies of the bitstream in the RTM package doesn't sound like a good idea
12:09
<
whitequark >
then the individual AMC packages could copy the RTM bitstream out of the RTM package at build time
12:10
<
sb0 >
we might even not need a RTM package. cache the RTM bitstream outside conda?
12:10
<
whitequark >
that doesn't really work on buildbot
12:10
<
whitequark >
not reliably anyway
12:10
<
sb0 >
ok, then fine, we can do that
12:12
<
sb0 >
what in particular with sayma is user-hostile, in your opinion?
12:14
<
rqou >
i just found out that someone i know somewhat well is also working on a diy mass spectrometer
12:14
<
rqou >
I'm trying to find out more, maybe there can be some collaboration?
12:15
<
sb0 >
rqou, who's it?
12:16
<
rqou >
a former classmate
12:18
<
rqou >
I'll have more info later; I'm still checking e.g. whether this is supposed to be a secret project
12:18
<
sb0 >
is it a diy calutron?
12:21
<
whitequark >
sb0: moving parts that our tooling doesn't handle
12:21
<
sb0 >
can you be specific?
12:22
<
whitequark >
for example, the two FPGAs that have to be flashed and loaded separately. but I've just fixed that.
12:22
<
whitequark >
the conda packages that have to be built in specific precise order on the buildbot or you'll get errors
12:23
<
sb0 >
well sure, loading the RTM FPGA has been an open issue for a while
12:23
<
whitequark >
I mean with `artiq_flash load` too.
12:24
<
sb0 >
and that's not really an issue with sayma, but with setting up software/infrastructure that no one (before you) had looked into deeply
12:27
<
whitequark >
you could put it that way but the end result is that sayma is more user-hostile because of its increased complexity
13:36
_whitelogger has joined #m-labs
14:17
futarisIRCcloud has joined #m-labs
14:29
<
GitHub142 >
artiq/master 79ea454 whitequark: conda: use $SP_DIR instead of $PREFIX/lib/python3.5/site-packages. (#652)...
14:29
<
GitHub142 >
artiq/master 885ab40 whitequark: conda: split RTM and AMC packages back....
14:35
<
whitequark >
bb-m-labs: force build --props=package=artiq-sayma_rtm artiq-board
14:35
<
bb-m-labs >
build forced [ETA 18m28s]
14:35
<
bb-m-labs >
I'll give a shout when the build finishes
14:36
<
GitHub21 >
smoltcp/master c2d18ec Philipp Oppermann: Return specific sockets from `new` functions instead of `Socket`....
14:44
<
whitequark >
bb-m-labs: force build --props=package=artiq-sayma_rtm artiq-board
14:44
<
bb-m-labs >
build forced [ETA 18m28s]
14:44
<
bb-m-labs >
I'll give a shout when the build finishes
14:45
<
travis-ci >
m-labs/smoltcp#642 (master - c2d18ec : Philipp Oppermann): The build passed.
15:19
<
GitHub94 >
artiq/master 9a94482 whitequark: conda: fix typo in 885ab409.
15:19
<
GitHub184 >
artiq/master 0edc34a whitequark: artiq_devtool: the proxy artiq_flash action doesn't exist anymore.
15:32
<
travis-ci >
batonius/smoltcp#125 (master - c2d18ec : Philipp Oppermann): The build passed.
16:24
<
whitequark >
bleh, I had to scrap most of the code I wrote in the last few days
16:24
<
whitequark >
too complex and fragile
16:25
<
sb0 >
in? artiq_flash?
16:26
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
20:08
<
GitHub129 >
sinara/master 327ecdd Greg: zotino v1.1 added copper balancing
20:29
mumptai has joined #m-labs
22:37
<
rjo >
has anyone used openocd to talk to the xadc in 7 series?
22:54
<
cr1901_modern >
what's the use case?
23:38
<
GitHub37 >
[smoltcp] dlrobertson commented on pull request #125 c3c5988: The `len` used as input to `DATA` should be the result of `data[field::LENGTH]` instead of the buffer length. Also don't make the same mistake I did with ICMPv4 and make sure to check that the buffer is bigger than that before using that field.
https://github.com/m-labs/smoltcp/pull/125#discussion_r164317095