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
<GitHub107> [smoltcp] dlrobertson opened issue #137: poll_at returns the time left to call poll instead of the timestamp at which to call poll https://github.com/m-labs/smoltcp/issues/137
<GitHub163> [smoltcp] whitequark commented on issue #137: It's not obviously a duration. It means "as early as possible", and is used in situations where the current timestamp is inaccessible. https://github.com/m-labs/smoltcp/issues/137#issuecomment-361778704
<GitHub72> [smoltcp] hjr3 commented on issue #103: @dlrobertson I have not been able to catch you on #m-labs irc and I just requested access to redox chat. I have started working on the `Hop-by-Hop Options Header` implementation at https://tools.ietf.org/html/rfc8200#section-4.3. https://github.com/m-labs/smoltcp/issues/103#issuecomment-361798824
<GitHub132> [artiq] sbourdeauducq commented on issue #913: Any difference in openocd versions? https://github.com/m-labs/artiq/issues/913#issuecomment-361805915
whitequark has quit [Ping timeout: 255 seconds]
whitequark has joined #m-labs
sb0 has quit [Quit: Leaving]
rohitksingh_work has joined #m-labs
<bb-m-labs> build #1178 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1178
<GitHub116> [artiq] jordens commented on issue #913: You need the last commit.... https://github.com/m-labs/artiq/issues/913#issuecomment-361819882
<GitHub168> [artiq] jordens commented on issue #913: You need the last commit.... https://github.com/m-labs/artiq/issues/913#issuecomment-361819882
kraza has joined #m-labs
<kraza> hello everyone
<kraza> Hey, is anyone online?
<kraza> hello
FabM has joined #m-labs
sb0 has joined #m-labs
<GitHub197> [sinara] marmeladapk pushed 1 new commit to master: https://git.io/vN7RJ
<GitHub197> sinara/master 848392b Paweł: Kasli v1.1rc3...
<GitHub136> [sinara] marmeladapk tagged Kasli/v1.1rc3 at 973d558: https://git.io/vN7Rq
<GitHub157> [smoltcp] batonius commented on issue #75: @phil-opp @whitequark What's the status of the PR? I could use a DHCP implementation :) https://github.com/m-labs/smoltcp/pull/75#issuecomment-361883113
<rjo> kraza: hello
<kraza> hello
<kraza> Hey, so I'd like to ask about the quadrupoles
<GitHub116> [smoltcp] phil-opp commented on issue #75: I'm happy to update and adjust this PR as soon as there's desire to merge it. In https://github.com/m-labs/smoltcp/issues/63#issuecomment-339422852 @whitequark said that he wants to do the next step himself, maybe he wants to wait until the other parts are ready?... https://github.com/m-labs/smoltcp/pull/75#issuecomment-361891262
<kraza> I found the github with driver plans
<sb0> _florent_, going to turn off the kasli for a while to put heatsinks on the fpgas
<sb0> hm
<sb0> they're not self-adhesive. it'll take a bit longer than expected
<sb0> done
<sb0> i'm using this kafuter k5202 thermally conductive glue, it's surprisingly strong and efficient
<sb0> kraza, go ahead and ask
<rjo> kraza: just ask.
<_florent_> sb0: are you at the lab? if so, can you connect the two kasli using the same sfp for both (0 or 2)?
<_florent_> sb0: this would allow me to test things with the same bistream on both
<sb0> _florent_, ok
<_florent_> sb0: thanks
<_florent_> sb0: i checked the si5324 output, it's fine (150MHz)
<sb0> _florent_, done. sfp0
<_florent_> sb0: tx_init and rx_init fsm also seem fine
<sb0> _florent_, and the qpll is locking?
<_florent_> sb0: yes
<sb0> doesn't it need a stable clock before it's taken out of reset anyway?
<sb0> I remember seeing something about this in the xilinx doc
<sb0> maybe the lock signal is high but the clock output is still garbage. that wouldn't surprise me for something related to xilinx transceivers ...
<_florent_> yes we should probably keep the gtp in reset until we have a clean clock
rohitksingh_work has quit [Read error: Connection reset by peer]
sb0 has quit [Quit: Leaving]
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<GitHub187> [smoltcp] phil-opp opened issue #138: UDP socket buffer wastes space https://github.com/m-labs/smoltcp/issues/138
<GitHub197> [smoltcp] whitequark commented on issue #138: Assuming you can do that without unsafe code, sure. https://github.com/m-labs/smoltcp/issues/138#issuecomment-361925161
<GitHub170> [smoltcp] whitequark commented on issue #75: @phil-opp Can you add tests for parsing/emission and documentation for methods?... https://github.com/m-labs/smoltcp/pull/75#issuecomment-361927439
<GitHub58> [smoltcp] phil-opp commented on issue #75: > Can you add tests for parsing/emission and documentation for methods?... https://github.com/m-labs/smoltcp/pull/75#issuecomment-361929304
<GitHub166> [smoltcp] dlrobertson commented on issue #137: Ah, that makes sense. I guess I was thinking that if that was the case the timestamp would be equal to the timestamp passed as an argument. Thanks for the clarification https://github.com/m-labs/smoltcp/issues/137#issuecomment-361934023
<GitHub137> [smoltcp] whitequark commented on issue #75: > What about the length checks (see #75 (comment))?... https://github.com/m-labs/smoltcp/pull/75#issuecomment-361936362
dlrobertson has joined #m-labs
sb0 has joined #m-labs
rohitksingh has joined #m-labs
<sb0> bb-m-labs: force build --props=package=artiq-kasli-opticlock artiq-board
<bb-m-labs> build forced [ETA 18m17s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1179 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1179
<rjo> whitequark: could you look at the lit failure in release-3?
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
<GitHub82> [artiq] dhslichter commented on issue #407: As a benchmark for comparison, @r-srinivas ran the test on our ARTIQ 2 setup which runs the magtrap experiment (Windows 7 with NIST AV), and we got 450-470 ms. Will run on the new ARTIQ 3 setup today and let you know how that looks. https://github.com/m-labs/artiq/issues/407#issuecomment-361971474
<GitHub105> [smoltcp] hjr3 opened pull request #139: Add IPv6 Extension Hop-by-Hop Options Header (master...ipv6-hop-by-hop) https://github.com/m-labs/smoltcp/pull/139
rohitksingh has quit [Quit: Leaving.]
rohitksingh-demo has joined #m-labs
rohitksingh-demo has quit [Quit: Leaving.]
rohitksingh-demo has joined #m-labs
<sb0> _florent_, since artix7 gtp init is so slow, have you looked at any transceivers init timers in drtio?
<sb0> _florent_, what does the received data look like? does it contain unaligned valid data, or garbage?
<GitHub0> [artiq] jonaskeller commented on issue #407: With 3.2 py_8+gitaa64b8ad (the most recent flashable gateware), it takes between 520ms and 570ms on our Windows system. https://github.com/m-labs/artiq/issues/407#issuecomment-361999279
rohitksingh-demo has quit [Read error: Connection reset by peer]
<GitHub70> [smoltcp] phil-opp opened pull request #140: Use separate metadata and payload buffers for UDP sockets (master...socket_buffer) https://github.com/m-labs/smoltcp/pull/140
<GitHub90> [smoltcp] whitequark commented on pull request #140 c6197e5: `debug_assert!` https://github.com/m-labs/smoltcp/pull/140#discussion_r165150834
<GitHub42> [smoltcp] whitequark commented on pull request #140 c6197e5: `debug_assert!` https://github.com/m-labs/smoltcp/pull/140#discussion_r165151540
<GitHub8> [smoltcp] whitequark commented on pull request #140 c6197e5: You should take this common logic and put it into `impl SocketBuffer`. https://github.com/m-labs/smoltcp/pull/140#discussion_r165151239
<GitHub71> [smoltcp] whitequark commented on pull request #140 c6197e5: This comment doesn't make sense.... https://github.com/m-labs/smoltcp/pull/140#discussion_r165153049
<GitHub22> [smoltcp] whitequark commented on pull request #140 c6197e5: I would prefer explicit initialization in *examples*, to make it clear what is being constructed. https://github.com/m-labs/smoltcp/pull/140#discussion_r165149622
<GitHub194> [smoltcp] whitequark commented on pull request #140 c6197e5: This has to have two lifetimes. If you think it can be one, try to construct multiple socket buffers without using `Vec`. https://github.com/m-labs/smoltcp/pull/140#discussion_r165149947
<GitHub136> [smoltcp] whitequark commented on pull request #140 c6197e5: Same as above. https://github.com/m-labs/smoltcp/pull/140#discussion_r165151031
<GitHub133> [smoltcp] whitequark commented on pull request #140 c6197e5: `debug_assert!` https://github.com/m-labs/smoltcp/pull/140#discussion_r165150801
<GitHub117> [smoltcp] whitequark commented on pull request #140 c6197e5: It is not necessary to return `Error::Truncated` from this function anymore since there are no separate packet buffers. https://github.com/m-labs/smoltcp/pull/140#discussion_r165150390
<GitHub81> [artiq] jbqubit commented on issue #898: > You linked to line 300 specifically. https://github.com/m-labs/artiq/issues/898#issuecomment-362036241
<GitHub15> [artiq] jbqubit commented on issue #898: > You linked to line 300 specifically.... https://github.com/m-labs/artiq/issues/898#issuecomment-362036241
<GitHub135> [artiq] jbqubit commented on issue #898: > You linked to line 300 specifically.... https://github.com/m-labs/artiq/issues/898#issuecomment-362036241
mumptai has joined #m-labs
<GitHub133> [artiq] whitequark commented on issue #898: Yes, I already said that I did and it works... https://github.com/m-labs/artiq/issues/898#issuecomment-362043484
<GitHub185> [smoltcp] LuoZijun commented on issue #136: @whitequark ... https://github.com/m-labs/smoltcp/pull/136#issuecomment-362053895
<GitHub155> [smoltcp] LuoZijun commented on issue #82: @liranringel ... https://github.com/m-labs/smoltcp/issues/82#issuecomment-362057613
<GitHub43> [smoltcp] LuoZijun commented on pull request #136 78c7fb7: i'm not sure this, when we create one `tun` interface with `IFF_NO_PI` flag on linux. https://github.com/m-labs/smoltcp/pull/136#discussion_r165176170
<GitHub129> [smoltcp] LuoZijun commented on pull request #136 78c7fb7: BPF Reader problem.... https://github.com/m-labs/smoltcp/pull/136#discussion_r165176436
<GitHub128> [smoltcp] whitequark commented on pull request #136 0a2e785: Please do not do this. Instead, add the `phy-tap_interface` feature as a dependency in `Cargo.toml`. https://github.com/m-labs/smoltcp/pull/136#discussion_r165183106
<GitHub18> [smoltcp] whitequark commented on pull request #136 0a2e785: Please do not just move things around. https://github.com/m-labs/smoltcp/pull/136#discussion_r165183525
<GitHub156> [smoltcp] whitequark commented on issue #136: This PR is very complicated and nearly impossible to review. How about splitting it into multiple parts? https://github.com/m-labs/smoltcp/pull/136#issuecomment-362068416
dlrobertson has quit [Ping timeout: 265 seconds]
<GitHub125> [smoltcp] LuoZijun commented on issue #136: @whitequark ... https://github.com/m-labs/smoltcp/pull/136#issuecomment-362075918
mumptai has quit [Quit: Verlassend]
stekern has quit [Ping timeout: 240 seconds]
stekern has joined #m-labs
<GitHub136> [artiq] jbqubit opened issue #914: misoc asyncserial https://github.com/m-labs/artiq/issues/914
<GitHub99> [artiq] jbqubit commented on issue #911: I did the following again this afternoon. Same error.... https://github.com/m-labs/artiq/issues/911#issuecomment-362110706