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
<GitHub162> [smoltcp] whitequark commented on issue #54: @little-dude OK, looking closer at [gopacket/layers] I now see what you mean. It is indeed massive.... https://git.io/vFee9
<GitHub147> [smoltcp] whitequark commented on issue #54: @little-dude OK, looking closer at [gopacket/layers] I now see what you mean. It is indeed massive.... https://git.io/vFee9
<GitHub74> [smoltcp] whitequark commented on issue #52: #51 also needs a ManagedMap. https://git.io/vFevG
<GitHub46> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vFevQ
<GitHub46> smoltcp/master 2602a15 whitequark: Fix a naming mishap. NFCI.
<GitHub113> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vFefe
<GitHub113> smoltcp/master 7e4971d whitequark: Rename Cargo features: socket-* → proto-*.
<travis-ci> m-labs/smoltcp#337 (master - 2602a15 : whitequark): The build passed.
<travis-ci> m-labs/smoltcp#338 (master - 7e4971d : whitequark): The build passed.
<GitHub116> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vFefx
<GitHub116> smoltcp/master 475486c whitequark: Update README.
<travis-ci> m-labs/smoltcp#339 (master - 475486c : whitequark): The build passed.
<GitHub139> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vFek0
<GitHub139> smoltcp/master 42e2c04 whitequark: Expose wrapping and unwrapping of SocketRefs.
<travis-ci> m-labs/smoltcp#340 (master - 42e2c04 : whitequark): The build passed.
<GitHub111> [smoltcp] dlrobertson commented on issue #3: I am definitely interested in working on this post #50 https://git.io/vFeIH
<GitHub184> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vFetY
<GitHub184> smoltcp/master f64a99a whitequark: Use a much more sensible method naming for SocketRef.
<GitHub93> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/cdba330845d8b51a6a55108f233a9208dec42391
<GitHub93> artiq/master cdba330 whitequark: Update smoltcp....
<GitHub122> [artiq] whitequark closed issue #840: Frequent malformed packet errors https://github.com/m-labs/artiq/issues/840
<GitHub49> [artiq] whitequark commented on issue #840: Core device now logs the complete packet under DEBUG log level, please open an issue per type of malformed packet you see (unless it is something benign). https://github.com/m-labs/artiq/issues/840#issuecomment-339195108
<GitHub193> [artiq] whitequark commented on issue #840: Maybe we should lower the log level for the malformed ingress packet to DEBUG. https://github.com/m-labs/artiq/issues/840#issuecomment-339195150
<GitHub7> [artiq] sbourdeauducq commented on commit cdba330: We don't use UDP anymore. https://github.com/m-labs/artiq/commit/cdba330845d8b51a6a55108f233a9208dec42391#commitcomment-25172820
<GitHub197> [artiq] whitequark commented on commit cdba330: Aren't there frequent discussions of using UDP for something? https://github.com/m-labs/artiq/commit/cdba330845d8b51a6a55108f233a9208dec42391#commitcomment-25172880
<GitHub14> [artiq] sbourdeauducq commented on commit cdba330: No. And I had actually told you not to spend time implementing anything UDP-related. https://github.com/m-labs/artiq/commit/cdba330845d8b51a6a55108f233a9208dec42391#commitcomment-25172890
<GitHub29> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/6bdeddd201008a8ee027834d03369909f25605f3
<GitHub29> artiq/master 6bdeddd whitequark: runtime: remove UDP-related code.
<GitHub173> [artiq] whitequark commented on commit cdba330: Sure, let me remove a whole 74 LOC... https://github.com/m-labs/artiq/commit/cdba330845d8b51a6a55108f233a9208dec42391#commitcomment-25172916
<GitHub199> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/89b7c9e09112bea921f76f8e9c028b63218e0862
<GitHub199> artiq/release-3 89b7c9e whitequark: Update smoltcp....
<bb-m-labs> build #853 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/853
<bb-m-labs> build #595 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/595
<bb-m-labs> build #1738 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1738
<whitequark> sb0: btw core device gained default route support as of today
<whitequark> so if it ever needs to establish outbound connections it can.
<whitequark> not sure why though
<sb0> the artiq core device won't, but ionpak might
<whitequark> ok
<whitequark> I have not expected so many people to become interested in smoltcp
<whitequark> that's some deluge of PRs in such a small time
<sb0> I guess there is all the iot hype + poor quality of other stacks ...
<whitequark> IGMP?
<whitequark> for IoT?
<whitequark> actually I'm not even sure what IGMP is useful for
<bb-m-labs> build #854 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/854
<bb-m-labs> build #596 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/596
<GitHub177> [smoltcp] pothos opened issue #62: TCP hangs when sending https://git.io/vFeY1
<bb-m-labs> build #1739 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1739
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 248 seconds]
rohitksingh has joined #m-labs
<GitHub42> [smoltcp] phil-opp commented on issue #57: > What's remaining here? I'd like to merge it ASAP.... https://git.io/vFeu6
<GitHub189> [smoltcp] phil-opp commented on issue #57: > What's remaining here? I'd like to merge it ASAP.... https://git.io/vFeu6
<GitHub148> [smoltcp] phil-opp commented on issue #57: Found the problem and was able to fix it :tada:!... https://git.io/vFe1a
<GitHub180> [smoltcp] batonius commented on issue #55: After trying to implement it for some time, I've decided against building **on top** of _smoltcp_ : coordinating several independent TCP/IP stacks under a single abstraction just doesn't feel right.... https://git.io/vFe5w
<GitHub185> [smoltcp] phil-opp commented on pull request #57 98a684f: I don't know of a better way. Direct access to `self.*` does not work, since the compiler then tries to borrow the complete `self` in the closure. https://git.io/vFedT
<GitHub90> [smoltcp] phil-opp commented on issue #57: I rebased the PR, renamed the generic parameters (`Rx`/`Tx` instead of `T` for `phy::{Rx, Tx}Token`), and updated the documentation. It compiles and all tests pass, so I think this is ready for merging/final review.... https://git.io/vFehT
<rjo> _florent_: ping re sayma.
<GitHub181> [smoltcp] phil-opp opened issue #63: DHCP support https://git.io/vFvm0
<GitHub59> [nu-servo] jordens pushed 3 new commits to master: https://github.com/m-labs/nu-servo/compare/8adb796519e9...fe4b60b9027f
<GitHub59> nu-servo/master a218be1 Robert Jordens: iir: doc
<GitHub59> nu-servo/master 46710c5 Robert Jordens: servo: fix adc cycle duration
<GitHub59> nu-servo/master fe4b60b Robert Jordens: servo_rtio: add RTIO interface for all of servo
<GitHub94> [smoltcp] whitequark commented on issue #63: > Is DHCP support planned?... https://git.io/vFv8m
<GitHub133> [sinara] gkasprow pushed 1 new commit to master: https://github.com/m-labs/sinara/commit/f2c83b29697ec44a3b97be62d8c359dcdbd4cefd
<GitHub133> sinara/master f2c83b2 Greg: added CPLD pinout
rohitksingh has quit [Quit: Leaving.]
<GitHub169> [migen] jordens pushed 1 new commit to master: https://git.io/vFvgv
<GitHub169> migen/master 9d72dad Robert Jordens: ise: support cpld workflow
<bb-m-labs> build #194 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/194
<rjo> bb-m-labs: force build --props=package=artiq-kc705-nist_clock artiq-board
<bb-m-labs> build forced [ETA 15m31s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #855 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/855
mumptai has joined #m-labs
<GitHub153> [smoltcp] whitequark commented on issue #63: OK here's the plan.... https://git.io/vFvKH
<GitHub69> [smoltcp] whitequark commented on issue #63: OK here's the plan.... https://git.io/vFvKH
<GitHub74> [artiq] sbourdeauducq pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/6bdeddd20100...e80a527f2eca
<GitHub74> artiq/master e80a527 Sebastien Bourdeauducq: dashboard: add DAC monitoring widgets
<GitHub74> artiq/master bb6e761 Sebastien Bourdeauducq: examples/device_db: update DAC entry for Zotino, add sections
<bb-m-labs> build #856 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/856
<bb-m-labs> build #597 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/597
<bb-m-labs> build #1740 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1740
<GitHub38> [smoltcp] whitequark commented on pull request #57 b8e109c: Shouldn't we also give `TxToken::consume` similar treatment, for the same reason? https://git.io/vFvN0
<GitHub84> [smoltcp] whitequark commented on pull request #57 b8e109c: This has only a single buffer so max_burst_size should be `Some(1)`, to cap the receive window. https://git.io/vFvNa
<GitHub0> [smoltcp] little-dude commented on issue #54: Thanks @whitequark.... https://git.io/vFvNr
<GitHub173> [smoltcp] little-dude closed issue #54: Would a dedicated crate for packet decoding make sense? https://git.io/vdoKK
<GitHub74> [smoltcp] whitequark commented on issue #54: I've considered building smoltcp on top of libpnet but I really dislike their heavy-handed type-based approach. As you can see smoltcp keeps things very simple. https://git.io/vFvAD
<GitHub35> [smoltcp] whitequark commented on pull request #57 b8e109c: Yeah, this seems sensible. https://git.io/vFvjG
<GitHub168> [smoltcp] whitequark commented on issue #55: I don't think this works. For example, an Ethernet port has an `EthernetInterface` on top of it, and a PPP link has a `PppInterface` on top of it.... https://git.io/vFfkV
<GitHub4> [smoltcp] whitequark commented on issue #55: I don't think this works. For example, an Ethernet port has an `EthernetInterface` on top of it, and a PPP link has a `PppInterface` on top of it. Now you can't make a socket that binds to either.... https://git.io/vFfkV
<whitequark> uhm
<whitequark> why do we run coveralls twice on every build
<whitequark> once on windows and once on linux
<whitequark> it flip-flops all the time
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
<GitHub40> [buildbot-config] whitequark pushed 1 new commit to master: https://git.io/vFfmk
<GitHub40> buildbot-config/master 1e9ebe0 whitequark: Aggregate coverage information by git revision.
bb-m-labs has joined #m-labs
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1741 forced
<bb-m-labs> I'll give a shout when the build finishes
<GitHub28> [smoltcp] dlrobertson commented on pull request #61 e1fa197: Kind of ugly, but inner type mutability differs without this https://git.io/vFfm2
<GitHub193> [smoltcp] dlrobertson commented on pull request #61 e1fa197: Added these so that `assert_eq!` would work https://git.io/vFfma
<GitHub153> [smoltcp] whitequark commented on pull request #61 e1fa197: That's a perfectly fine construct in smoltcp. https://git.io/vFfm6
<whitequark> wtf, why is there so much interest for smoltcp
<GitHub0> [smoltcp] whitequark commented on pull request #61 e1fa197: Same here. https://git.io/vFfOY
<GitHub150> [smoltcp] whitequark commented on pull request #61 e1fa197: You can box everything here and then you can just return EthernetInterface by value. https://git.io/vFfOq
<GitHub138> [smoltcp] whitequark commented on pull request #61 e1fa197: Same here. https://git.io/vFfOm
<cr1901_modern> I want to use it too, but it doesn't support my use case
<cr1901_modern> (well I can add the feature, but ENOTIME)
<whitequark> what's the use case, I wonder?
<bb-m-labs> build #857 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/857
AceChen has quit [Remote host closed the connection]
<bb-m-labs> build #598 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/598
<bb-m-labs> build #1741 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1741
Gurty has quit [Ping timeout: 255 seconds]
<GitHub50> [smoltcp] batonius commented on issue #55: > Ethernet port has an EthernetInterface on top of it, and a PPP link has a PppInterface on top of it. Now you can't make a socket that binds to either... https://git.io/vFfGc
Gurty has joined #m-labs
<GitHub159> [smoltcp] whitequark commented on issue #62: Oh yeah you hit a bug; retransmit timer gets reset by ACKs whereas it should not. https://git.io/vFfZr
<GitHub85> [smoltcp] whitequark commented on issue #55: > we can have IpInterface to hold Option<EthernetInterface>, Option<PppInterface>, Option<GreInterface>, etc., without using trait objects. Each of these interfaces would use a single Device encapsulating several physical links via iface_id.... https://git.io/vFfZA
<GitHub122> [smoltcp] whitequark commented on issue #62: Oh yeah you hit a bug; retransmit timer gets reset by ACKs whereas it should not.... https://git.io/vFfZr