Monday, 2023-04-24

*** tpb <[email protected]> has joined #litex00:00
*** Degi <[email protected]> has quit IRC (Ping timeout: 276 seconds)01:24
*** Degi_ <[email protected]> has joined #litex01:24
*** Degi_ is now known as Degi01:24
*** bl0x_ <[email protected]> has joined #litex01:47
*** bl0x <[email protected]> has quit IRC (Ping timeout: 264 seconds)01:49
*** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)02:03
*** TMM_ <[email protected]> has joined #litex02:03
*** benh <[email protected]> has quit IRC (Ping timeout: 255 seconds)05:58
*** benh_ <[email protected]> has joined #litex05:58
MelkhiorHello, NuBusFPGA V1.2 has landed, now giving credit where credit is due: https://github.com/rdolbeau/NuBusFPGA/blob/master/Pictures/NuBusFPGA_V1_2.jpg :-)06:24
*** jk- <[email protected]> has quit IRC (Ping timeout: 240 seconds)08:09
*** jk- <[email protected]> has joined #litex08:09
_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.08:58
_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.08:59
_florent_Melkhior: Nice! Thanks.09:00
somlo_florent_: I'm working on updating it to match the latest changes to the original version (lots of modifications to the platform file)11:44
somloonce 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 :)11:44
minute_florent_: cool! we're shipping some RKX7s now so i was re-trying everything again11:55
minute_florent_: ddr3 rate is still tied to cpu mhz, right?11:55
minutesome 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 DTS13:49
minuteand: 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?13:49
*** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)13:58
*** TMM_ <[email protected]> has joined #litex13:58
*** so-offish <[email protected]> has joined #litex15:13
*** so-offish <[email protected]> has quit IRC (Ping timeout: 255 seconds)15:18
minuteah, litex_json2dts_linux.py looks for "spiflash" in d["csr_bases"], but that's not a thing (anymore), there's spiflash_core and spiflash_phy16:02
*** somlo <[email protected]> has quit IRC (Read error: Connection reset by peer)16:09
*** somlo <[email protected]> has joined #litex16:12
minuteah so i'm hitting the same problem now https://github.com/litex-hub/linux-on-litex-vexriscv/issues/235#issuecomment-92586084416:42
minute_florent_: i suspect there's no updated linux driver for spi flash with litespi?16:42
_florent_somlo: ok good, if boards are totally different, I'm fine with a v2 platform/target16:51
_florent_minute: yes, ddr3 rate is still related to cpu freq (1:4 ratio on Kintex7)16:52
_florent_minute: For the number of HARTs with opensbi, that's probably here:16:53
_florent_https://github.com/litex-hub/opensbi/blob/0.8-linux-on-litex-vexriscv/platform/litex/vexriscv/platform.c#L2116:53
_florent_to recompile: https://github.com/litex-hub/linux-on-litex-vexriscv#-generating-the-opensbi-binary-optional16:53
_florent_Not sure I tested spiflash recently... 16:54
minute_florent_: thanks16:55
minute_florent_: is the "litex,spiflash" driver meant for "spiflash_core", "spiflash_phy" or do i have to use a different driver nowadays?16:56
_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 regression16:57
_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 :)16:58
_florent_minute: that's possible it was for the spiflash core that was used before switching to LiteSPI on targets16:59
_florent_minute: and this core has probably been remove from litex repo since was no longer used in boards17:00
minute_florent_: oh nice @ CI!17:02
_florent_minute: so we should probably remove spiflash support from the Linux-on-LiteX-Vexriscv README until someone look at it17:02
*** so-offish <so-offish!~so-offish@2610:148:610:2b11::e> has joined #litex17:33
*** bl0x_ <[email protected]> has quit IRC (Ping timeout: 240 seconds)18:10
*** ILoveScotch <[email protected]> has quit IRC (Quit: Client closed)18:54
*** a3f is now known as a3f[m]18:59
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #litex19:05
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 255 seconds)19:07
*** so-offish <so-offish!~so-offish@2610:148:610:2b11::e> has quit IRC (Read error: Connection reset by peer)19:40
cr1901Is there a litescope verilog core generator, like how there's lite*_gen.exe for dram, eth, pcie, etc?20:03
*** so-offish <so-offish!~so-offish@2610:148:610:2b11::e> has joined #litex20:27
*** so-offish <so-offish!~so-offish@2610:148:610:2b11::e> has quit IRC (Read error: Connection reset by peer)21:59

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