00:11 <_whitenotifier-f> [sphinx_symbiflow_theme] mithro opened issue #40: Make sure the paragraph mark is not copied - https://git.io/JUB43

01:37 <james_lan> I'm just getting into fpgas (I've got some low end zynqs), and I've been lurking a bit, trying to get a feel for what's going on, and it doesn't seem like much?

01:41 <sjkelly1> plenty :)

03:08 <user5> is anyone able to use simple browsers like links2 w3m dillo netsurf on risc-v softcore yet? is it still buggy if so?

03:09 <user5> also video watching tools like mpv, youtube-dl, vlc...any other one really...

13:40 <_whitenotifier-f> [symbiflow-arch-defs] rw1nkler opened issue #1668: Unresolved $_TBUF_ cells after Yosys synthesis - https://git.io/JUB7F

14:33 <_whitenotifier-f> [symbiflow-docs] mithro opened issue #348: Autoroll the submodules - https://git.io/JUBF7

14:40 <mithro> rwinker: You wanted me to fix the pypi upload for some packages, right?

14:42 <sf-slack> <rwinkler> mithro: Yes, could you create a token for sphinx-verilog-domain deployment? https://github.com/SymbiFlow/sphinx-verilog-domain

14:42 <tpb> Title: GitHub - SymbiFlow/sphinx-verilog-domain (at github.com)

14:45 <_whitenotifier-f> [sphinx-verilog-domain] mithro opened issue #14: Add "make upload" target - https://git.io/JUBbK

14:50 <mithro> rwinkler: doing now

14:59 <sf-slack> <rwinkler> mithro: Thanks! There is also a compatibility package in sphinxcontrib-verilog-diagrams that needs to be pushed to PyPI

15:01 <mithro> rwinkler: verilog-domain and verilog-diagrams is very close :-P

15:02 <mithro> rwinkler: I just noticed https://github.com/SymbiFlow/sphinxcontrib-verilog-diagrams/blob/master/Makefile#L23

15:02 <tpb> Title: sphinxcontrib-verilog-diagrams/Makefile at master · SymbiFlow/sphinxcontrib-verilog-diagrams · GitHub (at github.com)

15:03 <mithro> Hrm.... - I just needed to reload my page...

15:05 <sf-slack> <rwinkler> mithro: We change it already to sphinxcontrib-hdl-diagrams. The compatibility package is currently named sphinxcontrib-verilog-diagrams and it is just a wrapper on sphinxcontrib-hdl-diagrams with the message about depreciated package.

15:05 <mithro> rwinkler: Yeah - I thought you had missed a name change but I just looking at an old HTML page it seems

15:08 <mithro> rwinkler: I'm a bit confused about what just happened - I tried an `make upload_compat` and it seems to have uploaded a `sphinxcontrib_verilog_diagrams-0.1.0` rather than a `sphinxcontrib_verilog_diagrams-0.0.post71` like expected?

15:10 <sf-slack> <rwinkler> I fixed the package version on `0.1.0` since it is just a wrapper that should not change, and maybe should be removed in the future

15:10 <mithro> rwinkler: Maybe it is caused by me not doing a make clean first...

