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
fengling has quit [Quit: WeeChat 1.0]
<GitHub153> [artiq] jordens pushed 3 new commits to master: http://git.io/haVC
<GitHub153> artiq/master fae7246 Robert Jordens: pdq2: merge from main pdq2 repo
<GitHub153> artiq/master 5ab3290 Robert Jordens: pdq2: add refactored client code
<GitHub153> artiq/master 222d0a9 Robert Jordens: pdq2_controller: add dump option
fengling has joined #m-labs
travis-ci has joined #m-labs
<travis-ci> m-labs/artiq#55 (master - 222d0a9 : Robert Jordens): The build was broken.
travis-ci has left #m-labs [#m-labs]
balrog has quit [Ping timeout: 264 seconds]
<GitHub27> [artiq] jordens pushed 1 new commit to master: http://git.io/haXE
<GitHub27> artiq/master 577754c Robert Jordens: pdq2: fix argparser
travis-ci has joined #m-labs
<travis-ci> m-labs/artiq#56 (master - 577754c : Robert Jordens): The build was fixed.
travis-ci has left #m-labs [#m-labs]
rofl__ has quit [Ping timeout: 265 seconds]
rofl__ has joined #m-labs
balrog has joined #m-labs
rofl__ is now known as sh4rm4
aeris_ has joined #m-labs
sh4rm4 has quit [Ping timeout: 265 seconds]
sh4rm4 has joined #m-labs
sb0 has quit [Read error: Connection reset by peer]
FabM has quit [Ping timeout: 246 seconds]
sb0 has joined #m-labs
FabM has joined #m-labs
sb0 has quit [Quit: Leaving]
aeris_ has quit [Ping timeout: 244 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 256 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 246 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 256 seconds]
<GitHub184> [misoc] enjoy-digital pushed 1 new commit to master: http://git.io/hwfv
<GitHub184> misoc/master 9107710 Florent Kermarrec: litexxx cores: use default baudrate of 115200 for all tests
FabM has quit [Quit: ChatZilla 0.9.91.1 [Firefox 36.0.1/20150305021524]]
aeris_ has joined #m-labs
<GitHub29> [artiq] sbourdeauducq pushed 1 new commit to master: http://git.io/hwQb
<GitHub29> artiq/master 200e20f Sebastien Bourdeauducq: worker: close devices immediately after run and before analyze
aeris_ has quit [Ping timeout: 256 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 245 seconds]
aeris_ has joined #m-labs
aeris_ has quit [Ping timeout: 246 seconds]
aeris_ has joined #m-labs
fengling has quit [Quit: WeeChat 1.0]
mog has left #m-labs ["Leaving"]
mog has joined #m-labs
_florent_ has joined #m-labs
_florent_ has quit [Quit: Leaving]
aeris has quit [Quit: en a pas]
SturmFlut has joined #m-labs
SturmFlut has quit [Read error: Connection reset by peer]
aeris has joined #m-labs
aeris has quit [Quit: en a pas]
aeris has joined #m-labs
aeris has quit [Client Quit]
aeris has joined #m-labs
aeris has quit [Client Quit]
aeris has joined #m-labs
aeris has quit [Client Quit]
aeris has joined #m-labs
_florent_ has joined #m-labs
<_florent_> stb0: (if you read the logs) I've created an instrumented SoC with litescope to try to debug kc705 runtime
kyak has quit [Ping timeout: 264 seconds]
<_florent_> I can trigger litescope when runtime start running (or during runtime execution since I'm write the software write to a specific register to trigger analyzer)
<_florent_> I'm can observe all the signals we want
<_florent_> I'm going to investigate on that tomorrow, but if you have some ideas on interesting signals to visualize, please share :)
_florent_ has quit [Quit: Leaving]
kyak has joined #m-labs
kyak has joined #m-labs
<ysionneau> whitequark: I heard you're joining us (M-Labs) to work on ARTIQ? :)
<whitequark> yea
<whitequark> already did, in fact
<ysionneau> yes that's what sb0 told me (we had lunch today)
<ysionneau> welcome ! :)
kyak has quit []
sb0 has joined #m-labs
kyak has joined #m-labs
<rjo> whitequark: welcome!
<rjo> _florent_: are you using ethernet or the uart for piping the litescope data?
_florent_ has joined #m-labs
<_florent_> rjo: in this case it uses UART since runtime is loaded with netboot
<_florent_> sb0: do you remember what toolchain you used last time you tested runtime sucessfully on kc705, ISE or Vivado?
<rjo> _florent_: ah. so your liteeth stack is single-master? either used/claimed by litescope or byt the bios/runtime?
<_florent_> yes (at least for now :)
<rjo> _florent_: ack.
_florent_ has quit [Quit: Leaving]