Factor out resource "eth_rgmii"

[nmigen-issue-migration]

Issue by whitequark Friday Jun 28, 2019 at 03:47 GMT Originally opened as https://github.com/m-labs/nmigen-boards/issues/10

---

Boards using it:

• [ ] Atlys
• [ ] ECPIX5
• [ ] Genesys2
• [ ] versa_ecp5, versa_ecp5_5g

[nmigen-issue-migration]

Comment by HarryHo90sHK Tuesday Jan 07, 2020 at 07:50 GMT

---

May I know what is meant by factoring out this Ethernet resource? Will ECP5 boards not be able to use RGMII?

On a side note, the rx_ctl and tx_ctl signals are named rx_ctrl and tx_ctrl respectively. Is this intentional or a bug? Thanks!

[nmigen-issue-migration]

Comment by whitequark Tuesday Jan 07, 2020 at 08:24 GMT

---

May I know what is meant by factoring out this Ethernet resource?

Do a change similar to this commit: https://github.com/m-labs/nmigen-boards/commit/07156e68dd003e21a4b36819de80a239e0ab910f

Will ECP5 boards not be able to use RGMII?

Of course they will, or the board definition file would be pretty useless.

On a side note, the rx_ctl and tx_ctl signals are named rx_ctrl and tx_ctrl respectively. Is this intentional or a bug?

That is a typo.

[TechnoMancer]

When doing this and #13 I believe the MDIO should also be factored out into a separate resource, the managment bus for the PHYs supports multiple PHYs on one bus and it is not uncommon for multiple PHYs to share the same MDIO bus, which if the MDIO is part of the RGMIIResource or SGMIIResource will prevent using more than one such PHY on a board.

Some discussion in this direction has happened in #149