00:00 <rjo> bb-m-labs: force build --props=package=artiq-board,artiq_target=kasli,artiq_variant=suservo artiq-board

00:00 <bb-m-labs> The build has been queued, I'll give a shout when it starts

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

00:28 <bb-m-labs> build forced [ETA 41m17s]

00:28 <bb-m-labs> I'll give a shout when the build finishes

00:57 <bb-m-labs> build #1492 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1492

01:16 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #996: What do you mean by no longer working? https://github.com/m-labs/artiq/issues/996#issuecomment-387254265

01:21 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #996: I just tested the RTM hardware and it works fine. Are you using the wrong USB port? You need ``ftdi_location 3:10`` at the moment. https://github.com/m-labs/artiq/issues/996#issuecomment-387254977

03:00 <GitHub62> [smoltcp] dlrobertson closed issue #3: IPv6 https://github.com/m-labs/smoltcp/issues/3

03:00 <GitHub118> [smoltcp] dlrobertson commented on issue #3: Basic on-link IPv6 support is added in #196. Any subsequent bugs or feature requrests for IPv6 should be filed as separate issues. https://github.com/m-labs/smoltcp/issues/3#issuecomment-387269546

03:18 <GitHub146> [smoltcp] pothos closed issue #199: Stalled TCP connection because window update is not announced after reading https://github.com/m-labs/smoltcp/issues/199

03:55 <GitHub-m-labs> [artiq] enjoy-digital commented on issue #996: OK then i'll retry on Wednesday, i was using 3:10, it was working correctly but then stopped.... https://github.com/m-labs/artiq/issues/996#issuecomment-387276820

06:32 <GitHub-m-labs> [artiq] sbourdeauducq commented on issue #996: What was the error? https://github.com/m-labs/artiq/issues/996#issuecomment-387299150

09:23 <marmelada> hey, do you know if liteeth has linux driver and what is its state?

12:09 <GitHub-m-labs> [artiq] sbourdeauducq closed issue #996: serwb breaks when AMC bitstream is built with SAWG https://github.com/m-labs/artiq/issues/996

12:11 <sb0> marmelada, afaik there isn't. are you trying to run linux on misoc?

12:12 <marmelada> not me, but I'm trying to convince company I work in to use liteeth instead of temac

12:14 <marmelada> they have misoc up and running and liteeth works for them, but they may also want to have liteeth + microblaze (or just run linux on zynq)

12:31 <GitHub189> [smoltcp] dlrobertson opened issue #202: socket: accepts function does not need the entire IpRepr https://github.com/m-labs/smoltcp/issues/202

12:45 <GitHub28> [smoltcp] dlrobertson opened pull request #203: cargo: autodiscover should be off for examples (master...explicit-example) https://github.com/m-labs/smoltcp/pull/203

12:46 <hartytp> marmelada: one thing I'd really like to see is proper fuzzing of liteeth

12:47 <hartytp> it seems pretty good, but I'd be more confident using it if it were better tested (like smoltcp)

12:48 <hartytp> marmelada: do you have any info on how testing on booster is going?

12:48 <hartytp> we really need it asap

12:49 <hartytp> do you know if Greg/Maciej/Tomek were able to reproduce the issues I've seen?

12:49 <hartytp> (could you give a nudge to make sure that's all happening?)

12:49 <hartytp> thanks!

13:11 <marmelada> hartytp: Maciej is testing it right now

13:12 <sb0> marmelada, great!

13:18 <marmelada> is serwb still failing on latest artiq or is something wrong with my board?

15:18 <GitHub132> [smoltcp] whitequark commented on issue #202: Is this a problem? We already have the `IpRepr`. https://github.com/m-labs/smoltcp/issues/202#issuecomment-387439119

15:24 <GitHub41> [smoltcp] whitequark pushed 1 new commit to master: https://github.com/m-labs/smoltcp/commit/4397004267507fa18a91e86de3a6d7de40c638e5

15:24 <GitHub41> smoltcp/master 4397004 Dan Robertson: cargo: autodiscover should be off for examples...

15:24 <GitHub9> [smoltcp] whitequark closed pull request #203: cargo: autodiscover should be off for examples (master...explicit-example) https://github.com/m-labs/smoltcp/pull/203

15:26 <rjo> marmelada: #996 ?

15:26 <GitHub118> [smoltcp] dlrobertson commented on issue #202: It isn't really a problem. I was primarily thinking of this as unused information. In particular I was thinking about the case where the packet is something like IPv6 > Hop-by-Hop > UDP. In this case the UDP socket `accepts` function will accept the `IpRepr` with a `next_header` value of Hop-by-Hop, but obviously `repr` would be a `UdpRepr`. https://github.com/m-lab

15:37 <travis-ci> m-labs/smoltcp#900 (master - 4397004 : Dan Robertson): The build passed.

15:37 <travis-ci> Change view : https://github.com/m-labs/smoltcp/compare/880fb73d544f...439700426750

15:37 <travis-ci> Build details : https://travis-ci.org/m-labs/smoltcp/builds/376415951

16:03 <GitHub126> [smoltcp] whitequark commented on issue #202: Yeah, that check is already done in EthernetInterface, so I didn't add it to `accepts` as redundant. We may add it for completeness, although it feels a bit pointless. https://github.com/m-labs/smoltcp/issues/202#issuecomment-387454196

17:10 <sb0> marmelada, shouldn't fail. what error are you getting?

18:32 <marmelada> sb0: initialisation failed

18:32 <marmelada> I'll post more details tommorow

18:33 <marmelada> right now I'm pulling my hair out bc of kasli

18:33 <marmelada> on my modified suservo artiq is in rolling reboot state, it reboots after "si5324 is locked" info

18:34 <marmelada> (and si5324 led is lit)

18:34 <marmelada> curiously on opticlock it does not happen

18:34 <marmelada> and on opticlock software and my suservo gateware it does not happen either