<cr1901_modern>
Okay, I think I see... all I/O has to be done via Instance classes. This is going to be very weird generating Migen => EDIF plus UCF => IceStorm
<sb0>
cr1901_modern, what is weird about it? all a EDIF file is is blackboxes connected together. Instances fit perfectly.
<sb0>
whitequark, do you know why conda sometimes fails with "fatal: destination path '/var/lib/buildbot/slaves/debian-stretch-amd64-2/miniconda/conda-bld/artiq-kc705-nist_clock_1491023827445/work' already exists and is not an empty directory."
<sb0>
this is what is happening right now
<sb0>
whitequark, well, for the "sometimes" part, it turns out conda leaves a ton of rubbish in /var/lib/buildbot/slaves/debian-stretch-amd64-2/miniconda/conda-bld, and sometimes the new rubbish conflicts with the old
<sb0>
bb-m-labs, force build --revision=0cda1a3d3415a2ca7109c9a2ffb5ce6844ca4ad9 artiq
<bb-m-labs>
build forced [ETA 39m27s]
<bb-m-labs>
I'll give a shout when the build finishes
<sb0>
bb-m-labs, force build artiq
<bb-m-labs>
The build has been queued, I'll give a shout when it starts
Gurty has quit [Quit: Kooll ~o~ datalove <3³\infty]
Gurty has joined #m-labs
Gurty has joined #m-labs
Gurty has quit [Changing host]
felix_ has quit [Ping timeout: 246 seconds]
felix_ has joined #m-labs
<cr1901_modern>
sb0: I thought the edif backend could be used to bypass verilog generation completely as an input to yosys and friends
kaalia has joined #m-labs
<GitHub>
[artiq] tballance commented on issue #585: I have drafted a conda recipe for a simple stripped down version of artiq which includes (entry points for) only those bits needed on 'remote' rpc servers:... https://github.com/m-labs/artiq/issues/585#issuecomment-290953656