Wednesday, 2019-06-12

*** tpb has joined #symbiflow00:00
tpbTitle: Test 32-bit distributed RAM with larger designs · Issue #822 · SymbiFlow/symbiflow-arch-defs · GitHub (at
*** proteusguy has quit IRC00:38
*** proteusguy has joined #symbiflow00:50
*** futarisIRCcloud has joined #symbiflow01:42
*** Bertl_oO is now known as Bertl_zZ02:56
*** proteusguy has quit IRC03:07
*** proteusguy has joined #symbiflow03:19
*** citypw has joined #symbiflow03:22
*** futarisIRCcloud has quit IRC03:51
*** bjorkintosh has quit IRC03:58
*** bjorkintosh has joined #symbiflow04:00
*** proteusguy has quit IRC05:50
*** proteusguy has joined #symbiflow06:06
*** OmniMancer has joined #symbiflow07:04
*** citypw has quit IRC07:09
*** futarisIRCcloud has joined #symbiflow08:33
*** proteusguy has quit IRC09:06
*** OmniMancer1 has joined #symbiflow09:14
*** OmniMancer has quit IRC09:17
*** Bertl_zZ is now known as Bertl10:52
*** proteusguy has joined #symbiflow11:28
mithroFYI - I pushed a the latest database builds11:39
mithroduck2: How are things going?11:39
mithroduck2: Why is structure in structure not possible?11:40
*** futarisIRCcloud has quit IRC12:13
mithrotmichalak2: Could you go through all the issues on and make sure that they are still accurate?12:45
tpbTitle: GitHub - SymbiFlow/prjxray: Documenting the Xilinx 7-series bit-stream format. (at
sf-slack2<tmichalak> @mithro: sure, it will be good to have everything up to date12:46
mithrotmichalak: I try to do it every now and then, but never frequently enough12:46
sf-slack2<tmichalak> @mithro: that's natural, currently there is much to follow12:49
*** citypw has joined #symbiflow13:39
*** citypw has quit IRC14:06
duck2mithro: i'm just starting today's work. struct in struct is not possible for recursive types- for instance pb_type which can have more pb_types as children15:47
*** OmniMancer1 has quit IRC16:55
*** citypw has joined #symbiflow17:25
*** _whitelogger has quit IRC19:11
*** _whitelogger has joined #symbiflow19:14
*** proteusguy has quit IRC19:59
sf-slack2<tmichalak> @litghost: kokoro looks full or broken. Could you have a look and cancel all pending jobs?20:14
litghosttmichalak2: I see that is looks messed up, but @mithro will need to take a look20:16
plaesheya.. I've been trying to follow the prjxray Quickstart guide but there's something missing between 3rd and 4th step20:19
plaesstep3: Install cmake20:19
plaesstep4: Build the C++ tools: `make build`20:20
plaesthis fails20:20
plaesmake: *** No rule to make target 'build'.  Stop.20:20
plaesand on another note.. it seems that most of the stuff seems to work with Vivado 2019.1 :)20:30
sf-slack2<tmichalak> plaes: seems you are not calling make build from prjxay directory. Did you change the current working directory to prjxray?20:31
plaesah... I had ran 'cmake .' which overwrote Makefile :(20:34
sf-slack2<tmichalak> plaes: for now 2017.2 is used, mostly because of problems with newer version of the following type:
tpbTitle: MUXF8 vivado compatibility · Issue #14 · SymbiFlow/prjxray · GitHub (at
plaesyeah.. I read that issue20:42
plaes...after installation, so I thought that I should actually try it.. :)20:43
mithrotmichalak2: Do you still need me to look at something before I go to bed?21:23
sf-slack2<tmichalak> mithro: it would be great if you could have a look at the status of all current kokoro jobs and clean up the queue21:31

Generated by 2.13.1 by Marius Gedminas - find it at!