Date: Wed, 03 Jun 2020 23:40:52 +0000 From: greg@unrelenting.technology To: "Dan Kotowski" <dan.kotowski@a9development.com> Cc: "freebsd-arm" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> In-Reply-To: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> References: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> <fn58k-44ZAkuwnDdytVzV-cLaB9amYMgZWydbpR_muUcKNZwohKqn9zFxqqw_Vz8Ij8L8yOSv0XhefrcTSo_bSYSOe5_7wcjoBWl8Q2dDVM=@a9development.com> <xoiJF1ZUP3-rgbxC8ZmJGQNpsJSyK4zsAXhbLl8Ml96Da1lBPGwPqn0ANf7q-GgthPAWePSR9QDCM5vKysd_3e2aGtp-0egUXu6AW3bhLDg=@a9development.com> <CANCZdfqbd_u35toFYKr4LKkCBwnRhutM5knjnVcGR018Jfo1Vw@mail.gmail.com> <664db38a87ea8803be72af9738534994@unrelenting.technology> <b5105ce888b7a91eff50ec9118a910a8@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <ShdSNL8XDgj0KtPR4v8nn1ohjVssrnoUQGwNL-gHOpylio7Eo5J_WjA2Ko9YjV5md64MeFz017Ts01KUnpJa3Xpw4y_PncL4e5cfUcotRWM=@a9development.com> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <ZdPk7zJSE8UvoonkTixa2gV04ujgKfY93A71fz8cTB6ZPjt2uSCD5TdvFzDAEIR9Tu5LoGrcZLmXqgyrCmzh8OIB2JLc4gNKr6xF0pe931M=@a9development.com>
next in thread | previous in thread | raw e-mail | index | archive | help
June 3, 2020 7:09 PM, "myfreeweb" <greg@unrelenting.technology> wrote:=0A= =0A> On June 3, 2020 1:37:34 PM UTC, Dan Kotowski <dan.kotowski@a9develop= ment.com> wrote:=0A> =0A>>>>> I've sent a link to a known firmware build = before:=0A>>>>> https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhA= ClJGvErK/view=0A>>>>> Have you tried it? Any difference in FreeBSD/NetBSD= , with NVMe?=0A>>>> =0A>>>> I decided to go back to the UEFI sources and = have found some differences that I think need to be=0A>>> reconciled befo= re moving forward. That said, I'm not an ACPI wizard by any means - for m= e it's=0A>>> low-level mage spells at best...=0A>>>> In https://github.co= m/SolidRun/edk2-platforms we have 2 different branches that SolidRun seem= s to=0A>>> use:=0A>>>> =0A>>>> 1. LSDK-19.09-sr=0A>>>> 2. master-lx2160a= =0A>>>> =0A>>>> I've been building from the latter branch, but found some= significant differences in the former=0A>>> that I think may be importan= t to merge in.=0A>>> =0A>>> To me it seems like 19.09 is just outdated an= d doesn't have any benefits. Ask the solidrun people=0A>>> to be sure.=0A= >>> =0A>>> Either way, nothing here would fix the interrupt bug. It's our= bug since NetBSD works fine :(=0A>> =0A>> Any chance I can get a new tes= t kernel without PCIe quirks? I just got a much more recent image=0A>> fr= om jnettlet with the following comments:=0A>> =0A>> BEGIN QUOTE=0A>> If y= ou are using that recent uefi firmware I posted then you shouldn't be usi= ng the quirks for=0A>> pcie. That has an ecam shift setup where it should= behave....relatively to SBSA standards.=0A>> it definitely won't work wi= th the quirk enabled though. I have to add an interface to edk2 to turn= =0A>> the mode on or off depending if you want access to the root bus and= have a kernel with the quirk=0A>> applied, or you want it to work with j= ust the devices exposed but in a more compliant manner=0A>> without quirk= s=0A>> END QUOTE=0A> =0A> In the last couple kernels I posted, you should= be able to set debug.acpi.disabled=3Dpci_layerscape=0A> to skip the quir= k.=0A> =0A> I'll build the next one soon though, I guess with more interr= upt debug prints lol=0A=0Ahttps://send.firefox.com/download/ae38fa3524649= 7c1/#AVSGMsnrM0YB2MSL7rRJRQ=0A=0A- customized pcie driver=0A+ https://rev= iews.freebsd.org/D25121=0A+ more interrupt debugging (stray interrupts, a= ll GIC config writes)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32d1c173d986884efb9b28932c0ead52>