00:31 <_whitenotifier> [YoWASP/nextpnr] whitequark pushed 1 commit to develop [+0/-0/±1] https://github.com/YoWASP/nextpnr/compare/c874d235178d...ea0dab4a2ef3

00:31 <_whitenotifier> [YoWASP/nextpnr] whitequark ea0dab4 - Update dependencies.

01:22 <_whitenotifier> [YoWASP/yosys] whitequark pushed 1 commit to develop [+0/-0/±2] https://github.com/YoWASP/yosys/compare/5d070dd75650...8b071136c21f

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

03:00 <mithro> Does the idea of amaranth (and/or cxxrtl) support in https://github.com/Kuree/hgdb // https://hgdb.dev/ make sense?

03:04 <whitequark> interesting

03:04 <whitequark> I'll take a look at this; it seems more relevant to cxxrtl

03:07 <mithro> I found it via looking at the author of https://github.com/Kuree/fsim (who was posting about wanting a SystemVerilog simulation test suite on https://github.com/chipsalliance/sv-tests/issues/2522)

15:31 <shaiku> What is the proper way to install amaranth-boards? I can install it from pip but when I try any of the examples I always get "ModuleNotFoundError: No module named 'amaranth_boards'"

15:33 <vup> how did you install it with pip?

15:33 <vup> the pypi one is just a placeholder currently

15:35 <vup> I think something like `pip install git+https://github.com/amaranth-lang/amaranth-boards.git` should work

15:38 <whitequark> yeah

15:38 <shaiku> I initially did pip install amaranth-boards. Just did pip install git+https://github.com/amaranth-lang/amaranth-boards.git#egg=amaranth-boards and that worked :)

15:38 <shaiku> Can somebody put that at the bottom of this page real quick? https://amaranth-lang.org/docs/amaranth/latest/install.html

15:39 <whitequark> it's not really how it should be happening

15:40 <shaiku> That plus the "editable snapshot" instructions would finish out the install section.

15:40 <whitequark> and the steps are already explained for Amaranth itself

15:42 <shaiku> I'm sure that it's common-sense to you but there is no documentation whatsoever and I just expected pip install nmigen-boards to work (been failing at this since before the amaranth rename)

15:42 <whitequark> I'd much rather make that actually work than document the workaround

15:46 <shaiku> 30 seconds to document something that actually works or more months? years? of a blank TODO frustrating n00bs such as myself. Isn't it the case that all three methods of installation are valid but only one of them is not working at the moment? Why not document this.

15:49 <whitequark> because I'd rather get pinged every time someone hits this, honestly

15:50 <whitequark> (also, two out of three work for amaranth-boards, not one; you almost certainly want the editable snapshot and not the git+https:// installation)

15:56 <shaiku> two out of the three work -- that is exactly what I said when I phrased it "only one of them is not working" Well have it your way then :) I was just trying to help improve the project in a small way. Thanks for the help! Glad to finally get the boards installed properly.

15:58 <whitequark> oh, sorry, I misread

15:59 <whitequark> so there's no fundamental problem with making an amaranth-boards release, it's just not clear what the versioning scheme is supposed to be like

15:59 <whitequark> if you'd like, you can kick off that discussion by opening an issue on amaranth-boards

16:04 <vup> (or probably comment on the RFC: https://github.com/amaranth-lang/amaranth-boards/issues/128 )

16:04 <whitequark> oh, right, there's one

16:05 <vup> heh

18:33 <Degi> Hmm, is "Make sure that every board uses only non-overlapping pins in resources." compatible with like having single ended vs differential PMOD for example? Since that requires different resource instantiation

18:35 <d1b2> <dragonmux> yes, the rule it creates is that you can only request one of the two versions of the resource at a time or Amaranth will give you errors saying where you went wrong

18:35 <d1b2> <dragonmux> the non-overlapping property is only enforced at request time

20:09 <Degi> Ah I see