00:45 <GitHub-m-labs> [artiq] whitequark pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/0b4d06c7a9d7...b1d349cc1ba5

00:45 <GitHub-m-labs> artiq/master b1d349c whitequark: firmware: implement a sampling profiler....

00:45 <GitHub-m-labs> artiq/master 9857dfc whitequark: firmware: add irq::Exception to libboard.

01:19 <GitHub-m-labs> [artiq] whitequark pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/b1d349cc1ba5...4f29d9134fe1

01:19 <GitHub-m-labs> artiq/master 4f29d91 whitequark: firmware: update log_buffer....

01:19 <GitHub-m-labs> artiq/master 5ebc626 whitequark: artiq_coreprofile: fix an inverted option.

01:20 <GitHub-m-labs> [artiq] whitequark commented on issue #986: 400k cycles were spent rotating the log ring buffer in place. I am now observing exact same performance with or without aqctl_corelog. https://github.com/m-labs/artiq/issues/986#issuecomment-386769187

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

01:29 <GitHub-m-labs> [artiq] whitequark commented on issue #979: @jordens I've fixed #986. In case you manage to reproduce this, you can gather and view a profile with:... https://github.com/m-labs/artiq/issues/979#issuecomment-386769720

01:40 <bb-m-labs> build #857 of artiq-win64-test is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/857 blamelist: whitequark <whitequark@whitequark.org>

01:41 <bb-m-labs> build #2303 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2303 blamelist: whitequark <whitequark@whitequark.org>

01:44 <whitequark> sb0: what is your opinion on this migen patch? https://hastebin.com/tupeqorufu.patch

01:45 <whitequark> this lets you do e.g. `io = platform.request("io"); self.comb += [a.eq(io[0]), io[1].eq(b)]`

01:46 <whitequark> otherwise migen would declare the port as `output`, which seems obviously wrong and unexpected

01:49 <cr1901_modern> Syntactic sugar for declaring a tristate but not actually using the "enable" portion?

01:49 <whitequark> no, it just uses the verilog `inout` feature

01:49 <whitequark> you may actually want to use TSTriple anyway

01:50 <cr1901_modern> tbh, up until two days ago I just used "inout" and "tristate" interchangably

01:51 <cr1901_modern> I guess now the idea is "all tristates are inouts, but not all inouts have to be tristates"

01:56 <whitequark> read IEEE 1364.1-2005, too

01:57 <cr1901_modern> Will do tomorrow; I'm still reeling from pollen/can't think right now.

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

02:30 <bb-m-labs> build #858 of artiq-win64-test is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/858 blamelist: whitequark <whitequark@whitequark.org>

02:30 <bb-m-labs> build #2304 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2304 blamelist: whitequark <whitequark@whitequark.org>

02:50 <GitHub-m-labs> [artiq] whitequark pushed 5 new commits to master: https://github.com/m-labs/artiq/compare/4f29d9134fe1...a148729bf87b

02:50 <GitHub-m-labs> artiq/master 8a70c18 whitequark: firmware: add debug output to hmc542 driver.

02:50 <GitHub-m-labs> artiq/master 68ef09e whitequark: firmware: stop profiler before rebooting too.

02:50 <GitHub-m-labs> artiq/master 9dc7efe whitequark: compiler: transparently handle Windows newlines in RunTool.

02:58 <bb-m-labs> build #2305 of artiq is complete: Failure [failed lit_test] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2305 blamelist: whitequark <whitequark@whitequark.org>

03:00 <GitHub-m-labs> [artiq] whitequark pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/a148729bf87b...917a4185ebea

03:00 <GitHub-m-labs> artiq/master 917a418 whitequark: Unbreak 9dc7efef.

03:00 <GitHub-m-labs> artiq/master fd2b8d5 whitequark: firmware: raise hmc542 log level to INFO.

03:02 <GitHub-m-labs> [artiq] whitequark opened issue #994: Rename asyncserial https://github.com/m-labs/artiq/issues/994

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

03:48 <bb-m-labs> build #859 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/859

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

08:47 <GitHub-m-labs> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/c646409dbe5e8e5f995f309d01dcbcd4d00c524d

08:47 <GitHub-m-labs> artiq/master c646409 whitequark: firmware: fix order of bits clocked into hmc542....

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

09:36 <bb-m-labs> build #860 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/860

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