00:21 <lonjil[m]> <bl0x[m]> "Can you open an issue in the..." <- Sorry for the delay, I opened two issues.

00:39 <lonjil[m]> Incidentally, I just got my first FPGA today, in the form of a Nandland Go board. Gotta figure out how to make good use of the BRAM so I stop wasting a thousand DFFs on registers 😄

00:41 <whitequark[cis]> https://amaranth-lang.org/docs/amaranth/latest/stdlib/memory.html

00:54 <lonjil[m]> yeah. I put a little test together with that. Though I got a result that I didn't understand, so tomorrow (late here) I will teach myself about the yosys tooling that I believe exists for looking at how different parts of the design end up actually being expressed.

08:52 <_whitenotifier-9> [amaranth-yosys] kivikakk commented on issue #11: Thoughts on including optimization passes? - https://github.com/amaranth-lang/amaranth-yosys/issues/11#issuecomment-2205457479

10:38 <_whitenotifier-9> [amaranth-yosys] whitequark commented on issue #11: Thoughts on including optimization passes? - https://github.com/amaranth-lang/amaranth-yosys/issues/11#issuecomment-2205756814

10:45 <_whitenotifier-9> [amaranth-yosys] kivikakk commented on issue #11: Thoughts on including optimization passes? - https://github.com/amaranth-lang/amaranth-yosys/issues/11#issuecomment-2205769134

10:47 <_whitenotifier-9> [amaranth-yosys] kivikakk opened pull request #12: Add "opt" passes. - https://github.com/amaranth-lang/amaranth-yosys/pull/12

10:57 <_whitenotifier-9> [amaranth-yosys] whitequark closed pull request #12: Add "opt" passes. - https://github.com/amaranth-lang/amaranth-yosys/pull/12

10:57 <_whitenotifier-9> [amaranth-yosys] whitequark closed issue #11: Thoughts on including optimization passes? - https://github.com/amaranth-lang/amaranth-yosys/issues/11

10:57 <_whitenotifier-9> [amaranth-yosys] whitequark commented on pull request #12: Add "opt" passes. - https://github.com/amaranth-lang/amaranth-yosys/pull/12#issuecomment-2205795793

13:43 <_whitenotifier-9> [amaranth-yosys] kivikakk commented on pull request #12: Add "opt" passes. - https://github.com/amaranth-lang/amaranth-yosys/pull/12#issuecomment-2206112104

14:33 <_whitenotifier-9> [amaranth-soc] jfng reviewed pull request #94 commit - https://github.com/amaranth-lang/amaranth-soc/pull/94#discussion_r1664298045

14:39 <_whitenotifier-9> [amaranth-soc] jfng reviewed pull request #94 commit - https://github.com/amaranth-lang/amaranth-soc/pull/94#discussion_r1664306507

14:49 <_whitenotifier-9> [amaranth-soc] whitequark reviewed pull request #94 commit - https://github.com/amaranth-lang/amaranth-soc/pull/94#discussion_r1664327455

14:50 <_whitenotifier-9> [amaranth-yosys] whitequark commented on pull request #12: Add "opt" passes. - https://github.com/amaranth-lang/amaranth-yosys/pull/12#issuecomment-2206389762

15:00 <_whitenotifier-9> [amaranth-soc] jfng reviewed pull request #94 commit - https://github.com/amaranth-lang/amaranth-soc/pull/94#discussion_r1664346187

15:50 <_whitenotifier-9> [amaranth-soc] github-merge-queue[bot] created branch gh-readonly-queue/main/pr-94-058057f38b18537585a02e1db7955a184a1c5334 - https://github.com/amaranth-lang/amaranth-soc

15:52 <_whitenotifier-9> [amaranth-lang/amaranth-soc] github-merge-queue[bot] pushed 1 commit to main [+2/-0/±0] https://github.com/amaranth-lang/amaranth-soc/compare/058057f38b18...d99c8ee582a2

15:52 <_whitenotifier-9> [amaranth-lang/amaranth-soc] jfng d99c8ee - wishbone: add Wishbone-attached SRAM.

15:52 <_whitenotifier-9> [amaranth-soc] github-merge-queue[bot] deleted branch gh-readonly-queue/main/pr-94-058057f38b18537585a02e1db7955a184a1c5334 - https://github.com/amaranth-lang/amaranth-soc

15:52 <_whitenotifier-9> [amaranth-soc] jfng closed pull request #94: wishbone: add Wishbone-attached SRAM. - https://github.com/amaranth-lang/amaranth-soc/pull/94

