From owner-freebsd-arm@freebsd.org Wed Oct 3 18:42:18 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EBC110AA178 for ; Wed, 3 Oct 2018 18:42:18 +0000 (UTC) (envelope-from pygr@sonic.net) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0A9D38AAF3 for ; Wed, 3 Oct 2018 18:42:17 +0000 (UTC) (envelope-from pygr@sonic.net) Received: from [10.137.113.129] (108-169-4-40.dynamic.dsl.sonic.net [108.169.4.40] (may be forged)) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id w93Ig8Oi004820 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 3 Oct 2018 11:42:09 -0700 From: glenn Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 Date: Wed, 3 Oct 2018 11:42:08 -0700 References: To: freebsd-arm@freebsd.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.9.1) X-Sonic-CAuth: UmFuZG9tSVY/HvnM3/1TlAAT/cbaZENej1gbI7n1bwJIIEzUXQHX/OITTOWt07HXBG+KXKPsjxqcY+vvDcoxuCKqNSIf5zXb X-Sonic-ID: C;QPtzCDzH6BGIyoLirVfHYg== M;iCW2CDzH6BGIyoLirVfHYg== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 18:42:18 -0000 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 = progress. 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://forum.solid-run.com/linux-kernel-and-bootloaders-f34/port-light-is-= always-on-does-not-work-t3074.html = .=20 It was a surprise to me that modifying u-boot code affected the = functioning of the ethernet after control was passed to the OS. = Apparently some functionality that is built into u-boot continues to be = used by the OS. In addition to the changes in u-boot mentioned above, the = armada-388-clearfog-base.dts was edited to allow the serial console to = function. The second line in serial@12000 { compatible =3D "marvell,armada-38x-uart=E2=80=9D; was changed to=20 compatible =3D "snps,dw-apb-uart=E2=80=9D;=20 I=E2=80=99m thinking the reason that that enabled the serial console is = that 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. Glenn > Date: Tue, 2 Oct 2018 11:57:32 -0300 > From: Luiz Otavio O Souza > To: Marcin Wojtas > Cc: pygr@sonic.net, "freebsd-arm@freebsd.org" > > Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 > Message-ID: > = > Content-Type: text/plain; charset=3D"UTF-8" >=20 > On Tue, 2 Oct 2018 at 00:43, Marcin Wojtas wrote: >>=20 >> Hi Glenn, >>=20 >> I can see, that armada-388-clearfog-base.dts connects eth1 to a PHY = via MDIO. >> Unfortunately my Clearfog boards have the SFP cage connected only to >> the SGMII lanes only (no PHY). >>=20 >> Can you please try to boot with armada-388-clearfog.dts, where the = SFP >> cage is configured as the 'fixed-link' and let know? >=20 > 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. >=20 > Luiz >=20