whitequark changed the topic of #amaranth-lang to: Amaranth hardware definition language · weekly meetings on Mondays at 1700 UTC · code https://github.com/amaranth-lang · logs https://libera.irclog.whitequark.org/amaranth-lang
<_whitenotifier-6> [YoWASP/yosys] whitequark pushed 1 commit to develop [+0/-0/±1] https://github.com/YoWASP/yosys/compare/7f43eaa0553a...de11a07479d0
<_whitenotifier-6> [YoWASP/yosys] whitequark de11a07 - Update dependencies.
Lord_Nightmare has quit [Quit: ZNC - http://znc.in]
Lord_Nightmare has joined #amaranth-lang
Darius has quit [Ping timeout: 246 seconds]
Darius has joined #amaranth-lang
cr1901_ has joined #amaranth-lang
cr1901 has quit [Ping timeout: 240 seconds]
alanvgreen has quit [Server closed connection]
alanvgreen has joined #amaranth-lang
Sarayan has joined #amaranth-lang
Degi has joined #amaranth-lang
<fl4shk[m]> I still need to read the RFC
<fl4shk[m]> I read part of it
<fl4shk[m]> but not all of it
V has quit [Server closed connection]
V has joined #amaranth-lang
balrog has quit [Ping timeout: 255 seconds]
mindw0rk has quit [Read error: Connection reset by peer]
mindw0rk has joined #amaranth-lang
mindw0rk has quit [Ping timeout: 250 seconds]
mindw0rk has joined #amaranth-lang
jjsuperpower has joined #amaranth-lang
balrog has joined #amaranth-lang
jjsuperpower has quit [Ping timeout: 250 seconds]
jjsuperpower has joined #amaranth-lang
toshywoshy has quit [Server closed connection]
toshywoshy has joined #amaranth-lang
jjsuperpower has quit [Ping timeout: 250 seconds]
feldim2425 has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
feldim2425 has joined #amaranth-lang
<_whitenotifier-6> [amaranth-boards] VIPQualityPost opened pull request #224: Add Alchitry Cu board file. - https://github.com/amaranth-lang/amaranth-boards/pull/224
<_whitenotifier-6> [amaranth-boards] VIPQualityPost commented on pull request #224: Add Alchitry Cu board file. - https://github.com/amaranth-lang/amaranth-boards/pull/224#issuecomment-1606324029
cr1901_ is now known as cr1901
<d1b2> <vipqualitypost> so I finished the boardfile for the AlchitryCuPlatform. I was thinking it would be nice to make another file which allows support of the Alchitry IO board. This board can be shared between the Au/ Cu. What would be the best way to do this? Should I make another class like AlchitryIOPlatform? Or is there a way to set up a file that just contains something like [platform].add_resources for each board? Since the board fits two
<d1b2> different carriers it has a fixed pinout so I don't want to cook a specific file for each platform with the actual pin connections.
<whitequark> tbh we don't currently have a good or well known solution for it, i guess just put it in a separate file?
<d1b2> <vipqualitypost> ok, i'll tinker with some stuff and see if i can find a nice way to do this
<cr1901> Mercury baseboard was put into the same file when I wrote the board file for mercury
<whitequark> yeah but there's two Alchitry platforms
<cr1901> Ahhh I see