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>
index | next in thread | previous in thread | raw e-mail
June 3, 2020 7:09 PM, "myfreeweb" <greg@unrelenting.technology> wrote: > On June 3, 2020 1:37:34 PM UTC, Dan Kotowski <dan.kotowski@a9development.com> wrote: > >>>>> I've sent a link to a known firmware build before: >>>>> https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/view >>>>> Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? >>>> >>>> I decided to go back to the UEFI sources and have found some differences that I think need to be >>> reconciled before moving forward. That said, I'm not an ACPI wizard by any means - for me it's >>> low-level mage spells at best... >>>> In https://github.com/SolidRun/edk2-platforms we have 2 different branches that SolidRun seems to >>> use: >>>> >>>> 1. LSDK-19.09-sr >>>> 2. master-lx2160a >>>> >>>> I've been building from the latter branch, but found some significant differences in the former >>> that I think may be important to merge in. >>> >>> To me it seems like 19.09 is just outdated and doesn't have any benefits. Ask the solidrun people >>> to be sure. >>> >>> Either way, nothing here would fix the interrupt bug. It's our bug since NetBSD works fine :( >> >> Any chance I can get a new test kernel without PCIe quirks? I just got a much more recent image >> from jnettlet with the following comments: >> >> BEGIN QUOTE >> If you are using that recent uefi firmware I posted then you shouldn't be using the quirks for >> pcie. That has an ecam shift setup where it should behave....relatively to SBSA standards. >> it definitely won't work with the quirk enabled though. I have to add an interface to edk2 to turn >> the mode on or off depending if you want access to the root bus and have a kernel with the quirk >> applied, or you want it to work with just the devices exposed but in a more compliant manner >> without quirks >> END QUOTE > > In the last couple kernels I posted, you should be able to set debug.acpi.disabled=pci_layerscape > to skip the quirk. > > I'll build the next one soon though, I guess with more interrupt debug prints lol https://send.firefox.com/download/ae38fa35246497c1/#AVSGMsnrM0YB2MSL7rRJRQ - customized pcie driver + https://reviews.freebsd.org/D25121 + more interrupt debugging (stray interrupts, all GIC config writes)help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32d1c173d986884efb9b28932c0ead52>