| *** tpb has joined #vtr-dev | 00:00 | |
| *** digshadow has quit IRC | 01:00 | |
| *** digshadow has joined #vtr-dev | 04:57 | |
| *** digshadow has quit IRC | 11:19 | |
| *** digshadow has joined #vtr-dev | 11:33 | |
| *** digshadow has quit IRC | 11:35 | |
| *** digshadow has joined #vtr-dev | 11:38 | |
| *** digshadow has quit IRC | 11:42 | |
| *** ZipCPU has joined #vtr-dev | 13:57 | |
| *** vtrbot has quit IRC | 15:46 | |
| *** vtrbot has joined #vtr-dev | 15:47 | |
| *** vtrbot has quit IRC | 15:52 | |
| *** vtrbot has joined #vtr-dev | 16:08 | |
| *** digshadow has joined #vtr-dev | 17:12 | |
| *** digshadow has quit IRC | 18:32 | |
| mithro | kem_: Any idea why the .outputs end up getting called out:LED2 in the io.place file rather than just LED2? | 19:10 |
|---|---|---|
| kem_ | mithro: The name is ambiguous otherwise. VPR names each block by the first net which it drives. This means that, for example, the LUT/FF driving the output LED2 would be named 'LED2' (since that is the net that it drives). Since the output itself has no 'output nets' we just name it by prefixing the output name with 'out:'. | 19:14 |
| mithro | kem_: Makes it a bit awkward to generate the io.place file from a .pcf constraints as I will have to lookup the IO pin direction in the blif file... | 19:16 |
| *** digshadow has joined #vtr-dev | 21:55 | |
| *** digshadow has quit IRC | 23:59 | |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!