<GitHub46>
[artiq] sbourdeauducq commented on issue #908: It's not just a change in the timing, it seems that jitter also increases significantly. Noise/jitter issues (on-chip or on-board), e.g. crosstalk, MMCM failure. https://github.com/m-labs/artiq/issues/908#issuecomment-368181491
attie has quit [Ping timeout: 248 seconds]
attie has joined #m-labs
<GitHub88>
[artiq] jonaskeller commented on issue #902: So far, it's looking good. I left it idle for 6h and didn't see it crash, then set `net_trace` to 1 and left an experiment running in a loop to stress the core device. It's been running in that mode for over 2h now, which is a lot considering that I never saw it survive for more than a minute before. I'll leave it running over the weekend and let you know Monday how it went
attie has quit [Remote host closed the connection]
<bb-m-labs>
The build has been queued, I'll give a shout when it starts
attie has quit [Ping timeout: 260 seconds]
attie has joined #m-labs
<GitHub56>
[artiq] sbourdeauducq commented on issue #932: @jordens can you delete (or move to the dev channel) the buggy openocd versions? If course they are the ones that get installed as per Murphy's law... https://github.com/m-labs/artiq/issues/932#issuecomment-368213549
<GitHub167>
[artiq] jordens commented on issue #932: @sbourdeauducq It's not buggy openocd versions but incompatibility between the proxy bitstream shipped in the old board packages and the new openocd versions. Moving openocd won't help.... https://github.com/m-labs/artiq/issues/932#issuecomment-368217430
attie has quit [Remote host closed the connection]
attie has quit [Remote host closed the connection]
attie has joined #m-labs
<GitHub156>
[smoltcp] whitequark commented on issue #166: I'm not happy about this. You're making smoltcp perform significantly worse for the use case it is primarily intended for, which is small embedded devices. I don't think this is acceptable. https://github.com/m-labs/smoltcp/issues/166#issuecomment-368231079
attie has quit [Ping timeout: 240 seconds]
attie has joined #m-labs
<GitHub52>
[smoltcp] batonius commented on issue #166: Then I'll try to rethink the design to keep it this way, maybe along the lines of the old `Device` trait, with handler types owning packet buffers and returning them in destructors. The counterexample of loopback based on `RingBuffer` would still be impossible tho. https://github.com/m-labs/smoltcp/issues/166#issuecomment-368241377
<GitHub175>
[smoltcp] batonius commented on issue #170: I've tried to do that in #19, and even had a working prototype, but eventually lost interest, the `SocketRef` type we have is a remnant of that attempt. https://github.com/m-labs/smoltcp/issues/170#issuecomment-368245570