*** tpb <[email protected]> has joined #litex | 00:00 | |
*** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 00:19 | |
*** TMM_ <[email protected]> has joined #litex | 00:19 | |
*** so-offishul <[email protected]> has joined #litex | 00:27 | |
*** so-offish <so-offish!~so-offish@2610:148:610:2b11::11> has quit IRC (Ping timeout: 246 seconds) | 00:31 | |
*** Degi <[email protected]> has quit IRC (Ping timeout: 240 seconds) | 00:37 | |
*** Degi <[email protected]> has joined #litex | 00:39 | |
*** dark_star <[email protected]> has quit IRC (Ping timeout: 240 seconds) | 07:46 | |
*** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 14:10 | |
*** TMM_ <[email protected]> has joined #litex | 14:10 | |
*** so-offish1 <so-offish1!~so-offish@2610:148:610:2b11::17> has joined #litex | 15:10 | |
*** so-offishul <[email protected]> has quit IRC (Ping timeout: 240 seconds) | 15:13 | |
*** so-offish1 <so-offish1!~so-offish@2610:148:610:2b11::17> has quit IRC (Client Quit) | 15:14 | |
*** dark_star <[email protected]> has joined #litex | 15:23 | |
*** dark_star_1 <[email protected]> has joined #litex | 15:27 | |
*** dark_star <[email protected]> has quit IRC (Ping timeout: 240 seconds) | 15:28 | |
*** dark_star_2 <[email protected]> has joined #litex | 15:32 | |
*** dark_star_1 <[email protected]> has quit IRC (Ping timeout: 250 seconds) | 15:35 | |
*** so-offish <so-offish!~so-offish@2610:148:610:2b11::17> has joined #litex | 16:13 | |
*** dark_star_2 <[email protected]> has quit IRC (Ping timeout: 240 seconds) | 18:03 | |
*** pharonix71 <pharonix71!~pharonix7@user/pharonix71> has quit IRC (Remote host closed the connection) | 18:10 | |
*** pharonix71 <pharonix71!~pharonix7@user/pharonix71> has joined #litex | 18:10 | |
*** dark_star_2 <[email protected]> has joined #litex | 19:06 | |
amstan | sigh, why is this so hard? (not litex in particular) | 20:56 |
---|---|---|
amstan | i'm trying to simulate some verilog and run it in the context of a python module and every system out there (verilator, cocotb) has some kind of big blocker | 20:57 |
amstan | cocotb wants to take over the world and execution context, so i can't just call into verilog and return to some oblivious parent python function with the answer | 20:58 |
amstan | verilator is all C++ so it's hard to call from python without more wrapper work that needs to be custom coded per verilog module | 20:58 |
amstan | pyverilator doesn't even run, something sketchy with the tcl libraries it uses | 20:59 |
*** dark_star_2 <[email protected]> has quit IRC (Ping timeout: 246 seconds) | 21:11 | |
mithro | Most of the functionality in these pipelines is implemented by (common) plugins, inspired by the plugin-based design of **VexRiscv**. | 22:00 |
mithro | https://mici.hu/papers/bognar23proteus.pdf - Proteus: An Extensible RISC-V Core for Hardware Extensions | 22:00 |
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:6198:7d26:5f37:f25a> has quit IRC (Quit: Leaving) | 22:24 | |
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:cc09:34c3:7b50:cf94> has joined #litex | 22:26 | |
*** dark_star_2 <[email protected]> has joined #litex | 22:39 | |
*** dark_star_2 <[email protected]> has quit IRC (Ping timeout: 240 seconds) | 22:52 | |
*** dark_star_2 <[email protected]> has joined #litex | 23:33 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!