15:52 <_whitenotifier-9> [amaranth-soc] jfng closed issue #89: Wishbone-attached SRAM - https://github.com/amaranth-lang/amaranth-soc/issues/89

15:53 <_whitenotifier-9> [amaranth-lang/amaranth-lang.github.io] whitequark pushed 1 commit to main [+0/-0/±8] https://github.com/amaranth-lang/amaranth-lang.github.io/compare/78e1b9279082...351fd2ab6916

15:53 <_whitenotifier-9> [amaranth-lang/amaranth-lang.github.io] github-merge-queue[bot] 351fd2a - Deploying to main from @ amaranth-lang/amaranth-soc@d99c8ee582a2159ea9df38bfe666c08019f7f464 🚀

18:11 <zyp[m]> cr1901: so I'm playing a little bit with sentinel and I'm running into an issue where sentinel wanting amaranth from git and amaranth-soc wanting `amaranth>=0.5,<0.6` makes pdm sad -- how do you sort it when you work with it?

20:23 <cr1901_> zyp[m]: are you running "pdm update" immediately after checkout? sentinel should be using pdm.lock to avoid the most recently amaranth and deps

20:23 <cr1901_> also sentinel isn't amaranth 0.5 ready

20:24 <cr1901_> (Don't run pdm update. Failing that, let me see the exact terminal commands you ran since git checkout.)

20:24 <zyp[m]> I'm not running pdm in sentinel at all, I'm running pdm in my project with sentinel as a dependency

20:25 <cr1901_> Oh, that's not going to work. I should've moved that info to the README.md: https://github.com/cr1901/sentinel/blob/main/CHANGELOG.md#v010-alpha---2023-11-29

20:26 <zyp[m]> well, I ended up forcing amaranth 0.5 in tool.pdm.resolution.overrides -- so far it seems to work

20:26 <zyp[m]> what part of sentinel is not 0.5 ready?

20:26 <cr1901_> sims

20:27 <zyp[m]> in what sense?

20:27 <cr1901_> They're old-style "yield sig.eq(val) waits until the next clock tick to actually propagate the new value"

20:28 <cr1901_> strictly-speaking, if you ran amaranth 0.5 sim with sentinel, those tests will fail, but rv-formal and riscof will pass

20:29 <zyp[m]> ah, right, I'm less interested in running tests on sentinel and more interested in running code on sentinel :)

20:30 <cr1901_> It probably works fine w/ 0.5 for that purpose :).

20:30 <zyp[m]> I copied your WBMemory, wired it directly to a sentinel instance, stuck it in the sim and am poking it with my own testbench

20:31 <zyp[m]> https://paste.jvnv.net/view/V8EFh

20:32 <cr1901_> does it work :P?

20:33 <cr1901_> >tool.pdm.resolution.overrides I will probably end up putting that in the README.md then

20:33 <zyp[m]> so yes :)

20:33 <whitequark[cis]> i mean the tests still work on 0.5

20:34 <whitequark[cis]> it's deprecated but supported

20:34 <whitequark[cis]> heck, we haven't even removed them from main

20:34 <whitequark[cis]> the old style syntax

20:35 <cr1901_> >They're old-style "yield sig.eq(val) waits until the next clock tick to actually propagate the new value"

20:35 <cr1901_> those aren't supported, and haven't been since 36 was impl'd

20:36 <cr1901_> s/aren't supported/don't work/

20:36 <whitequark[cis]> ohh, I see

20:36 <whitequark[cis]> yeah

20:38 <cr1901_> smolarith might be a small package, but it's good as my "GNU hello world" for testing new amaranth features and syntax. The idea is I update that first to get a feel, and then update Sentinel

20:38 <cr1901_> but I've fallen a bit behind

20:38 <zyp[m]> are there any projects using sentinel yet?

20:39 <cr1901_> I have no idea, probably not. I know a few have checked it out tho

20:40 <cr1901_> It occupies a niche between serv and picorv32 (tho serv/sentinel implements M-mode, and picorv32 uses a custom interrupt scheme)

20:41 <zyp[m]> yeah, I'm thinking about using it to replace a serv I have in a project I'd like to port to be all-amaranth

20:43 <zyp[m]> so far it only does some initialization tasks like configuring a few ethernet PHY registers

20:43 <cr1901_> If you can tolerate like 700 extra LUTs usage, sentinel is perfectly fine for that and was my intended use case :)

20:44 <cr1901_> It's meant to "watch over your design and then get the hell out of the way".