<whitequark[cis]>
vup: yeah. we did actually recently *remove* that argument I think, but definitely an RFC is fine
<cr1901>
If I have a switch, and the ON position turns an LED off (direct connection), that means the switch is inverted/pull-up and I should add invert=True, correct?
<whitequark[cis]>
yes. or the LED is inverted
<cr1901>
No schematic is provided. When I push a button down (same gateware, 'cept with a button), the LED lights up
<cr1901>
Oh, lemme try led.eq(1)
<cr1901>
Ahh, the LEDs are definitely inverted.
<cr1901>
And for buttons, pressed should be a 1 input (and if it isn't, invert?)?
d_olex_ has quit [Read error: Connection reset by peer]
frgo_ has quit [Remote host closed the connection]
frgo has joined #amaranth-lang
Mimil has joined #amaranth-lang
Mimil has quit [Client Quit]
<vup>
whitequark / Wanda: ah yeah I just saw it got removed in the implementation of RFC 50, I guess because it was deemed superfluous with the support for messages?
<whitequark[cis]>
I think so
<Wanda[cis]>
mmm yeah there was something like it?