01:43 <_whitenotifier> [YoWASP/yosys] whitequark pushed 1 commit to develop [+0/-0/±1] https://github.com/YoWASP/yosys/compare/2611a78f85b4...8a0d2e9416da

01:43 <_whitenotifier> [YoWASP/yosys] whitequark 8a0d2e9 - Update dependencies.

03:56 <d1b2> <j4cbo> how can i instantiate an SB_RGB_DRV? this primitive needs to be connected directly to the I/O pins without an SB_IO, and i'm not sure how to prevent the SB_IO from being generated

03:57 <tpw_rules> have you seen https://lab.ktemkin.com/post/nmigen-instance/ ?

03:59 <d1b2> <j4cbo> i saw a discussion in #fpga from early 2020 that said "pass dir='-' to plat.getresource" but that doesn't seem to be allowed anymore (i get "Direction must be one of "i", "o", "oe", or "io", not '-'")

03:59 <d1b2> <j4cbo> yeah, that's basically what i'm doing, and amaranth is happy but it produces Verilog that nextpnr can't deal with (because there's an SB_IO in the way)

04:00 <tpw_rules> oh, i don't think i understood the question correctly then

04:02 <d1b2> <j4cbo> SB_RGB_DRV is an ice40 primitive for some special constant-current pins; those pins can be associated with either the SB_RGB_DRV or an SB_IO, but not both

04:03 <tpw_rules> so you don't want the resource machinery to automatically create an SB_IO

04:04 <d1b2> <j4cbo> exactly

04:04 <d1b2> <j4cbo> when i just use Instance("SB_RGB_DRV", ...) to instantiate it, Amaranth winds up connecting the output of the SB_RGB_DRV to the SB_IO's D_OUT_0, which can't be placed

04:06 <tpw_rules> not sure how to do that then, sorry

04:12 <whitequark> could you show the code you are using?

04:16 <d1b2> <j4cbo> https://gist.github.com/j4cbo/c6902e385de835b85abc3329c9fa4365

07:31 <gatecat> j4cbo: try something like `dir=dict(r='-', g='-', b='-')` to the platform.request

15:50 <d1b2> <j4cbo> ah, that did it, thanks!