Tuesday, 2020-09-01

*** tpb has joined #timvideos00:00
-_whitenotifier-3- [yosys] pull[bot] opened pull request #542: [pull] master from YosysHQ:master - https://git.io/JUmmC01:42
*** GNUmoon has quit IRC03:32
*** GNUmoon has joined #timvideos03:34
-_whitenotifier-3- [yosys] pull[bot] closed pull request #542: [pull] master from YosysHQ:master - https://git.io/JUmmC04:42
*** GNUmoon has quit IRC07:29
*** GNUmoon has joined #timvideos08:16
*** shenki has quit IRC11:05
*** shenki has joined #timvideos11:30
*** ChanServ sets mode: +v shenki11:30
*** cr1901_modern has quit IRC14:29
*** cr1901_modern has joined #timvideos14:31
*** FFY00 has quit IRC15:43
*** FFY00 has joined #timvideos15:43
*** FFY00 has quit IRC15:47
*** FFY00 has joined #timvideos15:47
-_whitenotifier-3- [yosys] pull[bot] opened pull request #543: [pull] master from YosysHQ:master - https://git.io/JUmND17:07
*** futarisIRCcloud has joined #timvideos17:07
*** cr1901_modern1 has joined #timvideos17:11
*** cr1901_modern has quit IRC17:12
*** CarlFK has quit IRC17:44
*** shorne has quit IRC17:44
*** titanbiscuit has quit IRC17:44
*** CarlFK has joined #timvideos17:46
*** shorne has joined #timvideos17:46
*** titanbiscuit has joined #timvideos17:46
*** kornbluth.freenode.net sets mode: +v CarlFK17:46
*** titanbiscuit has quit IRC17:46
*** titanbiscuit has joined #timvideos17:47
*** cr1901_modern1 has quit IRC19:04
*** cr1901_modern has joined #timvideos19:04
shornemithro: ok, I have it working, as you suggested earlier it would be good to have a linux-on-mor1kx project, ill also look at that19:17
*** futarisIRCcloud has quit IRC19:26
mithroshorne: Hi!19:31
mithroshorne: Long time no chat!19:31
mithroshorne: I would eventually like us to get back to having a "linux-on-litex" without a CPU in the name which supports rv32/64, ppc32/64, sh2/4 and mor1kx19:33
mithroshorne: But other people think that is "to complex", so it'll be a slow process19:36
daveshahDoes seem like  good idea long term19:38
daveshahMight as well add OpenSPARC to that list to round things off :)19:38
mithroDoes OpenSPARC fit on anything?19:38
mithroI guess FPGAs have gotten really big since OpenSPRAC was a thing....19:39
daveshahDefinitely it would fit on UltraScale stuff19:39
daveshahI think I looked at the smallest core config at was 2x ECP5 ish19:39
daveshahso high Artix-7 territory19:39
daveshahbut the fun multithreading etc wasn't included in that, that was many 100ks LUTs19:39
mithroYeah - ASIC designs, specially ASIC super-scalar CPU designs with things like many ported register files, map very poorly to FPGAs19:40
daveshahIndeed, my only interest in these is as PnR/synthesis torture tests, not anything practical :D19:42
shornemithro: I thought that was what we already had with litex-buildenv.  There was build-linux.sh that just worked.19:43
mithroshorne: Yes, but litex-buildenv is showing it's age with a huge mishmash of Python, shell, Make, etc19:44
daveshahDid that ever work for all arches?19:44
mithrodaveshah: It works for rv32 and mor1k19:44
daveshahI remember looking at it pre-linux-on-litex-vexriscv19:44
daveshahI see19:44
mithroEven did a tutorial about doing it -> https://github.com/timvideos/litex-buildenv/wiki/HowTo-LCA2018-FPGA-Miniconf19:45
tpbTitle: HowTo LCA2018 FPGA Miniconf · timvideos/litex-buildenv Wiki · GitHub (at github.com)19:45
cr1901_modernI wanted to replace litex-buildenv's logic with meson, but that went by the wayside for now19:45
mithroThe Antmicro team has updated that tutorial to use VexRISCV and Renode (rather than mor1kx and QEMU)19:45
cr1901_moderndoes lm32 still work?19:46
daveshahAh nice, that was probably after I looked19:46
shorneAh19:46
mithrodaveshah: The LCA2018 FPGA Miniconf was a big driver of getting all the mor1kx Linux stuff on LiteX working19:46
shornelm32 worked last I checked, but not the linux port19:46
mithroI'm not sure I can convince them (Antmicro) to add support for mor1kx into Renode, but I have insisted that they keep the build-linux.sh script working with mor1kx19:47
cr1901_modernwell yea I don't expect the linux port to work, Yann hasn't done anything w/ it for a while19:47
shornemithro: and it still works, I booted linux with the latest kernel patches19:47
shornehowever, the branch used in litex-buildenv does not boot19:47
shornehence I was asking if its still recommended19:48
shorneIll figure out what is wrong with the linux branch used in litex-buildenv.19:48
mithroshorne: Lots of people still have success with litex-buildenv, but it is not everyone's cup of tea19:49
mithroAnd I'm the first to say it needs to be rewritten19:49
daveshahRewritten, or work put into making LiteX itself more accessible instead?19:49
daveshahI would personally prefer to see more work on the latter19:49
cr1901_modernI would like to see all the cores use nmigen, even if only w/ the compat layer.19:50
daveshahYeah, that's been a somewhat longstanding discussion19:51
shorneI think the purpose of litex-buildenv was to make litex more accessible19:51
daveshahMy feeling is the best way to do that is to improve the main litex repo rather than have a separate thing, that risks causing ecosystem confusion19:51
shornei.e. it installs all of the python dependencies and gets it working, but I guess it hide a lot of the complexity, so when you really want to develop in litex you may not know where to start19:52
daveshahThere is now three-way duplication of platforms between litex, litex-boards and litex-buildenv19:52
daveshahThat doesn't seem ideal imo19:52
cr1901_moderndaveshah: I haven't worked on litex a lot since early 2019, but the PLAN was at the time for most litex boards to come straight from omigen19:53
cr1901_modernand subclassed if necessary to add litex-specific functionality19:53
cr1901_modernlitex-boards didn't exist back then, but I think the idea's the same >>19:53
daveshahI think things have diverged quite a bit since then, particularly with oMigen development slowing down19:53
cr1901_modernlitex targets have to be annotated with more info than the main repo boards19:54
cr1901_modernDunno a good way to do that besides subclassing or duplication19:54
daveshahbetween buildenv and litex? or between litex and migen19:54
cr1901_modernbetween litex and migen19:55
daveshahI think in that case duplication isn't too evil19:55
cr1901_moderndaveshah: Actually wait... it MIGHT'VE been between litex-buildenv and migen (sic)19:55
daveshahThe problem I have is mostly the duplication between litex-buildenv and litex/litex-boards19:56
cr1901_modernI'll go through my old PRs in a bit and give you a better answer19:56
daveshahIt feels like most of the litex-buildenv stuff should end up in litex-boards19:56
cr1901_modernthe litex-buildenv board files defined some C constants that were required to init the board19:57
cr1901_modernlike SPIflash number of cycles to delay19:57
mithro@daveshah We have a goal of excising platforms from litex-buildenv19:57
daveshahGreat!19:58
daveshahThat will already improve things a lot19:58
mithrolitex-buildenv predates litex-boards19:58
mithroInfact litex-buildenv predates LiteX IIRC19:58
cr1901_modernto use an analogy, if nmigen were to organically grow such functionality, those constants would probably be provided by nmigen-soc19:58
cr1901_modernYes, litex-buildenv descends from HDMI2USB build system19:59
cr1901_modernwhich in ancient times used misoc19:59
mithrocr1901_modern: I'm hoping that LiteSPI removes the need for a bunch of the constants19:59
* cr1901_modern nods19:59
cr1901_modernI'm just thinking out loud about how nmigen-soc would handle the same thing19:59
shorne]20:25
shornesorry, screen froze20:25
-_whitenotifier-3- [yosys] pull[bot] closed pull request #543: [pull] master from YosysHQ:master - https://git.io/JUmND20:58
*** GNUmoon has quit IRC21:54
*** GNUmoon has joined #timvideos22:44
*** levi has joined #timvideos23:01
*** cr1901_modern has quit IRC23:25
*** cr1901_modern has joined #timvideos23:41

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