_florent_ changed the topic of #litex to: LiteX FPGA SoC builder and Cores / Github : https://github.com/enjoy-digital, https://github.com/litex-hub / Logs: https://libera.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
Degi has quit [Ping timeout: 276 seconds]
Degi_ has joined #litex
Degi_ is now known as Degi
bl0x_ has joined #litex
bl0x has quit [Ping timeout: 264 seconds]
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
benh has quit [Ping timeout: 255 seconds]
benh_ has joined #litex
<Melkhior> Hello, NuBusFPGA V1.2 has landed, now giving credit where credit is due: https://github.com/rdolbeau/NuBusFPGA/blob/master/Pictures/NuBusFPGA_V1_2.jpg :-)
jk- has quit [Ping timeout: 240 seconds]
jk- has joined #litex
<_florent_> minute: Thanks for reporting the issue on OHCI, I'll already integrated the workaround and will have a closer look at the real issue in the next days since I need to build some Linux SoCs.
<_florent_> somlo: Thanks for the STLV7325 PR, as discussed in the issue, I'm just wondering if the changes are important or not between the revisions, if not, we could eventually try to support revisions in the platforms/targets as we are doing for other boards.
<_florent_> Melkhior: Nice! Thanks.
<somlo> _florent_: I'm working on updating it to match the latest changes to the original version (lots of modifications to the platform file)
<somlo> once they're as close to each other as I can get them, I'll let you run diff and decide if it's worth combining or keeping separate :)
<minute> _florent_: cool! we're shipping some RKX7s now so i was re-trying everything again
<minute> _florent_: ddr3 rate is still tied to cpu mhz, right?
<minute> some more questions: linux-on-litex-vexriscv mentions spi flash to be accessible via /dev/mtd*, but that is not so... presumably something needs to be added to the DTS
<minute> and: even if i can p+r 16 vexrsicv cores, linux and opensbi only recognize (or have IDs) for 8 HARTs. what is the right place to increase this limit?
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
so-offish has joined #litex
so-offish has quit [Ping timeout: 255 seconds]
<minute> ah, litex_json2dts_linux.py looks for "spiflash" in d["csr_bases"], but that's not a thing (anymore), there's spiflash_core and spiflash_phy
somlo has quit [Read error: Connection reset by peer]
somlo has joined #litex
<minute> _florent_: i suspect there's no updated linux driver for spi flash with litespi?
<_florent_> somlo: ok good, if boards are totally different, I'm fine with a v2 platform/target
<_florent_> minute: yes, ddr3 rate is still related to cpu freq (1:4 ratio on Kintex7)
<_florent_> minute: For the number of HARTs with opensbi, that's probably here:
<_florent_> Not sure I tested spiflash recently...
<minute> _florent_: thanks
<minute> _florent_: is the "litex,spiflash" driver meant for "spiflash_core", "spiflash_phy" or do i have to use a different driver nowadays?
<_florent_> NLNet is going to help funding the development of hardware CI tests (in complement of the current simulation in CI), I'm planning to have a Linux-on-LiteX-VexRiscv hardware CI test, so this will help catching these kind of regression
<_florent_> somlo: While doing this, I'm also planning to automatically test Linux-LiteX-Rocket on hardware, this will avoid some tests on your side :)
<_florent_> minute: that's possible it was for the spiflash core that was used before switching to LiteSPI on targets
<_florent_> minute: and this core has probably been remove from litex repo since was no longer used in boards
<minute> _florent_: oh nice @ CI!
<_florent_> minute: so we should probably remove spiflash support from the Linux-on-LiteX-Vexriscv README until someone look at it
so-offish has joined #litex
bl0x_ has quit [Ping timeout: 240 seconds]
ILoveScotch has quit [Quit: Client closed]
a3f is now known as a3f[m]
GNUmoon2 has joined #litex
GNUmoon has quit [Ping timeout: 255 seconds]
so-offish has quit [Read error: Connection reset by peer]
<cr1901> Is there a litescope verilog core generator, like how there's lite*_gen.exe for dram, eth, pcie, etc?
so-offish has joined #litex
so-offish has quit [Read error: Connection reset by peer]