| *** jacobk <jacobk!~quassel@64.189.201.150> has quit IRC | 00:43 | |
| *** jacobk <jacobk!~quassel@utdpat242032.utdallas.edu> has joined #f4pga | 01:04 | |
| *** jacobk <jacobk!~quassel@utdpat242032.utdallas.edu> has quit IRC | 01:24 | |
| *** jacobk <jacobk!~quassel@64.189.201.150> has joined #f4pga | 04:08 | |
| *** TMM_ <TMM_!hp@amanda.tmm.cx> has quit IRC | 11:34 | |
| *** TMM_ <TMM_!hp@amanda.tmm.cx> has joined #f4pga | 11:34 | |
| *** indy <indy!~indy@dsl-static-104.213-160-167.telecom.sk> has quit IRC | 11:52 | |
| *** indy <indy!~indy@dsl-static-104.213-160-167.telecom.sk> has joined #f4pga | 11:59 | |
| F4PGASlackBridge | <kboronski> @ept a bit late reply, but nextpnr does sort-of have a packing stage. The thing is that it's not generic and the implementation is architecture-dependent code. Nextpnr has that thing called "Arch API" which separates generic code from code that's written specifically for a given architecture. The "pack" stage is just a procedure from that API invoked before placement and that's it. | 13:08 |
|---|---|---|
| F4PGASlackBridge | <ethanrcampbell02> Hi, I was wondering if there are any current plans to add Project X-Ray documentation for the xc7k160t. If not, how much work would the process of running the fuzzers myself be expected to be, considering there already seems to be support for the 70t? | 19:05 |
| *** jacobk <jacobk!~quassel@64.189.201.150> has quit IRC | 20:13 | |
| *** jacobk <jacobk!~quassel@64.189.201.150> has joined #f4pga | 20:21 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC | 22:38 | |
| *** DrWhax <DrWhax!~DrWhax@37.218.247.209> has quit IRC | 22:41 | |
| *** DrWhax <DrWhax!~DrWhax@37.218.247.209> has joined #f4pga | 22:41 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #f4pga | 22:41 | |
| *** TMM_ <TMM_!hp@amanda.tmm.cx> has quit IRC | 23:44 | |
| *** TMM_ <TMM_!hp@amanda.tmm.cx> has joined #f4pga | 23:44 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!