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
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has quit [Client Quit]
stekern has quit [Ping timeout: 264 seconds]
stekern has joined #m-labs
<_florent_>
sb0: that could be worth giving a try to the full design with serwb on your boards, but i think there is still something i need to figure out
<cr1901_modern>
I wonder how true this is, having not actually really used the GUI
mumptai has joined #m-labs
<GitHub110>
[smoltcp] dlrobertson commented on pull request #78 2cfa089: Might be more readable to just write this out https://git.io/vFrGK
<GitHub188>
[smoltcp] dlrobertson commented on pull request #78 2cfa089: This IP is used multiple times. Might be worthwhile to make this a variable that is used. https://git.io/vFrG6
<GitHub196>
[smoltcp] batonius opened pull request #79: Make socket errors in `socket_egress` non-critical. (master...ignored_arps) https://git.io/vFrcm
<GitHub196>
[smoltcp] batonius commented on issue #79: False alarm, the issue is with ICMP sockets not setting `device_result` in `socket_egress`, `Error::Unaddressable` in `device_result` is already being ignored. Will add the fix to #78. https://git.io/vFrBW
<GitHub159>
[smoltcp] batonius closed pull request #79: Make socket errors in `socket_egress` non-critical. (master...ignored_arps) https://git.io/vFrcm
<GitHub118>
[smoltcp] batonius commented on issue #78: **Problem 2**: ICMP sockets don't update `device_result` in `socket_egress`, so their `Error::Unaddressable` isn't ignored, resulting in early returns from `socket_egress` and `poll`, preventing the second from processing ARP responses, which results in ARP flood until the socket is open.... https://git.io/vFrRe
<GitHub61>
[smoltcp] batonius commented on issue #78: **Problem 2**: ICMP sockets don't update `device_result` in `socket_egress`, so their `Error::Unaddressable` isn't ignored, resulting in early returns from `socket_egress` and `poll`, preventing the second from processing ARP responses, which results in ARP flood while the socket is open.... https://git.io/vFrRe
<GitHub38>
[smoltcp] batonius commented on issue #78: @whitequark By the way, why do we break from the loop in `socket_egress` on `Error::Unaddressable`? There could be other sockets left with endpoints resolved, and by breaking here we prevent them from sending packets until all the sockets before them have their destinations resolved. https://git.io/vFrRo