21:21 <MrTrueDev> Is Litex known to work on with the full open source nextpnr-xilinx flow?

21:25 <MrTrueDev> And if so, I'm wondering how much success folks have had when it comes to DDR on say an artix digilent boards?

21:55 <somlo> MrTrueDev: If you dig through the LiteX commits, I remember seeing something about nextpnr-xilinx floating by. As for "full support" I really don't know, and will defer to _florent_ or gatecat

21:56 <MrTrueDev> So I see this: https://github.com/enjoy-digital/litex/blob/master/litex/build/xilinx/yosys_nextpnr.py

21:56 <MrTrueDev> I'm trying to determine if it shows up in Litex-boards however. Namely, here: https://github.com/litex-hub/litex-boards/tree/master/litex_boards/platforms

21:56 <somlo> I will have a month worth of my time available to actually get to the bottom of this question for myself -- I currently have access to a nexys video and a genesys2 board, be nice if I can get one of them to run self-hosting litex/rocket :)

21:57 <somlo> that's probably the commit I saw -- but I never had the cycles to try myself, always used vivado with xilinx up till now

21:58 <somlo> AFAIK, nextpnr-xilinx is a forked nextpnr repo that never got merged back into "official" nextpnr (again, take anything I say right now with a grain of salt)

21:58 <MrTrueDev> Self hosting Litex?

21:58 <MrTrueDev> Like run hosts on software?

21:58 <MrTrueDev> softcore

21:58 <somlo> how well it actually works, and which chips it supports, is still TBD as far as I'm aware

21:59 <somlo> nope, self-hosting as in "able to rebuild itself, on itself" (English has poor "linguistic/conceptual resolution" when things like self-hosting, or "free" for that matter, are used in conversation :D

22:00 <somlo> compiler people say "self hosting" when a compiler is written in its own language and its binary can (re-)build its own sources

22:01 <MrTrueDev> I see I had typos above

22:01 <somlo> so imagine extending that property to the whole software stack (system libraries and kernel supporting the compiler's execution), and then further down to the "gateware" on top of which the software stack is running

22:01 <MrTrueDev> I meant running Litex build on softcore on FPGA

22:02 <MrTrueDev> WRT earlier question:

22:02 <MrTrueDev> 1. https://github.com/enjoy-digital/litex/issues/1174

22:02 <MrTrueDev> 2. https://github.com/enjoy-digital/litex/pull/1180

22:02 <somlo> yeah, run a linux distro on a litex+cpu system, then run yosys/nextpnr on that linux distro to rebuild the underlying litex bitstream

22:02 <MrTrueDev> Seems that it is conceptually supported, although you may have to edit the build files yourself? And as such, YMMV

22:05 <somlo> yeah, I don't know how big the gap is between "conceptually supported" and "here's how it's done on a board I have, or can easily buy" -- but I'm planning to find out soon-ish :)

22:05 <MrTrueDev> So you might run something like this https://github.com/litex-hub/litex-boards/blob/master/litex_boards/targets/digilent_basys3.py with:

22:05 <MrTrueDev> python3 digilent_basys3.py --build --toolchain=symbiflow

22:08 <somlo> presumably after building/installing nextpnr-xilinx (plus whatever dependencies that requires)