Date: Wed, 3 Oct 2018 21:09:12 +0200 From: Marcin Wojtas <mw@semihalf.com> To: pygr@sonic.net Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 Message-ID: <CAPv3WKfrC6LTheAquXhQgGVh=CpY5pnda9vTVA6bAhE_c-H2Uw@mail.gmail.com> In-Reply-To: <AE738977-F1C8-4F8A-9E42-FD4CFD9317E8@sonic.net> References: <mailman.57.1538568001.62956.freebsd-arm@freebsd.org> <AE738977-F1C8-4F8A-9E42-FD4CFD9317E8@sonic.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Glenn , =C5=9Br., 3 pa=C5=BA 2018 o 20:42 glenn <pygr@sonic.net> napisa=C5=82(a): > > Hi Luiz and Marcin, > > Thank you for taking an interest in this. > > I have looked into the problem further (Google is your friend) and made p= rogress. After modification of the u-boot source before build, the message = =E2=80=9Cstatus: no carrier=E2=80=9D for the second ethernet port no longer= appears . The recipe is detailed in the last post in this thread: http://f= orum.solid-run.com/linux-kernel-and-bootloaders-f34/port-light-is-always-on= -does-not-work-t3074.html <http://forum.solid-run.com/linux-kernel-and-boot= loaders-f34/port-light-is-always-on-does-not-work-t3074.html>. > > It was a surprise to me that modifying u-boot code affected the functioni= ng of the ethernet after control was passed to the OS. Apparently some func= tionality that is built into u-boot continues to be used by the OS. > Good catch. Yes, PHY initialization is supposed to be done in the bootloader, later the generic ukphy is used for handling the media status/update (no dedicated driver). > In addition to the changes in u-boot mentioned above, the armada-388-clea= rfog-base.dts was edited to allow the serial console to function. The secon= d line in > > serial@12000 { > compatible =3D "marvell,armada-38x-uart=E2=80=9D; > > was changed to > > compatible =3D "snps,dw-apb-uart=E2=80=9D; > > I=E2=80=99m thinking the reason that that enabled the serial console is t= hat FreeBSD doesn=E2=80=99t have a driver that responds to "marvell,armada-= 38x-uart=E2=80=9D but does have one that responds to "snps,dw-apb-uart=E2= =80=9D. I see it's a fairly fresh change in the mainline Linux, I hope I will manage to squeeze it to 12. Thanks, Marcin > > Glenn > > > Date: Tue, 2 Oct 2018 11:57:32 -0300 > > From: Luiz Otavio O Souza <lists.br@gmail.com> > > To: Marcin Wojtas <mw@semihalf.com> > > Cc: pygr@sonic.net, "freebsd-arm@freebsd.org" > > <freebsd-arm@freebsd.org> > > Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 > > Message-ID: > > <CAB=3D2f8z0GumRUQB7gbV4wLLVuk6BRf3pu6JSAP3sOhpoXdstsw@mail.gmail= .com> > > Content-Type: text/plain; charset=3D"UTF-8" > > > > On Tue, 2 Oct 2018 at 00:43, Marcin Wojtas wrote: > >> > >> Hi Glenn, > >> > >> I can see, that armada-388-clearfog-base.dts connects eth1 to a PHY vi= a MDIO. > >> Unfortunately my Clearfog boards have the SFP cage connected only to > >> the SGMII lanes only (no PHY). > >> > >> Can you please try to boot with armada-388-clearfog.dts, where the SFP > >> cage is configured as the 'fixed-link' and let know? > > > > I don't have the Clearfog Base here, but this board has the PHY1 reset > > connected to GPIO pin 19, you probably want to check this too. > > > > Luiz > > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPv3WKfrC6LTheAquXhQgGVh=CpY5pnda9vTVA6bAhE_c-H2Uw>