Saturday, 2020-10-10

*** tpb has joined #symbiflow00:00
*** juanmard has quit IRC00:13
*** OmniMancer has joined #symbiflow01:46
*** Degi has quit IRC02:26
*** Degi has joined #symbiflow02:27
*** kraiskil has quit IRC03:00
*** citypw has joined #symbiflow03:12
*** proteusguy has quit IRC04:43
*** az0re has quit IRC04:47
*** proteusguy has joined #symbiflow04:56
*** az0re has joined #symbiflow05:48
*** OmniMancer has quit IRC06:34
*** OmniMancer has joined #symbiflow06:49
*** kgugala_ has joined #symbiflow07:32
*** kraiskil has joined #symbiflow07:33
*** kgugala has quit IRC07:35
*** kgugala_ has quit IRC07:55
*** kgugala has joined #symbiflow07:55
*** kraiskil has quit IRC08:02
*** proteusguy has quit IRC08:06
*** proteusguy has joined #symbiflow08:18
*** ArturSwiderski has joined #symbiflow08:50
ArturSwiderskiMy request from yesterday to join the mailing list is still pending, so I didn't get any task for the time being, so I am leaving my email address here. If any of you can point me to tasks which I could possibly do it would be appreciated. I am interested in entry level tasks (c++ or  verilog ). My email : [email protected]08:52
*** ArturSwiderski has quit IRC08:52
*** ArturSwiderski has joined #symbiflow08:54
*** kgugala_ has joined #symbiflow09:01
*** ArturSwiderski has quit IRC09:01
*** kgugala has quit IRC09:03
sf-slack<pgielda> @ArturSwiderski there is not really a lot of movement on the mailing list... most of the communication happens here on irc and more importantly on github where the work happens. Personally, I would recommend starting with just trying to *use* (precompiled) Symbiflow toolchain (following the guidelines from https://github.com/symbiflow/symbiflow-examples) then figure out a part of the toolchain software stack (its09:04
sf-slackreally a lot of smaller projects) where you think you can contribute and then try to improve something small. Also we are always happy to see improvements (PRs) to documentation. There is never enough documentation ;)09:04
tpbTitle: GitHub - SymbiFlow/symbiflow-examples: Examples designs for showing different ways to use SymbiFlow toolchains. (at github.com)09:04
sf-slack<pgielda> There are also adjacent projects that you can try to contribute to (e.g. LiteX, a migen-based SoC generator that support Symbiflow - and many other toolchains). https://github.com/litex-hub https://github.com/enjoy-digital/litex09:06
tpbTitle: LiteX-Hub ยท GitHub (at github.com)09:06
sf-slack<pgielda> Important part of the flow is Verilog to Routing  -- https://github.com/verilog-to-routing/vtr-verilog-to-routing . This project is heavily developed by both contributors from Symbiflow and researchers and students of University of Toronto09:09
tpbTitle: GitHub - verilog-to-routing/vtr-verilog-to-routing: Verilog to Routing -- Open Source CAD Flow for FPGA Research (at github.com)09:09
sf-slack<pgielda> There is a number of papers published about VtR, I would suggest digging through those if you are interested in contributing there.09:10
*** citypw has quit IRC09:34
*** ArturSwiderski has joined #symbiflow09:59
ArturSwiderskiOk I will try  to get familiar with tool, before I was using Intel/Altera  vendor specific stuff10:03
*** ArturSwiderski has quit IRC10:34
LoftyWell, Intel stuff actually falls under Project Mistral, which I am (de facto) project lead for11:00
LoftyI have a few tasks that might be doable for others11:00
LoftyA rewrite of the infrastructure for Cyclone IV would probably be enough motivation to replace synth_intel11:06
*** ArturSwiderski has joined #symbiflow11:09
*** ArturSwiderski has quit IRC12:28
sf-slack<olof.kindgren> Ohh... Mistral - Cyclone, I get it! Wasn't the Intel documentation project called someting else, or do I remember that wrong?12:50
LoftyChibi was the Max V documentation project12:52
LoftyMistral is the Cyclone V documentation project12:53
sf-slack<olof.kindgren> Chibi..?12:53
*** titanbiscuit has quit IRC12:53
sf-slack<olof.kindgren> Ah. I see12:53
Lofty(a style of Japanese cartoon emphasising being small and cutesy)12:54
sf-slack<olof.kindgren> Thought it sounded familiar. I used to watch a lot of anime when I was younger12:59
sf-slack<mgielda> for me chibi only sounds familiar because of chibios13:00
*** umarcor has quit IRC13:03
*** ArturSwiderski has joined #symbiflow13:22
sf-slack<pgielda> http://chibios.sourceforge.net/docs3/rt/index.html13:44
tpbTitle: ChibiOS/RT: Introduction (at chibios.sourceforge.net)13:44
sf-slack<pgielda> "Chibi ? I didn't want a serious name for this project. It is the Japanese word for small as in small child. So ChibiOS/RT means small Real Time Operating System. "13:44
sf-slack<pgielda> ;)13:44
*** shivam has joined #symbiflow14:01
sf-slack<olof.kindgren> I was working as system architect at a large Japanese company a couple of years ago and named all parts of the system different things from Gundam in the hope that I would get some recognition. No one noticed a shit. So disappointed14:10
sf-slack<olof.kindgren> Like the sensors were called Newtype X, Z and ZZ and he control application was called psycommu14:13
sf-slack<mgielda> what can you do. some people just do not understand14:49
*** kgugala_ has quit IRC15:43
*** kgugala has joined #symbiflow15:45
*** OmniMancer has quit IRC16:41
*** james_lan has joined #symbiflow16:56
*** kraiskil has joined #symbiflow17:19
*** ArturSwiderski has quit IRC18:05
*** salarii has joined #symbiflow18:12
*** kraiskil has quit IRC18:51
*** salarii has quit IRC18:51
*** az0re has quit IRC20:39
*** shivam has quit IRC20:41
sf-slack<olof.kindgren> I think I'm having issues inferring 32-bit wide memories with byte enable. Is this a known issue?20:48
sf-slack<olof.kindgren> For the quicklogic backend I mean20:50
sf-slack<olof.kindgren> Hmm..might be my 2-bit memory that isn't inferred correctly actually. Too tired to look more at it now21:01
LoftyI don't think the QuickLogic backend infers memories at all22:15
*** kraiskil has joined #symbiflow22:21
*** kraiskil has quit IRC23:55

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!