cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #amaranth-lang
cr1901 has quit [Read error: Connection reset by peer]
_whitelogger has joined #amaranth-lang
cr1901 has joined #amaranth-lang
<benny2366[m]>
when I do ```from amaranth.sim import Simulator, Period``` I get ```ImportError: cannot import name
<benny2366[m]>
Period' from 'amaranth.sim `
<benny2366[m]>
```. and that comes from the docs so I must be missing something
<benny2366[m]>
or the docs needs updating
<vup>
benny2366[m]: you are probably reading the docs for a newer version than you have installed. `Period` is not in 0.5.x. The docs for the currently released version (0.5.4) can be found at https://amaranth-lang.org/docs/amaranth/v0.5.4/
<benny2366[m]>
and how do you check the version again?
<benny2366[m]>
ok and now apparently it's complaining about the platform.default_clk_frequency . is it because I'm not using the amaranth boards import?
<benny2366[m]>
nop that's not it
<benny2366[m]>
dam it
<benny2366[m]>
* dam it forgot sim.run() but still no fix so to speak
<vup>
if you run a design with the simulator it gets passed None as the platform
<benny2366[m]>
so I have to do something like this
frgo has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo_ has joined #amaranth-lang
frgo has quit [Ping timeout: 260 seconds]
frgo_ has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 260 seconds]
<RobTaylor[m]>
Catherine: any thoughts on allowing a metadata annotation to a Component itself, as well as on its signature members?
frgo has joined #amaranth-lang
<zyp[m]>
don't we already have that?
<zyp[m]>
I mean, the metadata is still attached to a signature, but you can also attach it to the toplevel signature of a component, not just signature members
<RobTaylor[m]>
zyp: oh, you're right. i misread the relevant line ><
<RobTaylor[m]>
zyp: thank you!
<zyp[m]>
speaking of annotations, I have some code that builds on amaranth-soc#58, expanding it with the possibility of attaching additional annotations to a memory map
<zyp[m]>
yeah, amaranth-soc#58 provides an annotation with the registers of e.g. a peripheral block, and being able to attach additional annotations to give peripheral-specific metadata is useful
<zyp[m]>
then when you export the metadata from the memory bus initiator's perspective, you get a nice hierarchy with everything