Date: Sun, 6 Jan 2019 16:04:42 -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: <20190106210442.o3vmftxvdy4huihv@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
--iqyorbvit3i5wqbz 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 Jarachandran, Could you provide a sha256 hash of the uploaded firmware? 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 --iqyorbvit3i5wqbz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAlwybWUACgkQaoRlj1JF bu7m8w/7BlclsuqXmf0j7Tyga68L86pFpmOL/7Fhkv4L6PqDRIEdf5Hl3325NMgE iJxX9iAaJ36hPk14k4W9yFFqWEiVtZlgOfh1mut7i0q8mrsXq1Sjdh/IR5YUzx5S DcfUwV1/zptmldSdcWHBHl9/4Hudu4YGpT+jxBW7ykV5UzOZR2vymUG1NBDfAkSE hVeBi9U1hf/i49Uf5slrqPU1XCG6q0Axq2EIQiMF7bKw7y5benToMYyw4DIbLqOw lw7CbcYZAjnY22neRoCcWEn/4oz54xDjwvdQAxvtiA9IRO+unFnesRGTACg9mgVE 0D/pcoKRq/z6JICFdAKzupTZ2YxIbZ94dxu0quf6cjRY5oVbIxy+3z2c40f65xJR FKoH4tVzBiqiCwmHzl2P3QkQ7XYAwirtvIg0+z0po77PKCh8NNpRgbZrU/ZHWstX ShMjwxdXbvGhDDn+WIYxOrM8NyuiIiLS/4FAmQebqASxafwbwOokixF8fD9TZ9dp 8/ha/6UpPdg3ODpKfCDfQTiwIv+frs5P90kMo6jDuWEKbXRnx6QzxwbtTBMNjDYI IqHcTGX8JwCBFTvHJ7BvaG8EL6wf79+XisCFXeM0LgVkdq4yjnlE9TfiqNnEVxsd 667aFawkU2ND9uy4Zvgh3BB6u5udqPCaL9nzs47DYSyAcDz/u94= =uLUI -----END PGP SIGNATURE----- --iqyorbvit3i5wqbz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190106210442.o3vmftxvdy4huihv>