sxpert has joined #symbiflow
citypw has joined #symbiflow
kraiskil_ has joined #symbiflow
TT_ has joined #symbiflow
TT_ has quit [Client Quit]
kgugala has joined #symbiflow
citypw has quit [Ping timeout: 258 seconds]
kraiskil_ has quit [Ping timeout: 244 seconds]
_whitelogger has joined #symbiflow
citypw has joined #symbiflow
kraiskil_ has joined #symbiflow
kraiskil_ has quit [Ping timeout: 240 seconds]
<mithro> Morning everyone!
kraiskil_ has joined #symbiflow
<nats`> morning:)
<mithro> nats`: Happy to chat nowish if you want
kraiskil_ has quit [Ping timeout: 258 seconds]
citypw has quit [Ping timeout: 268 seconds]
kraiskil_ has joined #symbiflow
<tpb> Title: tilegrid: automatically generate number of frames · Issue #444 · SymbiFlow/prjxray · GitHub (at github.com)
<digshadow> got a chance to write up my proposal
<digshadow> please check that out when you get some time and see if that looks of interest. This should simplify adding IP blocks to tilegrid
<noopwafel> that looks very doable and v.easy to check
<digshadow> cool :)
kraiskil_ has quit [Read error: Connection reset by peer]
kraiskil_ has joined #symbiflow
kgugala has quit [Ping timeout: 256 seconds]
litghost has joined #symbiflow
kraiskil_ has quit [Ping timeout: 268 seconds]
Rahix has quit [Quit: Rahix]
<digshadow> nats`: fyi I'm doing a big rename right now
<digshadow> heads up: major prjxray rename pull request: https://github.com/SymbiFlow/prjxray/pull/448
<tpb> Title: fuzzers: name with tile type by mcmasterg · Pull Request #448 · SymbiFlow/prjxray · GitHub (at github.com)
<digshadow> noopwafel, nats` you will want to rebase when this is merged
<nats`> a good occasion to learn how to rebase :D
<noopwafel> ACK :)
<digshadow> noopwafel: although if you are messing just with tilegrid it might not effect you (I didn't rename that)
<nats`> maybe you should the need to install vivado 2017.2 in top of the readme
<nats`> because it's so long it should be run before everything else :D
<nats`> Step 1:
<nats`> Install Vivado 2017.2.
<nats`> with a highlight should I say
<mithro> digshadow: Did my suggestion of splitting things into pips and non-pips make sense?
<nats`> mentionning 2017.2 is mandatory because i'm pretty sure everybody will take at best the last 2017
<digshadow> nats`: is there something you think could be clarified in the readme
<nats`> yep that 2017.2 is mandatory
<nats`> I mean it's not highlighted
<nats`> so I think people will just get the 2017.4 since on xilinx website you have to specifically go to archive
<nats`> it's not that important but the install is so long that it could be boring
<nats`> basically something like "2017.2 only because all other version are known to be non working"
<nats`> maybe with the link to the bug report
<digshadow> nats`: I originally had the link to the bug report in there, but IMHO it just clutters up the readme
<mithro> digshadow: Should the tile type be `int` rather than `pip`?
<nats`> fair enough
<nats`> so maybe only making it more clear that 2017.2 is the only one supported
<digshadow> I wouldn't be opposed to some emphasis verbage, but if user defies the readme, then *shrug*
<digshadow> mithro: eh maybe. I was thinking the name in general might not be great
<digshadow> we have other int as well possibly, so wasn't sure if that was vague as well
<digshadow> today they were named "pip" so I just rolled with that
<mithro> digshadow: It is unclear to me if these are targeting more than just the INT tiles?
<sorear> are you talking about the version of vivado which is targeted by the fuzzer?
<digshadow> sorear: yeah
<mithro> I think saying that Vivado 2017.2 is required is probably a good addition
<digshadow> mithro: it does say that...?
<digshadow> step 1: "Install Vivado 2017.2"
<mithro> digshadow: Being explicit that it is *exactly* 2017.2 and not "implicitly" 2017.2 or later version is helpful
<digshadow> sure, thats what I meant by clarifying verbage
<mithro> Great first patch for someone :-P
<mithro> digshadow: If I do a db build at the moment, it should be expected to run all the way to the end, right?
<digshadow> mithro: maybe? I just renamed a ton of stuff
<mithro> digshadow: Well, I'm actually running just before your rename
<digshadow> FYI there is a known issue on VCC wires
<digshadow> pips
<digshadow> it might complete, but the database will be known bad
<nats`> <mithro> Great first patch for someone :-P <= My job is done I can go away in peace like the greatest Samourai :D
<tpb> Title: Broken VCC_WIRE entries in database · Issue #440 · SymbiFlow/prjxray · GitHub (at github.com)
<nats`> someone can buy a decent ethernet link for Xilinx ?
<nats`> they are hosted on an ADSL...
tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow