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
<matterbridge-ml> [mattermost] <sb10q> @jbqubit hi
forrestv has joined #m-labs
balrog has joined #m-labs
balrog has quit [Ping timeout: 246 seconds]
balrog has joined #m-labs
Gurty has quit [Ping timeout: 258 seconds]
<cr1901_modern> sb10q: Is the IRC room being "deprecated"?
<futarisIRCcloud> Where are people moving to?
<cr1901_modern> futarisIRCcloud: Idk if people are moving
<cr1901_modern> I just noticed a mattermost bridge appeared today
<cr1901_modern> and sb0 left the room
<matterbridge-ml> [mattermost] <sb10q> it's not deprecated, I'm just adding options
<cr1901_modern> well at least it isn't slack (tm).
<matterbridge-ml> [mattermost] <sb10q> haha no
<matterbridge-ml> [mattermost] <sb10q> slack is bloated and proprietary
<cr1901_modern> and also likes to save itself to swap. Frequently.
Gurty has joined #m-labs
Gurty has quit [Changing host]
Gurty has joined #m-labs
<cr1901_modern> sb10q: Will you be back on IRC at all? How do I privmsg you if necessary (yes I can join the webclient if necessary)
<matterbridge-ml> [mattermost] <sb10q> yeah sure
<cr1901_modern> okay good, makes things easier for me
<cr1901_modern> See I'm not a luddite wrt chat protocols
<cr1901_modern> my issue is that multiple clients _destroys_ my bandwidth, so I have to pick and choose which ones I use
<cr1901_modern> and ultimately, IRC _still_ is the most important protocol for me to talk to ppl
* cr1901_modern looks for a mattermost pidgin plugin
<cr1901_modern> _destroys_ my mental* bandwidth, not internet b/w :P
balrog has quit [Ping timeout: 255 seconds]
balrog has joined #m-labs
balrog has quit [Ping timeout: 246 seconds]
balrog has joined #m-labs
balrog has quit [Ping timeout: 246 seconds]
balrog has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Remote host closed the connection]
<matterbridge-ml> [mattermost] <sb10q> sb10q updated the channel display name from: Town Square to: Main
<bb-m-labs> build #2502 of artiq-board is complete: Success [build successful] Build details are at https://buildbot.m-labs.hk/builders/artiq-board/builds/2502
<bb-m-labs> build #2984 of artiq is complete: Failure [failed python_unittest_2] Build details are at https://buildbot.m-labs.hk/builders/artiq/builds/2984 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<matterbridge-ml> [mattermost] <liqixue12> liqixue12 joined the team.
<matterbridge-ml> [mattermost] <kpwang> kpwang joined the team.
<matterbridge-ml> [mattermost] <sjm> sjm joined the team.
rohitksingh_work has joined #m-labs
_whitelogger has joined #m-labs
<matterbridge-ml> [mattermost] <quincyqin> quincyqin joined the team.
<matterbridge-ml> [mattermost] <zhulingxiao> zhulingxiao joined the team.
<lkcl> if bridging is going to be deployed can i make a recommendation that the notifications "XYZ joined the team" please be disabled?
<lkcl> otherwise people will be forced to write a filter program to get rid of what amounts to channel spam
* lkcl agrees with cr1901_modern that freenode is by far the de-facto medium for software libre projects
matterbridge-ml has quit [Remote host closed the connection]
mtrbot-ml has joined #m-labs
<mtrbot-ml> [mattermost] <sb10q> lkcl: I added NoSendJoinPart to the matterbridge options, hopefully that does it
<mtrbot-ml> [mattermost] <sb10q> lkcl: yes but many other people don't like IRC, hence, the bridging solution.
<mtrbot-ml> [mattermost] <sb10q> we should actually bridge to wechat as well, for that matter
m4ssi has joined #m-labs
<mtrbot-ml> [mattermost] <pkulik> pkulik joined the team.
<attie> doesn't seem to have worked
<attie> but those messages are only on sign-up so it should quiet down soon
<attie> certainly less frequent than IRC join/quits
<mtrbot-ml> [mattermost] <pkulik> @sb10q can I create a dedicated channel to Sayma & Metlino?
<mtrbot-ml> [mattermost] <sb10q> @pkulik just use this one for now. if the volume becomes a problem, we'll move to a dedicated channel
<mtrbot-ml> [mattermost] <pkulik> sure, however this way mattermost doesn't have any advantage over IRC (except maybe nicer formatting)
<mtrbot-ml> [mattermost] <pkulik> but we'll see if it's going to be used by people
<mtrbot-ml> [mattermost] <sb10q> it has backlog, phone apps, pictures, and many other features...
<mtrbot-ml> [mattermost] <sb10q> irc also supports multiple channels...
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
cedric has quit [Ping timeout: 246 seconds]
cedric has joined #m-labs
cedric has joined #m-labs
cedric has quit [Changing host]
cedric has quit [Ping timeout: 246 seconds]
cedric has joined #m-labs
cedric has joined #m-labs
cedric has quit [Changing host]
<mtrbot-ml> [mattermost] <pkulik> is there a way to use microscope with artiq on kasli?
<mtrbot-ml> [mattermost] <sb10q> @pkulik microscope needs a UART channel... you could disconnect the main UART (since the logs are available from the network anyway, that will work unless you are debugging some firmware crash) or connect the UART elsewhere
<mtrbot-ml> [mattermost] <pkulik> ok, I was hoping for a way without disconnecting uart :)
<mtrbot-ml> [mattermost] <sb10q> you can also put a USB-UART cable on EEM pins
<mtrbot-ml> [mattermost] <sb10q> for microscope
cr1901_modern1 has joined #m-labs
<mtrbot-ml> [mattermost] <sb10q> or implement microscope-over-JTAG, but it's more work
cr1901_modern has quit [Ping timeout: 258 seconds]
cr1901_modern1 has quit [Quit: Leaving.]
cr1901_modern has joined #m-labs
<cr1901_modern> How many ppl are in the bridge right now? 70 ppl is pretty good for an IRC channel :)
<cr1901_modern> err in the Mattermost chat*, not the bridge.
<mtrbot-ml> [mattermost] <pkulik> there are 10 members in this chat, however 4 are online
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
<mtrbot-ml> [mattermost] <sb10q> testing picture uploadtesting picture upload:
<travis-ci> oli-obk/smoltcp#1 (patch-1 - b8578e1 : Oliver Scherer): The build passed.
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has joined #m-labs
<lkcl> thanks sb0
<lkcl> attie: i use an intelligent plugin to hexchat that monitors login/exits, and instead of a flood of messages it summarises them.
rohitksingh has quit [Ping timeout: 246 seconds]
sb0 has joined #m-labs
<mtrbot-ml> [mattermost] <astro> astro joined the team.
m4ssi has quit [Remote host closed the connection]
<ZirconiumX> So, after nmigen was mentioned, I took a look at it, and it seems to be a rewrite/redesign of migen. Should I learn migen or nmigen? It'd suck to familiarise myself with the old way and it not work with the new way.
<whitequark> I'd say nmigen, but I'm biased :)
<whitequark> nmigen eliminates a lot of pain points in migen, but it's not yet quite complete enough for real-world designs
sb0 has quit [Remote host closed the connection]
<whitequark> however, if you are still learning migen and/or digital logic it'll probably be complete faster than you can learn
<key2> whitequark: any example of how to generate a inout with nmigen curently ?
<ZirconiumX> Thanks for the advice, whitequark
<whitequark> key2: inouts are only supported for instances
<whitequark> so if you have an instance using io_PACKAGE_PIN=x, then x will become an inout
<key2> there is an example somewher ?
<whitequark> you can also do frag.add_ports(foo, dir="io")
<key2> whitequark: but you have no example anywhere ?
<whitequark> no
rohitksingh has joined #m-labs
<mtrbot-ml> [mattermost] <emusan> emusan joined the team.
rohitksingh has quit [Ping timeout: 244 seconds]
rohitksingh has joined #m-labs
<mtrbot-ml> [mattermost] <rohitksingh> rohitksingh joined the team.
rohitksingh has quit [Read error: Connection reset by peer]
futarisIRCcloud has joined #m-labs