06:35 <_florent_> jevinskie[m]: this seems similar to https://github.com/enjoy-digital/litex/issues/249

06:37 <_florent_> jevinskie[m]: the is bit old and the woraround I suggested was related to migen IIRC, I could have a closer look if you want. If so, can you provide a minimal repro (what is generated vs what quartus needs?)

17:18 <jevinskie[m]> Sure, it’s using the new altera_pll and I found a workaround using string values “foo MHz” but I’ll send when I get back home

18:20 <bentomo> Hello, I've finally started scratching at litex with a need to use the litedram module and I'm trying to make sure I'm getting the flow right. I'm trying to use a yml based off of one of the examples but my modified one doesn't seem to generate what I expect. It seems the best way to figure out what parameters are supported is digging into the

18:20 <bentomo> source code. Is that a fair statement?

18:36 <jevinskie[m]> _florent_: more importantly, PRs #1323 and #1324 fix two issues I introduced in previous PRs. Sorry, mea culpa!

18:46 <somlo> _florent_ (or anyone else who might know): is there a way to turn on an arbitrary bios C #define (e.g. CONFIG_BIOS_NO_BOOT) from a litex-boards `--build` command line? Or does it need a dedicated addition to e.g. `builder_args` in e.g., litex/soc/integration/builder.py?

18:48 <somlo> along those same lines, in litex/soc/software/bios/main.c, we might want to consider wrapping the entire `static void boot_sequence()` definition in #ifndef CONFIG_BIOS_NO_BOOT ... #endif :)

18:49 <somlo> not sure if we're currently set up to get warnings for "dead code" functins that have no call sites anywhere else throughout the active sources...

18:50 <somlo> (I can add that #define at the top of bios/main.c by hand for my own experiments, but was wondering if there's a more "canonical" way of turning it on)

19:14 <jevinskie[m]> Can you use soc.add_config or add_constant? https://github.com/jevinskie/litex-boards/blob/32b40d771aed008b236fa11584932a042f875939/litex_boards/targets/altera_max10_dev_kit.py#L135

19:31 <somlo> jevinskie[m]: that's still an edit to some git tracked source file (qualitatively the same as if I'd just add `#define CONFIG_BIOS_NO_BOOT` to the top of litex/soc/software/bios/main.c, or not? I was wondering about the build command line itself (_florent_: NB, this is *not* a feature request, just a dumb question :D )

19:50 <_florent_> somlo: this could make sense to allow defining this from command line yes

20:41 <bentomo> _florent_ For the code in litedram under litdram/test/reference/ddr4_init.py and litdram/test/reference/ddr4_init.h, is there an example of how that makes it's way into a baremetal app and where the main.c would be? I'm trying to build a standalone ddr4 Xil MIG replacement that uses a SERV for initialization. But I'm new to both litex and migen.

20:41 <bentomo> Trying to soak up info myself but my cross compiler is still compiling:)

21:34 <mithro> It would be great to get https://docs.google.com/spreadsheets/d/1q5CUI289TjGw9c66wAesOHlvH8RVo-OK6_yJ4btzZPA/edit#gid=1200712426 updated

21:34 <tpb> Title: litex (liteDRAM, liteVideo, liteEth) Supported boards & Interfaces - Google Tabellen (at docs.google.com)