sb0 changed the topic of #m-labs to: https://m-labs.hk :: Mattermost https://chat.m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
airwoodix94 has joined #m-labs
airwoodix9 has quit [Ping timeout: 240 seconds]
airwoodix94 is now known as airwoodix9
Stormwind_mobile has quit [Remote host closed the connection]
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
stroboko1p has quit [Ping timeout: 256 seconds]
strobokopp has joined #m-labs
balrog has quit [Quit: Bye]
balrog has joined #m-labs
zkms has quit [Quit: zkms]
zkms has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Ping timeout: 265 seconds]
Stormwind_mobile has joined #m-labs
<mtrbot-ml_> [mattermost] <sb10q> https://gitlab.com/edouardklein/falsisign
<mtrbot-ml_> [mattermost] <sb10q> @astro why add libdyld to the cargo workspace?
<mtrbot-ml_> [mattermost] <sb10q> @astro is there no timer available? it seems you are simply incrementing a fake millisecond counter in the Sockets::run get_time() callback
Dar1us has quit [Ping timeout: 252 seconds]
Dar1us has joined #m-labs
futarisIRCcloud has joined #m-labs
airwoodix96 has joined #m-labs
airwoodix9 has quit [Ping timeout: 264 seconds]
airwoodix96 is now known as airwoodix9
mauz555 has joined #m-labs
_whitelogger has joined #m-labs
mumptai has joined #m-labs
strobokopp has quit [Read error: Connection reset by peer]
strobokopp has joined #m-labs
Dar1us has quit [Quit: Bye]
Dar1us_ has joined #m-labs
Dar1us_ is now known as Dar1us
<Astro-_> from what I've read, all local crates belong into the caro workspace members. is that wrong?
<Astro-_> we have never implemented a timer. high priority?
mumptai has quit [Read error: Connection reset by peer]
mumptai has joined #m-labs
<mtrbot-ml_> [mattermost] <dpn> @sb10q: In case you aren't routinely checking it, could I gently ping you to have a quick look at https://github.com/m-labs/artiq-comtools/pulls?
Getorix_ has joined #m-labs
Getorix has quit [Ping timeout: 256 seconds]
ohsix_ has quit [Ping timeout: 256 seconds]
daniellimws has joined #m-labs
<daniellimws> Hi, I just found out about migen this week, and quite interested in what I can do with it. But I also see that there's nmigen. Should I still start with migen or straight away try out nmigen? What's the main difference?
<tpw_rules> as a prolific nmigen user, i would say nmigen ;) it's taken a lot of lessons from regular migen and improved on them
<daniellimws> tpw_rules: Is it because of the syntax?
<tpw_rules> honestly i never really wrote migen. but i've had to read some of it and nmigen seems nicer
<daniellimws> tpw_rules: Is there any guide for nmigen that you refer to? I can only find guides for migen
<tpw_rules> unfortunately not really. it's still in flux
<daniellimws> Ok, anyways it seems there's a good amount of examples. I'll refer to those.
<daniellimws> Awesome, thanks
<_whitenotifier-9> [smoltcp] whitequark commented on pull request #336: WIP: Separate IP parts from EthernetInterface. - https://git.io/JfL2E
ohsix has joined #m-labs
X-Scale` has joined #m-labs
X-Scale has quit [Ping timeout: 256 seconds]
X-Scale` is now known as X-Scale
mauz555 has quit [Ping timeout: 272 seconds]
mauz555 has joined #m-labs
mauz555 has quit [Ping timeout: 256 seconds]
mauz555 has joined #m-labs
strobokopp has left #m-labs [#m-labs]
mauz555 has quit [Read error: Connection reset by peer]
ohsix has quit [Ping timeout: 264 seconds]
balrog has quit [Quit: Bye]
balrog has joined #m-labs
ohsix has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Ping timeout: 256 seconds]
ohsix has quit [Ping timeout: 240 seconds]
ohsix has joined #m-labs
X-Scale` has joined #m-labs
X-Scale has quit [Ping timeout: 256 seconds]
X-Scale` is now known as X-Scale
mauz555 has joined #m-labs
mauz555 has quit [Ping timeout: 272 seconds]
mauz555 has joined #m-labs
<mtrbot-ml_> [mattermost] <astro> @sb10q timer implemented. check my artiq-zynq branch.