01:03 <_whitenotifier-9> [YoWASP/yosys] whitequark pushed 1 commit to develop-0.27 [+0/-0/±1] https://github.com/YoWASP/yosys/commit/24cc8f54e55c

01:03 <_whitenotifier-9> [YoWASP/yosys] whitequark 24cc8f5 - [autorelease] Yosys 0.27.

01:03 <_whitenotifier-9> [yosys] whitequark created branch develop-0.27 - https://github.com/YoWASP/yosys

01:03 <_whitenotifier-9> [YoWASP/yosys] whitequark pushed 1 commit to develop [+0/-0/±1] https://github.com/YoWASP/yosys/compare/456bb97deb2d...4e77be9876f4

01:03 <_whitenotifier-9> [YoWASP/yosys] whitequark 4e77be9 - Update dependencies.

01:27 <_whitenotifier-9> [amaranth-boards] Godtec opened pull request #218: LimeSDR-mini-v2 board definition file, No RF chip or USB at the moment. - https://github.com/amaranth-lang/amaranth-boards/pull/218

01:33 <d1b2> <VA3TEC-Mikek-14362> Made Pull Request! First one! 🙂 Board programmed and working, still working on RF chip and USB. if that ok. Not sure if need extra code in main amaranth for the RF LMS7002 chip or not. Let me know what else you need! Thanks! Mike K (VA3TEC) aka Godtec.

01:42 <_whitenotifier-9> [YoWASP/nextpnr] whitequark pushed 1 commit to develop [+0/-0/±1] https://github.com/YoWASP/nextpnr/compare/58b36345a7bc...4d51aad0f7ae

01:42 <_whitenotifier-9> [YoWASP/nextpnr] whitequark 4d51aad - Update dependencies.

01:45 <_whitenotifier-9> [YoWASP/yosys] whitequark created branch release-0.27 https://github.com/YoWASP/yosys/commit/24cc8f54e55c4d1daab417e51a8611b1397edb77

01:45 <_whitenotifier-9> [yosys] whitequark created branch release-0.27 - https://github.com/YoWASP/yosys

05:06 <_whitenotifier-9> [amaranth] whitequark commented on pull request #759: add Lattice Nexus vendor platform (using nextpnr-nexus and prjoxide) - https://github.com/amaranth-lang/amaranth/pull/759#issuecomment-1457541723

05:09 <_whitenotifier-9> [amaranth-boards] whitequark closed pull request #185: Add support for cmod_a7 and cmod_s7 board. - https://github.com/amaranth-lang/amaranth-boards/pull/185

05:09 <_whitenotifier-9> [amaranth-lang/amaranth-boards] whitequark pushed 1 commit to main [+2/-0/±0] https://github.com/amaranth-lang/amaranth-boards/compare/a1da1f52831d...ce26e35b5c07

05:09 <_whitenotifier-9> [amaranth-lang/amaranth-boards] bl0x ce26e35 - Add support for cmod_a7 and cmod_s7 boards.

05:09 <_whitenotifier-9> [amaranth-boards] whitequark commented on pull request #185: Add support for cmod_a7 and cmod_s7 board. - https://github.com/amaranth-lang/amaranth-boards/pull/185#issuecomment-1457544739

05:10 <_whitenotifier-9> [amaranth-boards] whitequark commented on pull request #218: LimeSDR-mini-v2 board definition file, No RF chip or USB at the moment. - https://github.com/amaranth-lang/amaranth-boards/pull/218#issuecomment-1457545962

08:24 <d1b2> <Olivier Galibert> Suddently (not sure what changed) getting a weirdness with add_settings

08:24 <d1b2> <Olivier Galibert> Error (125048): Error reading Quartus Prime Settings File /home/galibert/air/air/fpga/build/top.qsf, line 104 File: /home/galibert/air/air/fpga/build/top.qsf Line: 104 Info (125063): s e t _ g l o b a l _ a s s i g n m e n t - n a m e O N _ C H I P _ B I T S T R E A M _ D E C O M P R E S S I O N O F F File: /home/galibert/air/air/fpga/build/top.qsf Line: 104

08:24 <d1b2> <Olivier Galibert> def toolchain_prepare(self, fragment, name, **kwargs): overrides = { "add_settings": '''set_global_assignment -name ON_CHIP_BITSTREAM_DECOMPRESSION OFF''' } return super().toolchain_prepare(fragment, name, **overrides, **kwargs)

08:25 <d1b2> <Olivier Galibert> Followed the syntax from amaranth_boards/rz_easyfpga_a2_2.py

08:25 <d1b2> <Olivier Galibert> was working for a long while

09:16 <d1b2> <Olivier Galibert> and... it's not doing it anymore

09:16 <d1b2> <Olivier Galibert> go figure

09:33 <_whitenotifier-9> [amaranth-boards] bl0x commented on pull request #185: Add support for cmod_a7 and cmod_s7 board. - https://github.com/amaranth-lang/amaranth-boards/pull/185#issuecomment-1457843070

