Date: Mon, 06 Jul 2020 17:00:22 +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: <a5b8fd2df391c4c4da914f5f425ef23f@unrelenting.technology> In-Reply-To: <82UUBttUqS5j5wotn5ibAhp3w3JveSof3dsBLqW68NkaOu1xc6txd62UJeyJgV6hk9mLNYqhAJDyEej_PPtiv_ps9vROdUI529pKfxp4lbs=@a9development.com> References: <82UUBttUqS5j5wotn5ibAhp3w3JveSof3dsBLqW68NkaOu1xc6txd62UJeyJgV6hk9mLNYqhAJDyEej_PPtiv_ps9vROdUI529pKfxp4lbs=@a9development.com> <kkodEYp_933GKBWBelm63luHcdDwaJ9WtfRtjVABbaYbQRXhH1W3w45T4PALvtMXXo6NNWbB7pgRdYZxJDNUHFKibY1FuHqIpPjiXZBAnxs=@a9development.com> <NkmJNP=5FBMdinQ07E7zvRW9EQtYTkHLISOPlALNNcbFXi7d0dsuvgHD2IW73ptiSh1kEml7=5FVHb9=5FeTIMaLAIeAici=5Fqpz2UyIrBWzXR4mvE=3D@a9development.com>_<D2780D27-20F4-4706-9956-7E188AD73F62@unrelenting.technology>_<iIPsVK-flf-29Ti4agFHulCx5v1aEOVnPY6tyxErDGGxUlRvonYC7xCUGxHNgH64ZOpBLbwzAubg8gARrYPgd8qLOVfFk1PmcxSp0QNB=5Fjs=3D@a9development.com>_<BE2611FE-FC83-4E3D-9977-E502DE8537A7@unrelenting.technology>_<z-iiKTafA-iirmiH=5FwVWUM9BHEa9uhccyljIc5=5FbuK8CgCdzAXdUgQuViiaULImI0BVmx9N3lKO=5F9=5FNN9IHfSYCv1H9W9P8n98ltXG02MT4=3D@a9development.com>_<71481BF5-3972-45A3-8287-FCEB1FCCDC41@unrelenting.technology> <I1KXMCQnSlZ49JcvIWbgOokJWv657vtAL4qs6eukqNEgvruGhpXhShgMklyEt525b191cDqiUxEvCFmaS_SakxoFijsFRYe0pWoGebD7BDs=@a9development.com> <A16FE19C-C34D-4100-9229-99FD098F8DE4@unrelenting.technology> <aG_BP2g5oB3XsAIQofWKiBCgLpUrPkxZQ6y11ArFprHlTKKvnUDrXRcFPJBAhZWKJMGuGmkEP1QAaRijb4Yv0R2v_4RrmRWyPOtO6jQlAzE=@a9development.com> <C4EFD0F3-FFD0-4789-B976-3DBA00395CCC@unrelenting.technology> <8a3f78ddd5136ef22c59e9f7b1b23ca6@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
July 6, 2020 7:07 PM, "Dan Kotowski" <dan.kotowski@a9development.com> wro= te:=0A=0A>> In the old firmware, under the Root Complex Nodes, `Output re= ference: 0x30` points to the ITS Node=0A>> with node offset 0x30.=0A>> Th= en in the new firmware, under the Root Copmlex Nodes, `Output reference: = 0x48` points to the SMMU=0A>> with node offset 0x48.=0A>> Is this what yo= u meant when you said everything is "behind the SMMU"?=0A>> =0A>> Yes.=0A= >> =0A>> What patches are we applying right now? I think some new builds = would be good, including one with=0A>> all the stuff we've fixed - like A= HCI - but with the NXP PCIe code so I can test on the old=0A>> firmware. = If I'm keeping track correctly, this includes:=0A>> =0A>> - D20835: enabl= e tagged pointers=0A>> - D20974: Port sbsawdt drive from NetBSD=0A>> - D2= 1017: armv8crypto: add AES-XTS support=0A>> - D24423: arm/pmu: add ACPI a= ttachment, more FDT names=0A>> =0A>> These are not directly related to ru= nning on NXP, just random improvements :)=0A>> =0A>> - D25145: acpi_resou= rce: support multiple IRQs=0A>> - D25157: ahci_generic: add quirk for NXP= 0004=0A>> - D25179: acpi_iort: fix mapping end calculation=0A>> =0A>> Yes= , these three.=0A>> =0A>> Here's the pci_layerscape patch:=0A>> =0A>> htt= ps://github.com/DankBSD/base/commit/c1ea44aa33b29f74daed89eee82b3dfeb105d= 376.patch=0A>> =0A>> If we haven't tried it + acpi_iort fix before, which= is quite likely, maybe that's a combination=0A>> that would work.=0A>> (= I remember when we tried it only, there was only the same interrupt probl= em as usual..)=0A>> =0A>> It's honestly kinda weird that "old" FW require= s the custom controller access while "new" FW=0A>> requires not doing it = >_<=0A> =0A> Any tips on where to add verbosity to dmesg during boot? You= had a handful of extras in there to=0A> print things things from the IOR= T.=0A=0AThat thing is here:=0Ahttps://github.com/freebsd/freebsd/blob/6ce= e1596c05e8a9ab64812444627b61c584ca6bc/sys/arm64/acpica/acpi_iort.c#L169= =0A=0A> Also seeing that NVMe hangs in nvme_ctrlr_start_config_hook,=0A> = maybe we want to add some verbosity to sys/dev/nvme/nvme_ctrlr.c to see w= hat it's waiting for?=0A=0A=0AWe know it's an interrupt.. everything is w= aiting for an interrupt.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a5b8fd2df391c4c4da914f5f425ef23f>