| *** tpb has joined #symbiflow | 00:00 | |
| *** sxpert has joined #symbiflow | 00:42 | |
| *** citypw has joined #symbiflow | 03:42 | |
| *** kraiskil_ has joined #symbiflow | 07:43 | |
| *** TT_ has joined #symbiflow | 09:09 | |
| *** TT_ has quit IRC | 09:10 | |
| *** kgugala has joined #symbiflow | 10:02 | |
| *** citypw has quit IRC | 10:10 | |
| *** kraiskil_ has quit IRC | 10:37 | |
| *** _whitelogger has quit IRC | 12:27 | |
| *** _whitelogger has joined #symbiflow | 12:30 | |
| *** citypw has joined #symbiflow | 13:09 | |
| *** kraiskil_ has joined #symbiflow | 13:29 | |
| *** kraiskil_ has quit IRC | 14:39 | |
| mithro | Morning everyone! | 14:53 |
|---|---|---|
| *** kraiskil_ has joined #symbiflow | 14:53 | |
| nats` | morning:) | 14:55 |
| mithro | nats`: Happy to chat nowish if you want | 14:55 |
| *** kraiskil_ has quit IRC | 15:09 | |
| *** citypw has quit IRC | 15:15 | |
| *** kraiskil_ has joined #symbiflow | 15:20 | |
| digshadow | noopwafel: https://github.com/SymbiFlow/prjxray/issues/444 | 15:41 |
| tpb | Title: tilegrid: automatically generate number of frames · Issue #444 · SymbiFlow/prjxray · GitHub (at github.com) | 15:41 |
| digshadow | got a chance to write up my proposal | 15:41 |
| 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 | 15:41 |
| noopwafel | that looks very doable and v.easy to check | 15:48 |
| digshadow | cool :) | 16:06 |
| *** kraiskil_ has quit IRC | 16:58 | |
| *** kraiskil_ has joined #symbiflow | 17:22 | |
| *** kgugala has quit IRC | 17:31 | |
| *** litghost has joined #symbiflow | 18:28 | |
| *** kraiskil_ has quit IRC | 18:56 | |
| *** Rahix has quit IRC | 20:24 | |
| digshadow | nats`: fyi I'm doing a big rename right now | 22:08 |
| digshadow | heads up: major prjxray rename pull request: https://github.com/SymbiFlow/prjxray/pull/448 | 22:24 |
| tpb | Title: fuzzers: name with tile type by mcmasterg · Pull Request #448 · SymbiFlow/prjxray · GitHub (at github.com) | 22:24 |
| digshadow | noopwafel, nats` you will want to rebase when this is merged | 22:24 |
| nats` | a good occasion to learn how to rebase :D | 22:25 |
| noopwafel | ACK :) | 22:25 |
| digshadow | noopwafel: although if you are messing just with tilegrid it might not effect you (I didn't rename that) | 22:25 |
| nats` | maybe you should the need to install vivado 2017.2 in top of the readme | 22:27 |
| nats` | because it's so long it should be run before everything else :D | 22:27 |
| nats` | Step 1: | 22:28 |
| nats` | Install Vivado 2017.2. | 22:28 |
| nats` | with a highlight should I say | 22:28 |
| mithro | digshadow: Did my suggestion of splitting things into pips and non-pips make sense? | 22:28 |
| nats` | mentionning 2017.2 is mandatory because i'm pretty sure everybody will take at best the last 2017 | 22:28 |
| digshadow | nats`: is there something you think could be clarified in the readme | 22:29 |
| nats` | yep that 2017.2 is mandatory | 22:30 |
| nats` | I mean it's not highlighted | 22:30 |
| nats` | so I think people will just get the 2017.4 since on xilinx website you have to specifically go to archive | 22:30 |
| nats` | it's not that important but the install is so long that it could be boring | 22:31 |
| nats` | basically something like "2017.2 only because all other version are known to be non working" | 22:31 |
| nats` | maybe with the link to the bug report | 22:31 |
| digshadow | nats`: I originally had the link to the bug report in there, but IMHO it just clutters up the readme | 22:40 |
| mithro | digshadow: Should the tile type be `int` rather than `pip`? | 22:40 |
| nats` | fair enough | 22:40 |
| nats` | so maybe only making it more clear that 2017.2 is the only one supported | 22:41 |
| digshadow | I wouldn't be opposed to some emphasis verbage, but if user defies the readme, then *shrug* | 22:41 |
| digshadow | mithro: eh maybe. I was thinking the name in general might not be great | 22:41 |
| digshadow | we have other int as well possibly, so wasn't sure if that was vague as well | 22:41 |
| digshadow | today they were named "pip" so I just rolled with that | 22:41 |
| mithro | digshadow: It is unclear to me if these are targeting more than just the INT tiles? | 22:41 |
| sorear | are you talking about the version of vivado which is targeted by the fuzzer? | 22:41 |
| digshadow | sorear: yeah | 22:41 |
| mithro | I think saying that Vivado 2017.2 is required is probably a good addition | 22:42 |
| digshadow | mithro: it does say that...? | 22:43 |
| digshadow | step 1: "Install Vivado 2017.2" | 22:43 |
| mithro | digshadow: Being explicit that it is *exactly* 2017.2 and not "implicitly" 2017.2 or later version is helpful | 22:44 |
| digshadow | sure, thats what I meant by clarifying verbage | 22:44 |
| mithro | Great first patch for someone :-P | 22:45 |
| mithro | digshadow: If I do a db build at the moment, it should be expected to run all the way to the end, right? | 22:46 |
| digshadow | mithro: maybe? I just renamed a ton of stuff | 22:47 |
| mithro | digshadow: Well, I'm actually running just before your rename | 22:47 |
| digshadow | FYI there is a known issue on VCC wires | 22:48 |
| digshadow | pips | 22:48 |
| digshadow | it might complete, but the database will be known bad | 22:48 |
| nats` | <mithro> Great first patch for someone :-P <= My job is done I can go away in peace like the greatest Samourai :D | 22:48 |
| digshadow | https://github.com/SymbiFlow/prjxray/issues/440 | 22:49 |
| tpb | Title: Broken VCC_WIRE entries in database · Issue #440 · SymbiFlow/prjxray · GitHub (at github.com) | 22:49 |
| nats` | someone can buy a decent ethernet link for Xilinx ? | 22:53 |
| nats` | they are hosted on an ADSL... | 22:53 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!