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
bentley` has joined #m-labs
kuldeep has quit [Remote host closed the connection]
kuldeep has joined #m-labs
_whitelogger has joined #m-labs
<GitHub28> [smoltcp] whitequark pushed 4 new commits to master: https://git.io/vMkEN
<GitHub28> smoltcp/master 40be830 whitequark: Implement the TCP CLOSING state.
<GitHub28> smoltcp/master a475925 whitequark: Implement the TCP FIN-WAIT-2 state.
<GitHub28> smoltcp/master a058996 whitequark: Implement the TCP FIN-WAIT-1 state.
<travis-ci> m-labs/smoltcp#5 (master - 553d640 : whitequark): The build passed.
balrog has quit [Ping timeout: 245 seconds]
balrog has joined #m-labs
fengling has quit [Ping timeout: 268 seconds]
bentley` has quit [Ping timeout: 256 seconds]
sb0 has joined #m-labs
_whitelogger has joined #m-labs
attie_ has joined #m-labs
fengling has joined #m-labs
attie has quit [*.net *.split]
sb0 has quit [Quit: Leaving]
<whitequark> sb0: so, um, it looks like I wrote a TCP/IP stack?
<whitequark> it passes all of the testing I subjected it to so far.
<whitequark> I am starting to integrate it right about now, then
<whitequark> ah wait, no, timeouts are still stubbed out, let me fix that first.
fengling has quit [Ping timeout: 268 seconds]
<GitHub130> [artiq] whitequark pushed 2 new commits to master: https://git.io/vMkxL
<GitHub130> artiq/master 010ce01 whitequark: firmware: remove spurious build-dependency on winapi.
<GitHub130> artiq/master aed9129 whitequark: firmware: remove cargo profiles....
fengling has joined #m-labs
mumptai has joined #m-labs
fengling has quit [Ping timeout: 268 seconds]
<bb-m-labs> build #286 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/286
fengling has joined #m-labs
<bb-m-labs> build #1185 of artiq is complete: Failure [failed python_unittest_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1185 blamelist: whitequark <whitequark@whitequark.org>
sb0 has joined #m-labs
<cr1901_modern> https://streaming.media.ccc.de/33c3/hall1 mithro's giving his talk now
<sb0> _florent_, brute-forcing attribute gets in jesd common.py and ignoring exceptions is not acceptable, you should probably have merged JESD204BTransportSettings and JESD204BPhysicalSettings in the first place.
<sb0> I'm talking about the code in get_configuration_data "for settings in [self.phy, self.transport], try... except: pass"
<sb0> this adds unnecessary complexity, and causes obscure bugs with values silently not set
<_florent_> sb0: ok to simplify that if you think that's useful
kuldeep has quit [Remote host closed the connection]
kuldeep has joined #m-labs
<_florent_> sb0: but jesd204b has lots or parameters and it's probably easier to split this settings to understand the code
<sb0> what is the difference between a "physical" and a "transport" setting?
<sb0> even if this difference is justified, attempting to get a parameter by name from the first structure that will provide it and ignoring errors is a recipe for bugs
<sb0> (such as those I am having right now, touching this code)
sb0 has quit [Quit: Leaving]
sandeepkr has joined #m-labs
sandeepkr has quit [Remote host closed the connection]
sandeepkr has joined #m-labs
acathla has quit [Quit: Coyote finally caught me]
acathla has joined #m-labs
Gurty has quit [Ping timeout: 256 seconds]
Gurty has joined #m-labs