https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1862767#M223524 <P>Hello&nbsp;<a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206761">@Chavira</a>&nbsp;</P><P>Thank you for your prompt response.&nbsp;</P><P>For my prototype I'm using&nbsp;<A href="https://github.com/nxp-imx/linux-imx/blob/lf-6.1.y/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts#L386" target="_blank">https://github.com/nxp-imx/linux-imx/blob/lf-6.1.y/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts#L386</A>&nbsp;device tree.&nbsp;</P><P>How can I modify the above dts?</P><P>Cheers,&nbsp;<BR />Nitesh</P> Thu, 09 May 2024 19:13:14 GMT pilotnite 2024-05-09T19:13:14Z https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1862714#M223521 <P>Hello,</P><P>I believe this issue can be easily resolved from userspace. Currently, when booting up the iMX93 EVK using "NXP i.MX Release Distro 6.1-mickledore imx93evk," the left Ethernet port is labeled (ENET2) and the right Ethernet port is labeled (ENET1) on the board. However, upon booting into Linux, eth0 is assigned to ENET2 and eth1 to ENET1.</P><P class=""><SPAN class="">[275870.178004] fec 42890000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off<BR /></SPAN><SPAN class="">[275870.185699] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready</SPAN></P><P class=""><SPAN class="">[275895.075584] imx-dwmac 428a0000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off<BR /></SPAN><SPAN class="">[275895.083801] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready<BR /><BR /><SPAN>What would be the best approach to ensure that upon Linux boot, ENET1 is eth0 and ENET2 is eth1? Should we consider changing the order in which drivers load, renaming the interface using systemd, or implementing a simple bash script?</SPAN></SPAN></P><P class="">Any help will be highly appreciated.&nbsp;</P><P class="">Cheers,<BR />Nitesh</P><P class="">&nbsp;</P> Thu, 09 May 2024 17:26:38 GMT https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1862714#M223521 pilotnite 2024-05-09T17:26:38Z https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1862761#M223523 <P><SPAN data-preserver-spaces="true">Hi <a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/233332">@pilotnite</a>!</SPAN></P> <P><SPAN data-preserver-spaces="true">Thank you for contacting NXP Support!</SPAN></P> <P><SPAN data-preserver-spaces="true">&nbsp;</SPAN></P> <P><SPAN data-preserver-spaces="true">I think that can be solved in the device tree.</SPAN></P> <P><SPAN data-preserver-spaces="true">&nbsp;</SPAN></P> <P><SPAN data-preserver-spaces="true">By default is defined in the following way:</SPAN></P> <P><SPAN data-preserver-spaces="true">&nbsp;</SPAN></P> <P><SPAN data-preserver-spaces="true">ethernet0 = &amp;fec;</SPAN></P> <P><SPAN data-preserver-spaces="true">ethernet1 = &amp;eqos;</SPAN></P> <P><SPAN data-preserver-spaces="true">&nbsp;</SPAN></P> <P><SPAN data-preserver-spaces="true">You have to change that with:</SPAN></P> <P><SPAN data-preserver-spaces="true">&nbsp;</SPAN></P> <P><SPAN data-preserver-spaces="true">ethernet0 = &amp;eqos;</SPAN></P> <P><SPAN data-preserver-spaces="true">ethernet1 = &amp;fec;</SPAN></P> <P><SPAN data-preserver-spaces="true">&nbsp;</SPAN></P> <P><SPAN data-preserver-spaces="true">Please try it and share your results.</SPAN></P> <P><SPAN data-preserver-spaces="true">&nbsp;</SPAN></P> <P><A class="editor-rtfLink" href="https://github.com/nxp-imx/linux-imx/blob/lf-6.1.y/arch/arm64/boot/dts/freescale/imx93.dtsi#L33" target="_blank" rel="noopener"><SPAN data-preserver-spaces="true">https://github.com/nxp-imx/linux-imx/blob/lf-6.1.y/arch/arm64/boot/dts/freescale/imx93.dtsi#L33</SPAN></A></P> <P><SPAN data-preserver-spaces="true">&nbsp;</SPAN></P> <P><SPAN data-preserver-spaces="true">Best Regards!</SPAN></P> <P><SPAN data-preserver-spaces="true">Chavira</SPAN></P> Thu, 09 May 2024 18:59:45 GMT https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1862761#M223523 Chavira 2024-05-09T18:59:45Z https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1862767#M223524 <P>Hello&nbsp;<a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206761">@Chavira</a>&nbsp;</P><P>Thank you for your prompt response.&nbsp;</P><P>For my prototype I'm using&nbsp;<A href="https://github.com/nxp-imx/linux-imx/blob/lf-6.1.y/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts#L386" target="_blank">https://github.com/nxp-imx/linux-imx/blob/lf-6.1.y/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts#L386</A>&nbsp;device tree.&nbsp;</P><P>How can I modify the above dts?</P><P>Cheers,&nbsp;<BR />Nitesh</P> Thu, 09 May 2024 19:13:14 GMT https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1862767#M223524 pilotnite 2024-05-09T19:13:14Z https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1862781#M223525 <P><a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206761">@Chavira</a>&nbsp;</P><P>Never mind... I see what you mean and I just noticed device tree "imx93-11x11-evk.dts" includes "#include "imx93.dtsi"".&nbsp;</P><P>Let me edit "imx93.dtsi" and test.&nbsp;</P><P>Cheers,&nbsp;<BR />Nitesh</P> Thu, 09 May 2024 19:27:29 GMT https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1862781#M223525 pilotnite 2024-05-09T19:27:29Z https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1863452#M223558 Much appreciated for the solution. Fri, 10 May 2024 11:48:28 GMT https://community.nxp.com/t5/i-MX-Processors/iMX93-Network-Interface/m-p/1863452#M223558 pilotnite 2024-05-10T11:48:28Z