15:21 <sf-slack> <rwinkler> mithro: I believe that the current errors on Travis CI with sphinxcontrib-verilog-diagrams(https://github.com/SymbiFlow/sphinxcontrib-verilog-diagrams), are caused by the old repository name: https://github.com/SymbiFlow/sphinxcontrib-hdl-diagrams/blob/master/Makefile#L25

15:21 <tpb> Title: GitHub - SymbiFlow/sphinxcontrib-hdl-diagrams: Sphinx Extension which generates various types of diagrams from Verilog code. (at github.com)

15:21 <mithro> rwinkler: Do you have a readthedocs account?

15:22 <sf-slack> <rwinkler> mithro: Yes `rw1nkler` same login as on GitHub

15:31 <sf-slack> <mgielda> h4x0r

15:31 <mithro> rwinkler: Going through and adding you as a maintainer to all our readthedocs sites

15:37 <mithro> rwinkler: You should have a *lot* more repos at readthedocs.org now

15:38 <_whitenotifier-f> [sphinxcontrib-hdl-diagrams] mithro opened issue #60: Set up redirection from sphinxcontrib-verilog-diagrams.readthedocs.org to sphinxcontrib-hdl-diagrams.readthedocs.org - https://git.io/JUBxT

18:12 <mithro> rwinkler: I believe I have uploaded the PyPi packages for sphinxverilog-hdl-diagrams and sphinx-verilog-domain

18:15 <_whitenotifier-f> [sphinxcontrib-hdl-diagrams] mithro opened issue #61: Fix codecov badge - https://git.io/JURvb

18:21 <mithro> rwinkler: Can you check?

18:21 <sf-slack> <rwinkler> mithro: Thanks. Yes, both of the packages are available on PyPI. Now, I can also see a lot of symbiflow projects on readthedocs. So everything works!

18:22 <mithro> We should get the rest of the Python packages under the SymbiFlow organization also being uploaded like this

18:27 <sf-slack> <rwinkler> mithro: Sure! It should be simple. I will check the other SymbiFlow projects

23:19 <dbobrek> Hello! I was wondering, is the Digilent Arty A7-100T supported?

23:19 <litghost> It is supported right now?

23:19 <sf-slack> <timo.callahan> dbobrek: Yes

23:19 <dbobrek> Okay. I wasn't sure because it wasn't listed on the main site, but the A7-35T was.

23:19 <dbobrek> Thanks!

23:19 <sf-slack> <timo.callahan> symbiflow-examples has a counter example, let me get the link

23:20 <dbobrek> Also, why is the Block RAM only listed as partially supported under Project X-Ray?

23:20 <sf-slack> <timo.callahan> https://github.com/SymbiFlow/symbiflow-examples -- if you scroll down, look for TARGET="arty_100"

23:20 <tpb> Title: GitHub - SymbiFlow/symbiflow-examples: Examples designs for showing different ways to use SymbiFlow toolchains. (at github.com)

23:21 <dbobrek> Thanks for the link

23:23 <sf-slack> <timo.callahan> Note the instructions are still a little incorrect. It helps if you download the repo first thing.

23:28 <sf-slack> <timo.callahan> Currently the instructions have you install Symbiflow under /opt, and unless you're logged in as root, you'll need some 'sudo's. But you can also try installing under your home directory (change INSTALL\_DIR)

23:29 <dbobrek> Is there any benefit one way or the other?

23:35 <sf-slack> <timo.callahan> dbobrek: the advantage to installing under /opt is that has been tested a bit more. The advantage to installing under your home directory is that you're not giving sudo permission to install scripts downloaded off of the internet :).

23:35 <sf-slack> <timo.callahan> dbobrek: It would be great if you're willing to try the user install, and let me know of any issues

23:37 <dbobrek> I'll probably go ahead an install it tonight then. However, I don't have a Symbiflow-compatible board right now. I popped in to ask about compatibility because I was about to buy an Arty board, so actually putting something on a device will have to wait.

23:42 <sf-slack> <timo.callahan> Yeah, makes sense to wait then

23:43 <sf-slack> <timo.callahan> I'll be around, and maybe the README will be improved by then. I have another example in the pipeline -- a Linux build.

23:43 <dbobrek> Cool!

23:59 <sf-slack> <timo.callahan> dbobrek: rereading what I wrote, it was a bit ambiguous. I meant, you may as well wait until you have the board before installing Symbiflow. And in case you're new to playing with real boards (like I was just a few months ago), you might find these super-basic intros useful: https://github.com/tcal-x/misc/ -- they apply to either Arty A7 board, 35T or 100T. However, they do assume you're running Linux

23:59 <sf-slack> (Debian/Ubuntu ideally).

23:59 <tpb> Title: GitHub - tcal-x/misc: Random stuff -- small demos/tutorials, etc. (at github.com)