Date: Fri, 4 Jan 2019 15:31:33 -0500 From: Shawn Webb <shawn.webb@hardenedbsd.org> To: "Jayachandran C." <jchandra@freebsd.org> Cc: Ed Maste <emaste@freebsd.org>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: ThunderX2 support in FreeBSD/arm64 Message-ID: <20190104203133.euftenspsfxp7vyq@mutt-hbsd> In-Reply-To: <CA%2B7sy7CGqEPpZ5LMcB7iy-m=hOiH6waauO9GPESicJc=kTnGMg@mail.gmail.com> References: <CA%2B7sy7BWtSi5uDgusf-sEHd06EGXwnUxo9cr8A9gLh1L_YJoXw@mail.gmail.com> <CAPyFy2DXHvAudezY9TUjnADO4FAbeKthxGyEOvow89iXmXa9ig@mail.gmail.com> <CA%2B7sy7CGqEPpZ5LMcB7iy-m=hOiH6waauO9GPESicJc=kTnGMg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--yp2u43dytvahevui Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 03, 2019 at 12:51:26PM -0800, Jayachandran C. wrote: > (Was AFK for a while, sorry for the late reply) > Hi Ed, >=20 > On Fri, Dec 21, 2018 at 11:15 AM Ed Maste <emaste@freebsd.org> wrote: > > > > On Mon, 17 Dec 2018 at 21:51, Jayachandran C. <jchandra@freebsd.org> wr= ote: > > > > > > Over the last few weeks I have committed changes for a few outstanding > > > items needed for ThunderX2 support in FreeBSD/arm64. > > > > I see that D10082, D10083, D10084 are still open, awaiting review. > > Should I apply them to my test tree? > > > > My current status - loader claims to start the kernel, but I see no > > further output. Can you share the kernel config file you used (or > > perhaps a git tree you built from)? >=20 > There seems to be 2 issues here - both of them happen when the AMI > firmware is used. > The first issue is that the efi framebuffer does not work, and I am > not able to select the serial console with AMI firmware. The second > issue is that the on-chip SATA controller is not setup correctly by > the AMI firmware and can cause a 'NBU BAR error' failure. >=20 > I have uploaded a test firmware and instructions to > https://people.freebsd.org/~jchandra/testfw/ which should boot FreeBSD > fine. This is an internal build which does not have both the problems > above. Let me know if this works, and I will try to push the fixes to > AMI. Hey Jayachandran, I'll apply the test firmware on my end either this weekend or Monday. I'll report back afterwards. Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --yp2u43dytvahevui Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAlwvwqAACgkQaoRlj1JF bu5xLQ//S2pa3f2h6im7BA0bkLtrlQAW551KVP/n488pp0V+ZVLQyo6PdpHr8ECe wi/lLU672FK/KsLptJFum8trPOtZWbhyPBV0v32fAvLNDUw0WTrRMgzTMtOZJcBC xKvUpwZ2GzniNdc4Yv1mqYa/ipjnW+g4kWBYzIIOLZxP3y9YgaB+LvYrPpkKhuPg BOn1eVRX/l2Bt4fuPzhYFbfIFmeQ/BpECSWGcGZMxgQdA0KNxdUXNuZynxtMCMka bnUAgg1l0zyyIKzfI838yxi0dYYKe/UJ0P0iSKklRTTfeiQPRWqs3B+js4r2h1le nWJEbRoA1pawbyjlm1QJZ07oXjU0dc4e7S4lMTOhcI1pZscNGDjXr7EpS/6XO5p3 xK/ITudD270YXdQfdsfsnfJz121T+P8gym+wKtZXlZ40LOSZCU99Iqo0VH5nXIz2 i/lvn6A7Ejm50MQmHGYXX0SPPUy3eXDE2S+5AyO4OSSCQsyNoq0GzDxSZ9nAgA1K 9zn8OgTqTlze8Mj+C/p0EX3sWkdWmkW9Pr4WDNe4cbgz3lIXQ+tWNleBx1PAGK+E Lj0MFCH4GqwQHBnvdoX/NFDVZeMyllrfg5vP4kpDmHIcSWXwA4Hq4nzzsYufYB+C xGIy07amLgvt7pjNQGBtskbith2wAStdjJRKKpRK4v7bSC78udg= =io+Y -----END PGP SIGNATURE----- --yp2u43dytvahevui--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190104203133.euftenspsfxp7vyq>