<tpb>
Title: unknown bit in zynq7 harness · Issue #746 · SymbiFlow/prjxray · GitHub (at github.com)
<litghost>
mithro: That includes that latest zynq update? Yuck
<litghost>
mithro: There are some GFAN errors in that update
<mithro>
litghost: Yes
<litghost>
mithro: zynq7/segbits_int_r.db
lopsided98 has joined #symbiflow
<mithro>
litghost: Yeah it seems that GFAN stuff isn't stable
<litghost>
mithro: It is a known issue. I think tmichalak is gonna try splitting out GFAN fuzzing from 050, which should hopefully fix that once and for all
<litghost>
*cross fingers*
Bertl is now known as Bertl_zZ
citypw has joined #symbiflow
futarisIRCcloud has joined #symbiflow
citypw has quit [Ping timeout: 272 seconds]
_whitelogger has joined #symbiflow
proteusguy has joined #symbiflow
proteusguy has quit [Remote host closed the connection]
proteusguy has joined #symbiflow
_whitelogger has joined #symbiflow
OmniMancer has joined #symbiflow
proteusguy has quit [Ping timeout: 255 seconds]
proteusguy has joined #symbiflow
shivm has joined #symbiflow
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
shivm has quit [Ping timeout: 256 seconds]
OmniMancer has quit [Quit: Leaving.]
Bertl_zZ is now known as Bertl
proteusguy has quit [Remote host closed the connection]
<sf-slack1>
<acomodi> upstream PR update: I have updated the PR with the `differing mode` issue fix after having modified the test `slicem.xml` architecture. I have tested that the regression tests relative to the patches do fail if the patches are not applied.
<sf-slack1>
<acomodi> *(upstream VPR update)
lethalbit has quit [Ping timeout: 252 seconds]
lethalbit has joined #symbiflow
<sf-slack1>
<acomodi> litghost, mithro: I am isolating the EBLIF write support patch. I need to create a regression test for it and than I'll open a new PR