*** tpb <[email protected]> has joined #yosys | 00:00 | |
*** notgull <notgull!~notgull@ec2-50-112-148-23.us-west-2.compute.amazonaws.com> has quit IRC (Ping timeout: 260 seconds) | 00:28 | |
*** notgull <notgull!~notgull@ec2-50-112-148-23.us-west-2.compute.amazonaws.com> has joined #yosys | 00:30 | |
*** citypw <citypw!~citypw@gateway/tor-sasl/citypw> has joined #yosys | 02:07 | |
*** citypw <citypw!~citypw@gateway/tor-sasl/citypw> has quit IRC (Ping timeout: 240 seconds) | 02:21 | |
*** FabM <FabM!~FabM@2a03:d604:103:600:2e60:8c7c:e8fb:7990> has joined #yosys | 07:14 | |
*** Guest17 <[email protected]> has joined #yosys | 08:04 | |
*** Guest17 <[email protected]> has quit IRC (Client Quit) | 08:07 | |
*** lexano <[email protected]> has quit IRC (Ping timeout: 245 seconds) | 08:19 | |
*** lexano <[email protected]> has joined #yosys | 08:33 | |
*** schaeg <schaeg!~anabrid@2a02:3036:264:70fa:5bba:5a59:3630:8c91> has joined #yosys | 10:12 | |
*** singham <[email protected]> has joined #yosys | 10:56 | |
singham | Hello | 10:56 |
---|---|---|
singham | Yosys is a fantastic initiative. I would love to be active here | 10:56 |
singham | In nextpnr, if someone can help me find the chipdb step, I can help by lowering it's required RAM usage by contributing | 10:57 |
singham | I have failed in past to build it on RPI3, and I failed yesterday to build it | 10:57 |
singham | I use currently hx8k board | 10:59 |
jn | what do you mean by the chipdb step, and by finding it? | 11:39 |
singham | The step which requires lots of RAM to build | 12:10 |
singham | The code in python program which uses memory | 12:11 |
singham | block of code. | 12:11 |
* singham was afk | 12:11 | |
*** singham <[email protected]> has quit IRC (Remote host closed the connection) | 13:23 | |
*** bjorkintosh <bjorkintosh!~bjork@user/bjorkintosh> has quit IRC (Quit: Leaving) | 16:15 | |
*** schaeg <schaeg!~anabrid@2a02:3036:264:70fa:5bba:5a59:3630:8c91> has quit IRC (Ping timeout: 245 seconds) | 16:41 | |
*** bjorkintosh <bjorkintosh!~bjork@2600:1700:5400:c80:c6e2:71ac:27e5:ca32> has joined #yosys | 16:44 | |
*** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (Ping timeout: 255 seconds) | 20:20 | |
*** tlwoerner <[email protected]> has quit IRC (Quit: Leaving) | 21:37 | |
*** tlwoerner <[email protected]> has joined #yosys | 21:37 | |
cr1901 | If I have two modules that are similar (same I/O ports), Is there a way to run a select query that will return "cells in one module but not the other"? | 21:43 |
lofty | cr1901: select syntax is hierarchical, so if you know the name of that module you can use `c:foo/*`, IIRC | 21:48 |
cr1901 | Hmmm, nope "select c:leds-bad/*" selects nothing | 21:52 |
cr1901 | "select leds-bad leds-good %i" returns nothing as well | 21:54 |
cr1901 | (although I guess that's not surprising, seeing that the intersection is technically... nothing. yosys can't figure out which cells are "the same" in between two modules) | 21:55 |
jix | cr1901: I don't think there is a way to do it with only a select query, but there might be other ways | 22:12 |
jix | also when do you consider a cell to be in both modules? will it have the same name? or do you want some structural comparison | 22:12 |
cr1901 | structural comparison | 22:17 |
*** ats <[email protected]> has quit IRC (Ping timeout: 256 seconds) | 23:03 | |
*** ats <[email protected]> has joined #yosys | 23:10 | |
*** nonchip <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 23:21 | |
*** nonchip <[email protected]> has joined #yosys | 23:21 | |
*** abradd <[email protected]> has joined #yosys | 23:25 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!