Date: Sat, 7 Dec 2019 22:29:00 -0700 From: Rebecca Cran <rebecca@bsdio.com> To: Marcel Flores <marcel@brickporch.com>, freebsd-arm@freebsd.org Subject: Re: ThunderX Networking Message-ID: <883e0aae-5685-dad0-b75b-eadfbab6e6ae@bsdio.com> In-Reply-To: <FE344936-D6F2-4182-AEF6-D2D795333627@brickporch.com> References: <340B43A0-8E12-4F8C-A7F0-844BF8A55DB8@brickporch.com> <FE344936-D6F2-4182-AEF6-D2D795333627@brickporch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/7/19 4:41 PM, Marcel Flores wrote: > Took another look at the this. It seems the issue arose in this commit: > https://reviews.freebsd.org/rS334880 > > Manually removing the additional check and building a kernel allowed it to > match the PHY device. > > Following the steps outlined here: > > https://lists.freebsd.org/pipermail/freebsd-arm/2015-November/012612.html > > and was able to get the onboard NIC working. > > > This feels very much like a bug in the check logic of rS334880 to me, but > I admit I'm out of my depth on what exactly it's checking for. Interesting - thanks! I'd stopped using my ThunderX machine because of the frustration of not having the technical SoC documentation from Cavium I thought I needed to fix issues like this. -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?883e0aae-5685-dad0-b75b-eadfbab6e6ae>