Date: Sat, 7 Dec 2019 15:46:40 -0800 From: Marcel Flores <marcel@brickporch.com> To: freebsd-arm@freebsd.org Subject: Re: ThunderX Networking Message-ID: <2DB40DB6-73D0-440A-94B3-82A173E9DF3E@brickporch.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 Dec 7, 2019, at 3:41 PM, Marcel Flores <marcel@brickporch.com> = wrote: >=20 > Hi All, >=20 > Took another look at the this. It seems the issue arose in this = commit: >=20 > https://reviews.freebsd.org/rS334880 >=20 > Manually removing the additional check and building a kernel allowed = it to > match the PHY device. >=20 > Following the steps outlined here: >=20 > = https://lists.freebsd.org/pipermail/freebsd-arm/2015-November/012612.html >=20 > and was able to get the onboard NIC working. >=20 >=20 > 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. >=20 > -Marcel >=20 > _______________________________________________ > 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=E2=80=9D Of course, I linked to the wrong commit, that should be: https://reviews.freebsd.org/rS336281 In particular rS336281 seems to have been a follow up to rS334880. -Marcel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2DB40DB6-73D0-440A-94B3-82A173E9DF3E>