From owner-freebsd-arm@freebsd.org Wed Oct 3 19:09:23 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 44CEA10AAAB9 for ; Wed, 3 Oct 2018 19:09:23 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D89AE8B6DE for ; Wed, 3 Oct 2018 19:09:22 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-io1-xd2b.google.com with SMTP id w16-v6so5940236iom.7 for ; Wed, 03 Oct 2018 12:09:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=JX0bxDlTrSkgPdugWGkGEzNshlGKnv5P6fejC87X+e8=; b=GemXpjtA5Qo7wklg8F2xrClu9fIUI9Wo5t2N+irTXH6p06+RIB0ugG7aARDviz5/Q8 Bg0RbFv8N8S16z9Mcg1uBv3goMqAowZp/8w7oNvH0gb9bLHFmHDKMIiWCxhxb7sjR1y2 FT+b/jFQGWWei0szQGfkdn5mUJobSmlvheZ0nDrmueOLRwBj6zi5ccIELh6LrheZ71hd 4dhKMoyIRUvjqzKQu/mH5y02EnGsucXMvaVT/AC1OU+QCxu9VYftsWV9prc98kODmCxG 2SL0enFA+9u0XwGNNGiAZZhO0xdvXXIrBbVe5ig5SSp/PEQnq7JmfNSHklWyXts+b7mh Ltow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=JX0bxDlTrSkgPdugWGkGEzNshlGKnv5P6fejC87X+e8=; b=VDD4eNDAkmxf324Nc7ECTl5Ca8/Py/9ftcOIFEyx7UWG4Y0CU9aCJgwDpew99Dx4+3 3tZzd2gC0viNRAGqBssbfLtHVNprZ6E1/OWx/WUPtQiNlwnAIt9vLE1ynyqjZSi3S7Vp cYXWVDz2Ch3nBGOO9pXsUxpeJI8ClX/Xz57qcZcqkiwr/HU+nt3uxeW/Rc8bivturHBq bsDdHJkgONTVD9t77jm0+uHKlxp0CRyIWjQBiBaWio9FfKMuZscrmlwHAXUVIBmVaiX0 CuJXq6VyI5u473J8+6jrU/iDUOWFFpPqEP8358Q28USSxYlICmoh/+0PmP5qOGe/qUt8 65/A== X-Gm-Message-State: ABuFfoi3gF27y3nq9hoVUrf1KAooDjmY4LY+Cirbb/+UQQPgc2p6uDHv 6jqnnTd0qCkMDheWbDiGcfq/IjPv2Aj0dq8qS+OXpg== X-Google-Smtp-Source: ACcGV60IwbMa+13aavUg7ivsWZN/WkIh6surtOdpHwdkYkgTrauDxcmBEC4ixJPMVmHPrkZjFmc9V/Ri93BoaEvwYF4= X-Received: by 2002:a5e:c643:: with SMTP id s3-v6mr2163912ioo.108.1538593761996; Wed, 03 Oct 2018 12:09:21 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Marcin Wojtas Date: Wed, 3 Oct 2018 21:09:12 +0200 Message-ID: Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 To: pygr@sonic.net Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 19:09:23 -0000 Hi Glenn , =C5=9Br., 3 pa=C5=BA 2018 o 20:42 glenn 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 . > > 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 > > 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" > > > > 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"