09:56 <Sarayan> Ok, how do I create a resource (adv7513) where the attrs differ on some pins (io_standard, specifically)?

09:56 <Sarayan> I'd like all the pins to stay together, even if they io_standard is different

09:56 <Sarayan> their

11:55 <_whitenotifier-9> [amaranth-boards] Godtec commented on pull request #218: LimeSDR-mini-v2 board definition file, No RF chip or USB at the moment. - https://github.com/amaranth-lang/amaranth-boards/pull/218#issuecomment-1458036415

12:16 <Sarayan> ok, Subsignal can take an Attrs inside it, very nice

13:31 <_whitenotifier-9> [amaranth] galibert opened issue #762: Suggestion: DomainRenamer taking ClockDomains - https://github.com/amaranth-lang/amaranth/issues/762

13:41 <_whitenotifier-9> [amaranth] whitequark commented on issue #762: Suggestion: DomainRenamer taking ClockDomains - https://github.com/amaranth-lang/amaranth/issues/762#issuecomment-1458193915

14:03 <_whitenotifier-9> [amaranth] galibert commented on issue #762: Suggestion: DomainRenamer taking ClockDomains - https://github.com/amaranth-lang/amaranth/issues/762#issuecomment-1458229585

14:04 <_whitenotifier-9> [amaranth] whitequark commented on issue #762: Suggestion: DomainRenamer taking ClockDomains - https://github.com/amaranth-lang/amaranth/issues/762#issuecomment-1458231419

14:07 <_whitenotifier-9> [amaranth] galibert commented on issue #762: Suggestion: DomainRenamer taking ClockDomains - https://github.com/amaranth-lang/amaranth/issues/762#issuecomment-1458236548

17:59 <d1b2> <Olivier Galibert> sigh, quartus takes centuries to generate ram

20:03 <whitequark> essentially, ShapeCastable becomes an AmaranthType in that case

20:03 <whitequark> but it would actually be much easier to teach people that they just pass the shape to Signal, and they get a value with that shape, as normal

20:03 <whitequark> Sarayan: you probably had a stray * somewhere

20:03 <whitequark> re: resource, you have to manually splat the resource defined in amaranth_boards.resources at the moment

20:03 <whitequark> test

20:03 <whitequark> but you can say Pins(..., attrs={}) iirc

20:07 <d1b2> <Olivier Galibert> Resource("adv7513", 0, Subsignal("tx_d_r", Pins("AD25 AC25 AB25 AA24 AB26 R26 R24 P21", dir="o"), Attrs(io_standard="3.3-V LVTTL")), Subsignal("tx_d_g", Pins("P26 N25 P23 P22 R25 R23 T26 T24", dir="o"), Attrs(io_standard="3.3-V LVTTL")), Subsignal("tx_d_b", Pins("T23 U24 V25 V24 W26 W25 AA26 V23", dir="o"), Attrs(io_standard="3.3-V LVTTL")),

20:07 <d1b2> Subsignal("tx_clk", Pins("Y25", dir="o"), Attrs(io_standard="3.3-V LVTTL")), Subsignal("tx_de", Pins("Y26", dir="o"), Attrs(io_standard="3.3-V LVTTL")), Subsignal("tx_hs", Pins("U26", dir="o"), Attrs(io_standard="3.3-V LVTTL")), Subsignal("tx_vs", Pins("U25", dir="o"), Attrs(io_standard="3.3-V LVTTL")), Subsignal("tx_int", Pins("T12", dir="i"), Attrs(io_standard="1.2 V")), Subsignal("scl",

20:07 <d1b2> Pins("B7", dir="io"), Attrs(io_standard="2.5 V")), Subsignal("sda", Pins("G11", dir="io"), Attrs(io_standard="2.5 V")) )

20:07 <d1b2> <Olivier Galibert> that works 100%

20:08 <d1b2> <Olivier Galibert> and given pins that logically work together tend to have the same io standard, I thing we're ok

22:06 <_whitenotifier-9> [amaranth] cyber-murmel opened issue #763: Add `processes` variable to `main_runner` - https://github.com/amaranth-lang/amaranth/issues/763

22:27 <_whitenotifier-9> [amaranth-boards] Godtec synchronize pull request #218: LimeSDR-mini-v2 board definition file, No RF chip or USB at the moment. - https://github.com/amaranth-lang/amaranth-boards/pull/218

22:47 <d1b2> <OmniTechnoMancer> That looks worryingly like a utf16 encoding trouble

23:01 <josuah> great syntax for ports! very concise and intuitive https://github.com/amaranth-lang/amaranth-boards/blob/main/amaranth_boards/ice40_up5k_b_evn.py#L48-L49

23:33 <_whitenotifier-9> [amaranth] whitequark commented on issue #763: Add `processes` variable to `main_runner` - https://github.com/amaranth-lang/amaranth/issues/763#issuecomment-1459028299