| *** tpb has joined #symbiflow | 00:00 | |
| *** az0re has quit IRC | 00:14 | |
| *** az0re has joined #symbiflow | 00:45 | |
| *** Degi has quit IRC | 01:06 | |
| *** yeti has quit IRC | 01:07 | |
| *** m_hackerfoo has quit IRC | 01:13 | |
| *** sjkelly1 has joined #symbiflow | 01:20 | |
| *** sjkelly1 has quit IRC | 01:22 | |
| *** xobs1 has quit IRC | 01:22 | |
| *** unrznbl[m] has quit IRC | 01:23 | |
| *** m_hackerfoo has joined #symbiflow | 01:24 | |
| *** lambda has quit IRC | 01:24 | |
| *** az0re has quit IRC | 01:25 | |
| *** az0re has joined #symbiflow | 01:26 | |
| *** xobs1 has joined #symbiflow | 01:36 | |
| *** lambda has joined #symbiflow | 01:38 | |
| *** unrznbl[m] has joined #symbiflow | 01:42 | |
| *** yeti has joined #symbiflow | 02:11 | |
| *** Degi has joined #symbiflow | 02:12 | |
| *** unrznbl[m] has quit IRC | 02:14 | |
| *** perillamint has quit IRC | 02:14 | |
| *** daveshah has quit IRC | 02:14 | |
| *** mats has quit IRC | 02:14 | |
| *** tannewt has quit IRC | 02:14 | |
| *** guan has quit IRC | 02:14 | |
| *** benreynwar has quit IRC | 02:14 | |
| *** _whitelogger has quit IRC | 02:14 | |
| *** kmehall_ has quit IRC | 02:14 | |
| *** benreynwar has joined #symbiflow | 02:15 | |
| *** guan has joined #symbiflow | 02:15 | |
| *** tannewt has joined #symbiflow | 02:15 | |
| *** perillamint has joined #symbiflow | 02:15 | |
| *** mats has joined #symbiflow | 02:15 | |
| *** daveshah has joined #symbiflow | 02:15 | |
| *** unrznbl[m] has joined #symbiflow | 02:16 | |
| *** _whitelogger has joined #symbiflow | 02:17 | |
| *** kmehall_ has joined #symbiflow | 02:20 | |
| *** Degi has quit IRC | 02:47 | |
| *** Degi has joined #symbiflow | 02:50 | |
| *** _whitelogger has quit IRC | 03:39 | |
| *** _whitelogger has joined #symbiflow | 03:41 | |
| *** az0re has quit IRC | 04:02 | |
| *** az0re has joined #symbiflow | 04:49 | |
| *** diamondman has quit IRC | 06:20 | |
| *** diamondman has joined #symbiflow | 06:20 | |
| *** enriq has joined #symbiflow | 06:56 | |
| *** OmniMancer has joined #symbiflow | 06:58 | |
| *** enriq has quit IRC | 07:32 | |
| *** kraiskil has quit IRC | 08:21 | |
| *** enriq has joined #symbiflow | 08:43 | |
| *** enriq has quit IRC | 08:53 | |
| *** enriq has joined #symbiflow | 09:18 | |
| *** citypw has joined #symbiflow | 10:51 | |
| *** enriq has quit IRC | 13:03 | |
| *** enriq has joined #symbiflow | 13:07 | |
| *** enriq has quit IRC | 13:26 | |
| *** enriq has joined #symbiflow | 14:30 | |
| *** OmniMancer has quit IRC | 14:58 | |
| *** kgugala has quit IRC | 15:24 | |
| *** kraiskil has joined #symbiflow | 15:40 | |
| *** citypw has quit IRC | 16:30 | |
| mithro | https://github.com/Blinkinlabs/QL-EOS-S3-breakout | 16:30 |
|---|---|---|
| tpb | Title: GitHub - Blinkinlabs/QL-EOS-S3-breakout (at github.com) | 16:30 |
| litghost | nelson: What are your questions around tileconn? The code for generating it is located https://github.com/SymbiFlow/prjxray/blob/master/fuzzers/074-dump_all/generate_grid.py | 16:42 |
| tpb | Title: prjxray/generate_grid.py at master · SymbiFlow/prjxray · GitHub (at github.com) | 16:42 |
| litghost | nelson: The code in prjuray for generating tileconn is a little more general, and I think better, but they both handle the same kind of processing. | 16:42 |
| *** kraiskil has quit IRC | 17:22 | |
| sf-slack | <nelson> I did see that previously, just trying to make sense of what I am seeing. In xc7a100tcsg324-1/tileconn.json, the combination [0,1] (CLBLL_L, CLBLL_L) (line 100215 in the latest version I checked out), is confusing me. The source wire is called “CLBLL_LL_CIN” and the dest wire is called “CLBLL_LL_COUT_N”. That seems backwards to me. I assume the source wire would be who is driving the wire and dest would be | 17:31 |
| sf-slack | who is sinking the value. Am I looking at it wrong? Thanks! | 17:31 |
| litghost | nelson: tileconn has no directions | 17:33 |
| litghost | nelson: The pairs are undirected | 17:33 |
| *** kgugala has joined #symbiflow | 17:34 | |
| *** kraiskil has joined #symbiflow | 17:35 | |
| sf-slack | <nelson> Thanks - I was wondering that (it was the only plausible explanation). So, the terms source and dest in the documentation could just be tile1, tile2? | 17:35 |
| litghost | nelson: Ya | 17:35 |
| *** maartenBE has quit IRC | 18:46 | |
| *** maartenBE has joined #symbiflow | 18:48 | |
| -_whitenotifier-f- [symbiflow-arch-defs] andrewb1999 opened issue #1684: Support BRAM_Rs - https://git.io/JUyOT | 19:12 | |
| -_whitenotifier-f- [symbiflow-arch-defs] andrewb1999 opened issue #1685: Reduce lookahead creation time for partition regions - https://git.io/JUyOD | 19:18 | |
| *** enriq has quit IRC | 19:52 | |
| *** enriq has joined #symbiflow | 19:59 | |
| sf-slack | <nelson> Thanks. So, if the connections are directionless should I expect the same number of entries to show up in these two sets: INT_R,INT_R with offset [0, -1] and INT_R, INT_R with offset [0,1]? But they are different. Can you explain this? | 20:50 |
| *** enriq has quit IRC | 20:51 | |
| litghost | nelson: Not at all | 20:59 |
| litghost | nelson: tileconn is simply one of many possible folded representations of the graph. A normalization pass over tileconn might produce what you are expecting, but in the end it has little meaning | 21:00 |
| litghost | nelson: tileconn can only be considered in its totality when applied to a particular grid | 21:01 |
| litghost | nelson: Individual patterns or rules don't have particular mean | 21:01 |
| *** enriq has joined #symbiflow | 21:59 | |
| sf-slack | <nelson> What I decided to do to learn about the data structures was to see if I could come up with a list of all the wires connecting two adjacent INT_R tiles. Seems pretty basic. So, I grabbed all the INT_R,INT_R [0, -1] wire pairs and thought that was the list of all wires between them. But I see that the set of wires in INT_R,INT_R [0, 1] is different, suggesting neither set of wires is the entire set of connections. It | 22:03 |
| sf-slack | would seem that there must be additional information that tells what connections *actually* exist between any 2 adjacent INT_R tiles. My question is what is that information and how is it derived? Thanks. | 22:03 |
| litghost | nelson: The answer to your question is possible, but it requires converting tileconn into the full node map | 22:06 |
| litghost | nelson: So in your specific example, there are many tiles between two INT_R's, and tileconn may form the node 1 tile at a time | 22:06 |
| litghost | nelson: I guess you are focused on the +/-1 y case | 22:07 |
| sf-slack | <nelson> I am, I figured just trying to understand how to interpret adjacent tiles… | 22:07 |
| litghost | nelson: Anyways, the answer to you question can be easily solved using the connection database formed by symbiflow-arch-defs or xc-fasm2bels | 22:08 |
| litghost | nelson: Because what you are asking for is the set of nodes that contain wires for INT_R dx,dy and INT_R dx,dy+1 | 22:08 |
| litghost | nelson: I don't believe you can do that by examining tileconn directly | 22:09 |
| litghost | nelson: Also it varies depending on where you are in the grid | 22:09 |
| litghost | nelson: But you could limit yourself to the examples that exist between all north/south adcent INT_R tiles | 22:09 |
| *** enriq has quit IRC | 22:09 | |
| sf-slack | <nelson> OK, make a bit more sense. Can you point me to that other database and the code that generates it? Just trying to understand how the pieces fit together, what combination of things gives information once could traverse to combine wires in the device into nodes, etc. | 22:13 |
| litghost | https://github.com/SymbiFlow/symbiflow-xc-fasm2bels/blob/3b72e6f5beb09d85d2ba2957282ef2cf13933b0c/fasm2bels/database/create_channels.py#L309-L354 | 22:14 |
| tpb | Title: symbiflow-xc-fasm2bels/create_channels.py at 3b72e6f5beb09d85d2ba2957282ef2cf13933b0c · SymbiFlow/symbiflow-xc-fasm2bels · GitHub (at github.com) | 22:14 |
| *** kraiskil has quit IRC | 22:26 | |
| *** kraiskil has joined #symbiflow | 22:39 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!