sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
reportingsjr has joined #m-labs
<GitHub100> [artiq] sbourdeauducq commented on issue #685: Theoretically, jumbo frames are easy, and would boil down to changing a few numbers in the MAC followed by the usual yak shaving.... https://github.com/m-labs/artiq/issues/685#issuecomment-301217291
<GitHub109> [artiq] whitequark commented on issue #685: @sbourdeauducq This is just a wish, or maybe even a premature optimization. It should not be necessary to get lwip-like speeds. https://github.com/m-labs/artiq/issues/685#issuecomment-301218830
hedgeberg has quit [Quit: t(;-;t)]
hedgeberg has joined #m-labs
_whitelogger has joined #m-labs
cyrozap has quit [Quit: Client quit]
cyrozap has joined #m-labs
<GitHub193> [ionpak] sbourdeauducq pushed 4 new commits to master: https://github.com/m-labs/ionpak/compare/ad447cd5f9e9...246839f15399
<GitHub193> ionpak/master dc4534e Sebastien Bourdeauducq: average more IC samples
<GitHub193> ionpak/master ba1482d Sebastien Bourdeauducq: adjust anode PID coefficients
<GitHub193> ionpak/master 9803388 Sebastien Bourdeauducq: update errata
sb0 has quit [Quit: Leaving]
_whitelogger has joined #m-labs
hedgeberg has quit [Ping timeout: 255 seconds]
hedgeberg has joined #m-labs
<whitequark> sb0: are you doing averaging manually now?
sb0 has joined #m-labs
<sb0> whitequark, combining both. the manual averaging is mostly to filter out the spikes caused by the insufficient pwm resolution
<whitequark> ah ok
<whitequark> should I fix that now that I have the new board?
<whitequark> with the LA it should be quick
<sb0> yeah, that would help
<whitequark> okay
<whitequark> I think I'll just connect hte clock output to LA, it doesn't even have to have the shared ground at that frequency
<whitequark> hopefully that will not kill it...
<sb0> another major bug right now is the ADC stops sampling after a couple dozen seconds
sb0 has quit [Quit: Leaving]
<whitequark> yes, I've told you already why that happens
mumptai has joined #m-labs
sb0 has joined #m-labs
<GitHub141> [artiq] cjbe opened pull request #734: firmware: fix revision of compiler_builtins for satman (master...satman_compiler_builtins_rev) https://github.com/m-labs/artiq/pull/734
<GitHub139> [artiq] whitequark commented on issue #734: Why is this necessary exactly? https://github.com/m-labs/artiq/pull/734#issuecomment-301263762
<GitHub78> [artiq] cjbe commented on issue #734: Satman does not compile using the master branch of compiler_builtins. This pins it back to a working version -the same fix was applied to runtime in 52a046d https://github.com/m-labs/artiq/pull/734#issuecomment-301266031
cjbe has joined #m-labs
<GitHub191> [artiq] whitequark closed pull request #734: firmware: fix revision of compiler_builtins for satman (master...satman_compiler_builtins_rev) https://github.com/m-labs/artiq/pull/734
<GitHub154> [artiq] whitequark pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/170d2886fd1c...edef51c6b610
<GitHub154> artiq/master edef51c whitequark: Merge pull request #734 from cjbe/satman_compiler_builtins_rev...
<GitHub154> artiq/master 0b6fb95 Chris Ballance: firmware: fix revision of compiler_builtins for satman
<bb-m-labs> build #557 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/557
<bb-m-labs> build #474 of artiq-win64-test is complete: Warnings [warnings python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/474 blamelist: whitequark <whitequark@whitequark.org>, Chris Ballance <chris.ballance@physics.ox.ac.uk>
<bb-m-labs> build #1497 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1497
_whitelogger has joined #m-labs