sb0 changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs :: Due to spam bots, only registered users can talk. See: https://freenode.net/kb/answer/registration
gildarts24 has joined #m-labs
gildarts24 has quit [Killed (Unit193 (Spam is not permitted on freenode.))]
jem18 has joined #m-labs
jem18 has quit [Ping timeout: 268 seconds]
ovrstorm has joined #m-labs
ovrstorm has quit [Killed (Sigyn (Spam is off topic on freenode.))]
johnlage23 has joined #m-labs
johnlage23 has quit [Remote host closed the connection]
Zx328 has joined #m-labs
Zx328 has quit [Killed (Sigyn (Spam is off topic on freenode.))]
jrg has joined #m-labs
jrg has quit [Remote host closed the connection]
<GitHub-m-labs> [artiq] sbourdeauducq commented on pull request #1115 61d1a5c: Should the frequent use case be ``channel.count(channel.gate_rising(10*us))`` or ``channel.gate_rising(10*us); channel.count()``?... https://github.com/m-labs/artiq/pull/1115#discussion_r207083628
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1115: Fine except for what has already been said. https://github.com/m-labs/artiq/pull/1115#issuecomment-409783034
Hobbyboy0 has joined #m-labs
Hobbyboy0 has quit [Read error: Connection reset by peer]
StephenS14 has joined #m-labs
chaoscon10 has joined #m-labs
StephenS14 has quit [Ping timeout: 268 seconds]
chaoscon10 has quit [Ping timeout: 260 seconds]
<GitHub-m-labs> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/c659ae06812a59ef9ebdbe3a8a93ae6737a8465e
<GitHub-m-labs> artiq/release-3 c659ae0 Sebastien Bourdeauducq: firmware: actually compact in config::compact().
FiendKing04 has joined #m-labs
rohitksingh_work has joined #m-labs
FiendKing04 has quit [Killed (Sigyn (Spam is off topic on freenode.))]
Asorailahd has joined #m-labs
Asorailahd has quit [K-Lined]
<bb-m-labs> build #1749 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1749
<bb-m-labs> build #2538 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2538 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
jesse12 has joined #m-labs
jesse12 has quit [Ping timeout: 256 seconds]
kaolpr has joined #m-labs
<kaolpr> what is the easiest way to access CSR from ARTIQ experiment?
Croepha16 has joined #m-labs
Croepha16 has quit [K-Lined]
supercool2 has joined #m-labs
supercool2 has quit [Remote host closed the connection]
Cisien9 has joined #m-labs
Cisien9 has quit [Killed (Unit193 (Spam is not permitted on freenode.))]
albel72720 has joined #m-labs
albel72720 has quit [Remote host closed the connection]
bairdmich has joined #m-labs
bairdmich has quit [Killed (Sigyn (Spam is off topic on freenode.))]
<rjo> sb0: that connection reset was with a known-goot gs110tp (the same things that i have been using). when icleaned up the vlan setup there it disappeared. i think some packets went wrong and the keepalive killed it. not really sure though how much to attribute to smoltcp since everything else was working fine.
hartytp has joined #m-labs
<rjo> sb0: do we have an issue for that thing occuring with shaky wifi?
<sb0> rjo, no; not sure if that's the device's fault...
<sb0> there is generally a non-negligible packet loss rate on that wifi
ErrantEgo has joined #m-labs
ErrantEgo is now known as Guest28996
\mSg0 has joined #m-labs
Guest28996 has quit [Killed (Sigyn (Spam is off topic on freenode.))]
<rjo> sb0: christian had the artiq network on a vlan and the rest on another. on the link between his pc and the switch he was running the artiq vlan tagged and the other network untagged. i changed it to both tagged and the problem disappeared. but that should definitely not affect tcp keepalive on the artiq connection.
\mSg0 has quit [Killed (Sigyn (Spam is off topic on freenode.))]
<sb0> could be different problems too...
<rjo> i'll post the packet dump when i get it.
hartytp has quit [Quit: Page closed]
<rjo> other than that grabber looks good. two things: i am pretty sure the pixel duplication is a way to comply with the cl spec. the adc is running at 30 MHz (in that case) and the min cl freq is ~40 MHz. so they just send each pixel twice to double the frequency. checked that the lines get correspondingly longer if i reduce the adc freq.
hartytp has joined #m-labs
<rjo> i.e. three times the pixels on 20 MHz etc
hartytp has quit [Client Quit]
<rjo> christian asked for a way to get notified when the resolution changes. i wouldn't add that to the rtio interface because it'll become difficult to use. the easiest, least intrusive and most useful way seems to just log resolution changes in the grabber runtime task.
<rjo> and we should add one example.
Guest50138 has joined #m-labs
<GitHub-m-labs> [artiq] jordens opened issue #1120: grabber: log resolution changes https://github.com/m-labs/artiq/issues/1120
<GitHub-m-labs> [artiq] jordens opened issue #1121: grabber: add an example experiment https://github.com/m-labs/artiq/issues/1121
Guest50138 has quit [Ping timeout: 245 seconds]
Deusdeorum28 has joined #m-labs
Deusdeorum28 has quit [Ping timeout: 264 seconds]
rohitksingh_work has quit [Read error: Connection reset by peer]
qew has joined #m-labs
qew has quit [Killed (Sigyn (Spam is off topic on freenode.))]
kaolpr has quit [Quit: Konversation terminated!]
FiendKing04 has joined #m-labs
FiendKing04 has quit [Remote host closed the connection]
johnny5619 has joined #m-labs
johnny5619 has quit [Ping timeout: 265 seconds]
<GitHub-m-labs> [artiq] jordens commented on pull request #1115 61d1a5c: I'm ok with dropping the default for `up_to_timestamp`. That would also prevent a few more cases of the original problem of silently assuming that the count end time can be handled automatically (in DMA or with multiple gates). https://github.com/m-labs/artiq/pull/1115#discussion_r207170911
wgma has joined #m-labs
wgma has quit [Killed (Sigyn (Spam is off topic on freenode.))]
ptx026 has joined #m-labs
ptx026 has quit [Killed (Unit193 (Spam is not permitted on freenode.))]
Arokh21 has joined #m-labs
Arokh21 has quit [Killed (Unit193 (Spam is not permitted on freenode.))]
mumptai has joined #m-labs
mumptai has left #m-labs [#m-labs]
Nightmare14 has joined #m-labs
Nightmare14 has quit [Read error: Connection reset by peer]
X-Scale has quit [Ping timeout: 264 seconds]
<GitHub-m-labs> [artiq] jordens closed issue #595: digital camera/frame grabber support https://github.com/m-labs/artiq/issues/595
<GitHub-m-labs> [artiq] cjbe opened pull request #1122: share moninj injection state between dashboards (master...moninj_injection) https://github.com/m-labs/artiq/pull/1122
cjbe has joined #m-labs
Immune has joined #m-labs
Immune has quit [Remote host closed the connection]
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1122: > With the current implementation the modifying client receives a notification of its change up to 200ms after the change, which means that the dashboard moninj panel cannot be used to generate events faster than 200ms.... https://github.com/m-labs/artiq/pull/1122#issuecomment-409889363
<GitHub-m-labs> [artiq] sbourdeauducq commented on pull request #1122 cd9f832: Can we avoid breaking compatibility with the current protocol? https://github.com/m-labs/artiq/pull/1122#discussion_r207185930
tpw_rules has quit [Ping timeout: 240 seconds]
<cjbe> sb0, rjo: FWIW we also see connection resets on our Kaslis at a rate of ~1/day per Kasli when running experiments on a wired network through a couple of switches - have not managed to get a packet dump yet
tpw_rules has joined #m-labs
<GitHub-m-labs> [artiq] cjbe commented on pull request #1122 cd9f832: OK - permuting the packet numbering would allow new firmware with the old dashboard. New dashboard and old firmware would always break things though (firmware aborts connection on unknown packet type). https://github.com/m-labs/artiq/pull/1122#discussion_r207188129
<GitHub-m-labs> [artiq] sbourdeauducq commented on pull request #1122 cd9f832: OK, that's acceptable. https://github.com/m-labs/artiq/pull/1122#discussion_r207188411
<GitHub-m-labs> [artiq] sbourdeauducq commented on pull request #1122 cd9f832: This also prevents any unexpected injections at dashboard startup. https://github.com/m-labs/artiq/pull/1122#discussion_r207188623
<rjo> cjbe: any non-trivial vlan configuration?
<GitHub-m-labs> [artiq] jordens pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/5871d13da829...7d6a1b528d6c
<GitHub-m-labs> artiq/master e518a1f Robert Jördens: ad53xx: also increase slack after control readback
<GitHub-m-labs> artiq/master 7d6a1b5 Robert Jördens: ad9912: add ftw_to_frequency
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1122: Thanks! https://github.com/m-labs/artiq/pull/1122#issuecomment-409896258
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1112: Can you update this to your new input API? https://github.com/m-labs/artiq/pull/1112#issuecomment-409896925
ollien has joined #m-labs
<GitHub-m-labs> [artiq] klickverbot closed pull request #1112: test_rtio: Add loopback test using DMA (master...dma-loopback-test) https://github.com/m-labs/artiq/pull/1112
<cjbe> rjo: the Kasli and master are on the same VLAN - the configuration of this is out of my control, but I don't think it is doing anything exceptional
Smeef22 has joined #m-labs
Smeef22 has quit [Remote host closed the connection]
ollien has quit [Ping timeout: 240 seconds]
<rjo> cjbe: there is no vlan tagging on the linux machine going on?
<bb-m-labs> build #1750 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1750
<bb-m-labs> build #925 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/925
<bb-m-labs> build #2539 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2539
Guest97794 has joined #m-labs
Guest97794 has quit [Killed (Unit193 (Spam is not permitted on freenode.))]
burnout_ has joined #m-labs
burnout_ has quit [Ping timeout: 268 seconds]
<rjo> bb-m-labs: force build --props=package=artiq-board,artiq_target=kasli,artiq_variant=opticlock artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<bb-m-labs> build #1751 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1751
<bb-m-labs> build forced [ETA 20m32s]
<bb-m-labs> I'll give a shout when the build finishes
GorillaWarfare2 has joined #m-labs
GorillaWarfare2 has quit [Remote host closed the connection]
fkz has joined #m-labs
fkz has quit [Killed (Sigyn (Spam is off topic on freenode.))]
rohitksingh has joined #m-labs
<bb-m-labs> build #1752 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1752
<bb-m-labs> build #926 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/926
<bb-m-labs> build #2540 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2540
dx13 has joined #m-labs
X-Scale has joined #m-labs
dx13 has quit [Ping timeout: 265 seconds]
Ragnor26 has joined #m-labs
Ragnor26 has quit [Remote host closed the connection]
Gurty has quit [Ping timeout: 245 seconds]
Gurty has joined #m-labs
Gurty has quit [Changing host]
Gurty has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
<GitHub-m-labs> [artiq] jordens opened issue #1123: emtpy "raise" panics kernel cpu https://github.com/m-labs/artiq/issues/1123
Tools26 has joined #m-labs
Tools26 has quit [Killed (Unit193 (Spam is not permitted on freenode.))]
rohitksingh has joined #m-labs
key2 has quit [Ping timeout: 252 seconds]
SlashLife25 has joined #m-labs
SlashLife25 has quit [Remote host closed the connection]
Liara- has joined #m-labs
Liara- has quit [Remote host closed the connection]
uberardy has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
<uberardy> hey, maybe a bit off-topic, we're using migen in an open source project and I happen to be in Hong Kong at the moment, so I was wondering wheter I could stop by the office some time just to say hi?
key2 has joined #m-labs
Minkar has joined #m-labs
Minkar has quit [Remote host closed the connection]
rohitksingh has joined #m-labs
<GitHub164> [smoltcp] astro commented on issue #186: Rebased this one. https://github.com/m-labs/smoltcp/pull/186#issuecomment-409992357
gareth__26 has joined #m-labs
gareth__26 has quit [Remote host closed the connection]
uberardy has quit [Quit: uberardy]
uberardy has joined #m-labs
hartytp has joined #m-labs
<hartytp> kaolpr: have a look for register_kernel_cpu_csrdevice (github/irc)
<hartytp> basically, you need to
<hartytp> 1. add a memory region for your new crs
<hartytp> 2. create modules that inherit from AutoCSR and add them to your design
<hartytp> register them as kernel cpu devices
<hartytp> then expose them in api.rs
<hartytp> finally, you need to add a syscall to your experiment (see any of the core device drivers for examples)
<GitHub-m-labs> [artiq] klickverbot commented on issue #1123: This will be https://github.com/m-labs/artiq/blob/master/artiq/firmware/ksupport/eh.rs#L422. The correct fix would be just to check for an exception being present, and raising an error like you describe if there isn't. https://github.com/m-labs/artiq/issues/1123#issuecomment-410003982
hartytp has quit [Quit: Page closed]
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
cr1901 has joined #m-labs
<cjbe> rjo: As far as I can tell, no
rohitksingh has quit [Remote host closed the connection]