Date: Wed, 17 Jun 2020 20:32:36 +0000 From: Dan Kotowski <dan.kotowski@a9development.com> To: myfreeweb <greg@unrelenting.technology> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <z-iiKTafA-iirmiH_wVWUM9BHEa9uhccyljIc5_buK8CgCdzAXdUgQuViiaULImI0BVmx9N3lKO_9_NN9IHfSYCv1H9W9P8n98ltXG02MT4=@a9development.com> In-Reply-To: <BE2611FE-FC83-4E3D-9977-E502DE8537A7@unrelenting.technology> References: <NkmJNP_BMdinQ07E7zvRW9EQtYTkHLISOPlALNNcbFXi7d0dsuvgHD2IW73ptiSh1kEml7_VHb9_eTIMaLAIeAici_qpz2UyIrBWzXR4mvE=@a9development.com> <c1788ee7f14b9236e0972909032cb8fd@unrelenting.technology> <940a6099e971e01bd6d04564d0982b9d@unrelenting.technology> <c1e4129989005bc9bfd117988019107d@unrelenting.technology> <XYXpaNQ3XeZR6g5RpmjR3qs56wTKfNi_OpPX53S3yYdPMNMWR0kme-Q7hmNpxzR6EL3DqKxUnG8BcW6ueHv82Kaexu1j4VSLtNtQgYuxX_g=@a9development.com> <eRSoUazwekUoXHKtXhs_unN_78Zp3ow_uJ8j-ODdb7mgzz3n8L18wonbrqkmPn2ulVXoUKxHLh8Cc0VU6KMeIEm3X0KsPn8NH-JiqKmq8fI=@a9development.com> <D2780D27-20F4-4706-9956-7E188AD73F62@unrelenting.technology> <iIPsVK-flf-29Ti4agFHulCx5v1aEOVnPY6tyxErDGGxUlRvonYC7xCUGxHNgH64ZOpBLbwzAubg8gARrYPgd8qLOVfFk1PmcxSp0QNB_js=@a9development.com> <BE2611FE-FC83-4E3D-9977-E502DE8537A7@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > By the way, did you get any different firmware builds in the meantime= ? That don't have everything suspiciously routed to the SMMU in IORT.. > > > > s/suspiciously/by design/ > > BEGIN QUOTE > > the PCIe root nodes are hidden from the rich OS with this configuration= . To access the root nodes you need a quirk implemented. > > eventually it will be an option for those that want to run custom kerne= ls, but for now this is the solution for the most SBSA like configuration > > END QUOTE > > And how are we supposed to get any MSI-X interrupts in this configuration= ? > > Our fallback code for when nothing was matched in IORT (i.e. directly usi= ng PCIe RID with no offset) did not result in working interrupts. > > IIRC legacy interrupts didn't work either, but maybe you should retest th= em (disabling MSI, MSI-X). NSTR, but here you go anyways: https://gist.github.com/agrajag9/d4d75d7dca4= 1b3cb64c0a4243eed4eb7 Forgive my n00bishness and feel free to correct me below, I'm still learnin= g my way around down here... What are we doing with all the GSIVs in the IO= RT SMMU node? Based on reading the table and dmesg.boot, I'm seeing the following: * ITS node for gics * 2 root complex nodes for pci0 and 1, * Named component nodes for MCE, ugens, mmcs (if we still had that in), and= ahcis But then the SMMU node has: * 64 context interrupts, * 10 PMU interrupts, and * 5 ID mappings Where do these go? Are we perhaps not walking this section properly and tha= t's the quirk to which Jon is referring?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?z-iiKTafA-iirmiH_wVWUM9BHEa9uhccyljIc5_buK8CgCdzAXdUgQuViiaULImI0BVmx9N3lKO_9_NN9IHfSYCv1H9W9P8n98ltXG02MT4=>