<_whitenotifier-3>
[amaranth-lang/amaranth-lang.github.io] whitequark 3a1cbe7 - Deploying to main from @ amaranth-lang/rfcs@f4e3de1c3258957e948be3228b0f00975b25116b 🚀
frgo has joined #amaranth-lang
frgo_ has quit [Read error: Connection reset by peer]
Raito_Bezarius has quit [Ping timeout: 272 seconds]
Raito_Bezarius has joined #amaranth-lang
frgo_ has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
<bl0x[m]>
I'm updating a module from legacy Memory to the new Memory class (RFC 45). Do I have to use the new way of running simulations to properly simulate this new Memory? Or should the legacy simulation (with add_sync_process) still work?
frgo has joined #amaranth-lang
<whitequark[cis]>
the legacy simulations should still work
<whitequark[cis]>
they're emulated on top of the new ones
frgo has quit [Ping timeout: 245 seconds]
<bl0x[m]>
Hm, then for some reason I don't see anything on the read port.
<bl0x[m]>
Oops, did not add the Memory to m.submodules...
<bl0x[m]>
Works now.
<whitequark[cis]>
there should be a warning for that
<bl0x[m]>
Yes, in fact there was one. Above the backtrace. Meh, it's late.