whitequark[cis] changed the topic of #amaranth-lang to: Amaranth hardware definition language · weekly meetings: Amaranth each Mon 1700 UTC, Amaranth SoC each Fri 1700 UTC · play https://amaranth-lang.org/play/ · code https://github.com/amaranth-lang · logs https://libera.catirclogs.org/amaranth-lang · Matrix #amaranth-lang:matrix.org
cr1901_ has quit [Read error: Connection reset by peer]
cr1901 has joined #amaranth-lang
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #amaranth-lang
Degi has quit [Ping timeout: 248 seconds]
Degi has joined #amaranth-lang
cr1901_ has joined #amaranth-lang
cr1901 has quit [Read error: Connection reset by peer]
frgo has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
d_olex has quit [Remote host closed the connection]
d_olex has joined #amaranth-lang
hexastorm has joined #amaranth-lang
<hexastorm> I have a question about RFC 55. My platform defines a "debug_spi" resource using Subsignal("sck", Pins("19", dir="i")), etc. When I do platform.request("debug_spi"), I get a deprecation warning about using dir="-" and amaranth.lib.io.*Buffer. What’s the correct way to handle this now?
<hexastorm> thanks; I defined the pins without dir, e.g. Subsignal("sck", Pins("19")), then used platform.request("debug_spi", dir="-") and wrapped with sck = Buffer("i", board_spi.sck) — works great now.
<whitequark[cis]> yep, that's right!
hexastorm has quit [Quit: Client closed]