07:57 <_florent_> Regarding Migen/Amaranth, the current short term idea is just to allow building with Migen or Amaranth (compat), this way we don’t take any risks and can evaluate things further with Amaranth.

08:27 <_florent_> Sorry i’m off this week but could elaborate more next week.

08:28 <whitequark[cis]> pun intended? :)

08:54 <_florent_> Not really but also thought about it when writing :)

11:54 <MoeIcenowy> btw is there any historian to tell me what's the relationship between LiteX and MiSoC

11:58 <whitequark[cis]> MiSoC pretty much exists to suit the needs of M-Labs and QUARTIQ with community contributions nonexistent and not particularly encouraged. you can see this if you scroll through the commits for the last few years

11:59 <whitequark[cis]> also, lol https://github.com/m-labs/misoc/commit/4cd0c75b360fd4942c9dc29a23563b64f0668b1b

13:34 <MoeIcenowy> okay I am sorry to here that.

13:35 <MoeIcenowy> _florent_: BTW per GW2DDRPHY, I think maybe it's now needed to implement write leveling, and it looks like what WSTEP of DQS primitives designed to be used for

20:10 <_florent_> @MoeIcenowy: I contributed to MiSoC initially (2013-2015 IIRC) and also did some consulting for M-Labs but had dissagrements and communication issues, so went a different way with LiteX, without much ambition, just being able to build the projects I want with it and have pleasant collaboration with other developers.

20:14 <_florent_> gurki: This also probably answer your question, when improvement are required to Migen, I try to integrate them directly on LiteX.

20:20 <_florent_> But more generally, their is so much to do in open hardware, so if we can find ways for LiteX/Amaranth communities to reuse code from each others or collaborate, the better.