03:04 <sb0> rjo, did you test the DAC monitoring after the SPI and AD53xx changes?

03:13 <sb0> rjo, it's broken...

03:15 <sb0> ah, no, the example is

03:20 <sb0> it works now

03:20 <GitHub-m-labs> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/a20dfd9c001c...8d62ea228856

03:20 <GitHub-m-labs> artiq/master 8d62ea2 Sebastien Bourdeauducq: examples: fix KC705 ad53xx

03:20 <GitHub-m-labs> artiq/master c3f763e Sebastien Bourdeauducq: dashboard: also create monitoring widgets for the Zotino class

03:20 <GitHub-m-labs> artiq/master d6a63ad Sebastien Bourdeauducq: RELEASE_NOTES: formatting

04:01 <bb-m-labs> build #1388 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1388

04:27 <bb-m-labs> build #808 of artiq-win64-test is complete: Warnings [warnings python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/808 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>

04:31 <bb-m-labs> build #2222 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2222

04:34 <GitHub146> [smoltcp] dlrobertson commented on issue #180: Ah, good point. Updated. https://github.com/m-labs/smoltcp/pull/180#issuecomment-375944865

06:59 <GitHub156> [smoltcp] dlrobertson commented on issue #182: If `std::time::Duration` was moved to `std`, should we still roll our own `Duration` or should we just use the one provided in `core`? https://github.com/m-labs/smoltcp/issues/182#issuecomment-375949922

12:37 <GitHub109> [smoltcp] whitequark commented on issue #182: That's a good question! The `core` one has way too much resolution and is twice as big, so I'd say let's keep ours. We can always deprecate it. https://github.com/m-labs/smoltcp/issues/182#issuecomment-375967348

13:28 <GitHub98> [smoltcp] dlrobertson commented on issue #182: :+1: makes sense https://github.com/m-labs/smoltcp/issues/182#issuecomment-375970549

15:00 <sb0> rjo, what is the status of the timing problems on kasli? should I look into that?

15:57 <rjo> sb0: i tried a few different dcache/icache configs (didn't see anything that i understood) and killing the interrupts (helped a bit)

15:57 <rjo> sb0: iirc rohitksingh said he wanted to look into it a few months ago as well.

16:00 <rjo> sb0: help would be greatly appreciated

16:39 <GitHub59> [smoltcp] astro opened issue #183: Implement IPv4 option headers https://github.com/m-labs/smoltcp/issues/183

20:32 <GitHub-m-labs> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/87c2f119a5d7307118137d1d8205426e8c89b872

20:32 <GitHub-m-labs> artiq/master 87c2f11 whitequark: artiq_devtool: add load action.

21:11 <GitHub179> [smoltcp] astro commented on issue #129: > For example, there could be a Nat<D> type which wraps a Device and implements Device. Any IP packets sent from the underlying device get their source endpoint mapped to some global endpoint before being sent from the Nat. And vice-versa for incoming packets sent to the Nat.... https://github.com/m-labs/smoltcp/issues/129#issuecomment-376003857

21:12 <bb-m-labs> build #1389 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1389

21:38 <bb-m-labs> build #809 of artiq-win64-test is complete: Warnings [warnings python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/809 blamelist: whitequark <whitequark@whitequark.org>

21:41 <bb-m-labs> build #2223 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2223