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
sb0 has quit [Quit: Leaving]
kuldeep has quit [Ping timeout: 272 seconds]
kuldeep has joined #m-labs
ohama has quit [Ping timeout: 248 seconds]
ohama has joined #m-labs
kuldeep has quit [Read error: Connection reset by peer]
kuldeep has joined #m-labs
kuldeep has quit [Ping timeout: 255 seconds]
kuldeep has joined #m-labs
sandeepkr has joined #m-labs
kuldeep has quit [Read error: Connection reset by peer]
sandeepkr has quit [Ping timeout: 255 seconds]
sandeepkr has joined #m-labs
kuldeep has joined #m-labs
sandeepkr has quit [Remote host closed the connection]
sandeepkr has joined #m-labs
kuldeep_ has joined #m-labs
kuldeep has quit [Read error: Connection reset by peer]
sandeepkr_ has joined #m-labs
kuldeep_ has quit [Read error: Connection reset by peer]
sandeepkr has quit [Ping timeout: 272 seconds]
Gurty has quit [Ping timeout: 240 seconds]
sb0 has joined #m-labs
Gurty has joined #m-labs
<sb0> whitequark, any update on smoltcp integration?
Gurty has quit [Ping timeout: 240 seconds]
sandeepkr_ has quit [Read error: Connection reset by peer]
sandeepkr_ has joined #m-labs
<GitHub154> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/vMCq1
<GitHub154> artiq/master 780d6d1 Sebastien Bourdeauducq: worker: fix handling of archive parameter during dataset get in examine
Gurty has joined #m-labs
Gurty has joined #m-labs
Gurty has quit [Changing host]
<GitHub164> [artiq] sbourdeauducq opened issue #652: Python 3.6 support https://git.io/vMCqj
Zou has joined #m-labs
Gurty has quit [Ping timeout: 240 seconds]
stekern has quit [Ping timeout: 246 seconds]
stekern has joined #m-labs
<bb-m-labs_> build #305 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/305
rohitksingh has joined #m-labs
<bb-m-labs_> build #1205 of artiq is complete: Failure [failed python_unittest_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1205 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<sb0> whitequark, can a syscall return an integer tuple?
<whitequark> sb0: smoltcp: I'll finish rust-managed soon (an extension of smoltcp::Managed), which is necesssary to put an EthernetInterface into a Scheduler nicely
<whitequark> sb0: syscall: yes, but you have to make it a #[repr(C)] struct on the Rust side
<whitequark> Rust will actively reorder fields in non-#[repr(C)] structs to eliminate padding
<sb0> ok, great!
rohitksingh has quit [Quit: Leaving.]
folkert has joined #m-labs
<travis-ci> [rust-managed] whitequark pushed 1 new commit to master: https://github.com/m-labs/rust-managed/commit/73ccc3f36e1df7175ae5e6a6dca427f0160ff37e
<travis-ci> rust-managed/master 73ccc3f whitequark: Implement.
<travis-ci> m-labs/rust-managed#1 (master - 73ccc3f : whitequark): The build failed.
<travis-ci> [rust-managed] whitequark pushed 1 new commit to master: https://github.com/m-labs/rust-managed/commit/0e6c5697d091a15388ad0c36779ab420fc06c06d
<travis-ci> rust-managed/master 0e6c569 whitequark: Fix build with use_alloc+use_std.
<travis-ci> m-labs/rust-managed#2 (master - 0e6c569 : whitequark): The build is still failing.
<travis-ci> [rust-managed] whitequark force-pushed master from 0e6c569 to b7f9d51: https://github.com/m-labs/rust-managed/commits/master
<travis-ci> rust-managed/master b7f9d51 whitequark: Fix build with use_alloc+use_std.
<travis-ci> m-labs/rust-managed#3 (master - b7f9d51 : whitequark): The build was fixed.
<travis-ci> [rust-managed] whitequark tagged v0.1.0 at master: https://github.com/m-labs/rust-managed/commits/v0.1.0
<travis-ci> [rust-managed] whitequark pushed 1 new commit to master: https://github.com/m-labs/rust-managed/commit/bf1c603683bef5ec311712a8aeeb29103704154c
<travis-ci> rust-managed/master bf1c603 whitequark: README: fix doc link.
<travis-ci> m-labs/rust-managed#4 (v0.1.0 - b7f9d51 : whitequark): The build passed.
<travis-ci> m-labs/rust-managed#5 (master - bf1c603 : whitequark): The build passed.
<travis-ci> [rust-managed] whitequark pushed 1 new commit to master: https://github.com/m-labs/rust-managed/commit/354761862cfd6b61288cac24eb805275a986d9a7
<travis-ci> rust-managed/master 3547618 whitequark: Fix some documentation issues.
<travis-ci> [rust-managed] whitequark pushed 1 new commit to master: https://github.com/m-labs/rust-managed/commit/a96bf93b41e7749c895736f20a8ad3a8238251c4
<travis-ci> rust-managed/master a96bf93 whitequark: Bump version.
<travis-ci> m-labs/rust-managed#6 (master - 3547618 : whitequark): The build passed.
<travis-ci> m-labs/rust-managed#7 (master - a96bf93 : whitequark): The build passed.
<travis-ci> m-labs/rust-managed#8 (v0.1.1 - a96bf93 : whitequark): The build passed.
<GitHub194> [artiq] sbourdeauducq commented on issue #652: There are however problems with migen, and conda will need some attention (recompiling packages, switching qt to the anaconda package). https://git.io/vMCCr
<sb0> how can I use the ksupport recv! macro in other files inside ksupport? there is nowhere to put #[macro_use] ...
<sb0> ah, I have to put "mod rtio" (or whatever the other file is) *after* the macro definiton...
<sb0> and that's all
<whitequark> yep
sb0 has quit [Quit: Leaving]
sandeepkr_ has quit [Remote host closed the connection]
sandeepkr_ has joined #m-labs
sandeepkr_ has quit [Max SendQ exceeded]
sb0 has joined #m-labs
hozer has joined #m-labs
hozer has quit [Quit: Leaving.]
hozer has joined #m-labs
sb0 has quit [Quit: Leaving]