Date: Thu, 3 Jan 2019 12:51:26 -0800 From: "Jayachandran C." <jchandra@freebsd.org> To: Ed Maste <emaste@freebsd.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: ThunderX2 support in FreeBSD/arm64 Message-ID: <CA%2B7sy7CGqEPpZ5LMcB7iy-m=hOiH6waauO9GPESicJc=kTnGMg@mail.gmail.com> In-Reply-To: <CAPyFy2DXHvAudezY9TUjnADO4FAbeKthxGyEOvow89iXmXa9ig@mail.gmail.com> References: <CA%2B7sy7BWtSi5uDgusf-sEHd06EGXwnUxo9cr8A9gLh1L_YJoXw@mail.gmail.com> <CAPyFy2DXHvAudezY9TUjnADO4FAbeKthxGyEOvow89iXmXa9ig@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
(Was AFK for a while, sorry for the late reply) Hi Ed, 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> wrote: > > > > 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)? 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. 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. Thanks, JC.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B7sy7CGqEPpZ5LMcB7iy-m=hOiH6waauO9GPESicJc=kTnGMg>