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 · code https://github.com/amaranth-lang · logs https://libera.irclog.whitequark.org/amaranth-lang · Matrix #amaranth-lang:matrix.org
<_whitenotifier> [amaranth-lang/rfcs] whitequark pushed 1 commit to interfaces [+0/-0/±1] https://github.com/amaranth-lang/rfcs/compare/1f6c8277dfab...c53abf78f7ca
<_whitenotifier> [amaranth-lang/rfcs] whitequark c53abf7 - add (back) unresolved question about `transpose`
<cr1901> What happened in 4 days where transpose went from "least bad" to "really bad"? lol
<whitequark[cis]> experience
zyp[m] has joined #amaranth-lang
<zyp[m]> did we already shoot down reverse()?
<whitequark[cis]> Python has reversed in the prelude
<zyp[m]> ah, yeah, and it can mean bit order, right
<whitequark[cis]> yea
<cr1901> Couldn't tell you why, but I find the change in opinion amusing/funny. My humor must be broken.
<cr1901> Unfortunately, that was the best synonym for evert I saw
<whitequark[cis]> try looking for synonyms for other words
<cr1901> There's other words?
<whitequark[cis]> honestly, "flipped" might be least bad
<zyp[m]> well, it is analogous of flipping a signature
<whitequark[cis]> the reason I think "transpose" is bad is because we have multi-dimensional arrays right there, and "transpose" means a very specific thing for ndarrays
<whitequark[cis]> ndarrays are rarely used but as I was documenting it, I realized just how bad "transpose" is
<whitequark[cis]> and it's not any more intuitive than "flipped". less if anything
<cr1901> what is a transpose for an ndarray?
<whitequark[cis]> I think we can just go with "flipped" :s
<whitequark[cis]> cr1901: matrix transposition
<cr1901> ah that makes sense for 2d
<cr1901> overturn is a synonym for flipped that you liked. https://www.thesaurus.com/browse/flipped
<cr1901> As is inverted. Absolutely nothing wrong w/ that one, right? :)
<cr1901> Yea, I'd say consult a thesaurus for a few words that are bad/reserved, pick synonyms, and we vote on the ones you like whenever bikeshed time is again
<whitequark[cis]> "capsized"
<whitequark[cis]> (no)
<cr1901> (I like converse/obverse myself)
<whitequark[cis]> I want to go with just "flipped"
<cr1901> Yea, there's a tab, go to inverse. There's no way to link it directly
<whitequark[cis]> at this poiny
<whitequark[cis]> * at this point
<zyp[m]> sounds reasonable to me
<cr1901> Fine w/ me
<_whitenotifier> [YoWASP/nextpnr] whitequark pushed 1 commit to develop [+0/-0/±2] https://github.com/YoWASP/nextpnr/compare/ec507ffa95a0...e9af21a9cafd
<_whitenotifier> [YoWASP/nextpnr] whitequark e9af21a - Update dependencies.
<_whitenotifier> [rfcs] whitequark opened pull request #20: Add an RFC for deprecating non-FWFT FIFOs - https://github.com/amaranth-lang/rfcs/pull/20
<_whitenotifier> [rfcs] whitequark edited pull request #20: Add an RFC for deprecating non-FWFT FIFOs - https://github.com/amaranth-lang/rfcs/pull/20
<_whitenotifier> [amaranth] whitequark commented on issue #752: Deprecate and remove non-FWFT FIFOs - https://github.com/amaranth-lang/amaranth/issues/752#issuecomment-1684624731
Degi_ has joined #amaranth-lang
Degi has quit [Ping timeout: 256 seconds]
Degi_ is now known as Degi
<crzwdjk> Re RFC 20, what are non-FWFT FIFOs useful for? Or how do the use cases of FWFT vs non-FWFT FIFOs differ?
<whitequark[cis]> they aren't, that's why I'm removing them without a replacement
<crzwdjk> Ah okay. That's nice and simple then.
<_whitenotifier> [amaranth-lang/rfcs] whitequark pushed 2 commits to interfaces [+0/-0/±2] https://github.com/amaranth-lang/rfcs/compare/c53abf78f7ca...379d41946241
<_whitenotifier> [amaranth-lang/rfcs] whitequark c52952f - describe `.array` as composable
<_whitenotifier> [amaranth-lang/rfcs] whitequark 379d419 - go back to `flipped()` from `transpose()`
<_whitenotifier> [rfcs] whitequark opened pull request #21: Add an RFC defining policy for issuing patch releases - https://github.com/amaranth-lang/rfcs/pull/21
<_whitenotifier> [rfcs] whitequark edited pull request #21: Add an RFC defining policy for issuing patch releases - https://github.com/amaranth-lang/rfcs/pull/21
skipwich has quit [Quit: DISCONNECT]
skipwich has joined #amaranth-lang
<_whitenotifier> [rfcs] whitequark opened pull request #22: Add an RFC introducing `ValueCastable.shape()` - https://github.com/amaranth-lang/rfcs/pull/22
<_whitenotifier> [amaranth] whitequark commented on issue #794: RFC 15 breaks expectations of uses of `Signal.like` - https://github.com/amaranth-lang/amaranth/issues/794#issuecomment-1684733613
<_whitenotifier> [rfcs] whitequark commented on pull request #22: Add an RFC introducing `ValueCastable.shape()` - https://github.com/amaranth-lang/rfcs/pull/22#issuecomment-1684733767
<cr1901> I _was_ going to say I use non-FWFT/read enable in some code I'm converting to Amaranth, BUT... I've grepped the whole git history, looks like past-me decided to not to in the end. So no problem then :D
<cr1901> Thought it was on an abandoned-bc-this-code-is-trash-and-you-should-feel-bad branch
<crzwdjk> Oh wow, ice40 UP really is very slow, even compared to LP. Like, 2x slower or something as I am porting my design to it.
<crzwdjk> The max frequency nextpnr is giving is getting dangerously close to the minimum frequency I can drive the display panel at
<whitequark[cis]> yep
nyanotech has quit [Remote host closed the connection]
nyanotech has joined #amaranth-lang
key2 has joined #amaranth-lang
<key2> ah
<key2> interesting
<key2> but lattice FPGA do not handle 12G
<key2> I wonder how they do on their new 12G 4K then ;)
<key2> oops wrong window :)
GenTooMan has quit [Ping timeout: 248 seconds]
GenTooMan has joined #amaranth-lang
Wolfvak is now known as wolfvak
wolfvak is now known as Wolfvak
GenTooMan has quit [Ping timeout: 248 seconds]
GenTooMan has joined #amaranth-lang
GenTooMan has quit [Ping timeout: 246 seconds]
GenTooMan has joined #amaranth-lang
Wanda[cis] has quit [Quit: Idle timeout reached: 172800s]
GenTooMan has quit [Ping timeout: 256 seconds]
GenTooMan has joined #amaranth-lang
adamgreig[m] has quit [Quit: Idle timeout reached: 172800s]
mcc111[m] has quit [Quit: Idle timeout reached: 172800s]
GenTooMan has quit [Ping timeout: 256 seconds]
chuckmcm[m] has joined #amaranth-lang
<chuckmcm[m]> I have a suggestion for Amaranth (amaranth?) that I'm developing and I wondered what the procedure is for suggesting, do I just submit a PR to the rfcs repository? Or is there a gateway process?
<chuckmcm[m]> (and yes I think the change is "substantial" as it affects the `Platform` base class
<chuckmcm[m]> And more reading I'm now looking at the process in detail and will follow the process outlined in the docs for the RFC repo
Wanda[cis] has joined #amaranth-lang
<Wanda[cis]> generally you'd start with a quick discussion of the idea here
<Wanda[cis]> to get a general impression of what people think about the idea and what paths there are to take
<whitequark[cis]> yep, always a good idea. there is nothing that stops you from just submitting an RFC and it will be given fair consideration (though do note that I prioritize areas of work and it may be a while until we get to it)
<whitequark[cis]> however if you discuss it beforehand it will be more effective
GenTooMan has joined #amaranth-lang