Date: Tue, 19 May 2020 19:22:39 +0000 From: greg@unrelenting.technology To: "Dan Kotowski" <dan.kotowski@a9development.com>, "Marcin Wojtas" <mw@semihalf.com> Cc: "freebsd-arm" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology> In-Reply-To: <Ax3PRJg04l7bMoKmAlH13VNwNlBXYcDTSDYgnxJmZpTX5TQVgvpdQ_BNoqm136KK3iefGdUeCrvnOseWeRVUYK2Ly2n8Umio1yGAlg1ToU4=@a9development.com> References: <Ax3PRJg04l7bMoKmAlH13VNwNlBXYcDTSDYgnxJmZpTX5TQVgvpdQ_BNoqm136KK3iefGdUeCrvnOseWeRVUYK2Ly2n8Umio1yGAlg1ToU4=@a9development.com> <TLwmTbuqZXh21TMiFjCu96O2fOIoWgPXE-0amhQa7y66As1E39i0v-nC7j1saPpCy8KrT63uE_W92527rywGhtxTKVATtYBSLfrLRdZ3faA=@a9development.com> <2053cd2299b81860deecc638ef839d1f@unrelenting.technology> <0012917d629a48e9fcd8589f4f002e1b@unrelenting.technology> <947c2f9bfaad823a2b104b8741502b40@unrelenting.technology> <c88780825e96fe583b32adf86416706e@unrelenting.technology> <d709b1aae3d33f49fadcce9817cb102a@unrelenting.technology> <LqTdXCGMiTFwSobCq9LtV5QVLOZ42AiBDUTC9UrdM67cUlD_I8Y7no-8F7d_vs3VDJwIFJLgHTSZVrbkIXXeZ_-hcU0FxfWj0dr-GvhKXHA=@a9development.com> <b04385d558850dc1dfa60fc398c9ac6c@unrelenting.technology> <CAPv3WKdyOzegfK4NJjKzXQTp9jGV9VkDRWxY%2BhDudzWQKkRfEQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
May 19, 2020 9:17 PM, "Dan Kotowski" <dan.kotowski@a9development.com> wro= te:=0A=0A>>> I can't find the PCIe cables for my PSU right now, so the RX= 480 is out until I have time to dig=0A>>> through The Cable Box Of Doom. = But I do have a spare LSI SAS HBA that I'll try after lunch!=0A>> =0A>> Y= eah, mpr/mps drivers are present, would be an okay thing to try.=0A> =0A>= Latest dmesg.boot: https://gist.github.com/agrajag9/cf6d203dc3730350182c= b53ba5a8b999=0A> =0A> The HBA came up as pci1 on pcib1 (line 105). And, a= s expected since it came up as a generic PCI=0A> device rather than MPR/M= PS, the attached drive doesn't show up. And yes, I did confirm that mpr.k= o=0A> and mps.ko are present in /boot/kernel/=0A=0AThe problem is not tha= t the driver isn't loaded (you can always just kldload it manually), it's= this sadness:=0A=0Apcib1: pci_host_generic_core_alloc_resource FAIL: typ= e=3D4, rid=3D16, start=3D0000000000040000, end=3D00000000000400ff, count= =3D0000000000000100, flags=3D2000=0Apcib1: pci_host_generic_core_alloc_re= source FAIL: type=3D4, rid=3D16, start=3D0000000000000000, end=3Dffffffff= ffffffff, count=3D0000000000000100, flags=3D2000=0Apcib1: pci_host_generi= c_core_alloc_resource FAIL: type=3D3, rid=3D20, start=3D0000000670440000,= end=3D0000000670443fff, count=3D0000000000004000, flags=3D3800=0Apcib1: = pci_host_generic_core_alloc_resource FAIL: type=3D3, rid=3D28, start=3D00= 00000670000000, end=3D000000067003ffff, count=3D0000000000040000, flags= =3D4800=0A=0ALooking at NetBSD code, we might need to implement support f= or the custom NXP0016 config device:=0A=0Ahttps://github.com/NetBSD/src/c= ommit/1a0fb037e62e4e3472966e33588957919b5e3a97=0A=0AI'll have time to att= empt a blind port of that code next week :D=0A=0AThere is a way to get an= y stock OS (even Windows!) to work with this PCIe controller,=0Abut it in= volves awful hacks and legacy interrupts, unacceptable stuff:=0Ahttps://t= witter.com/linux4kix/status/1260946442346205184=0A=0Aso you'll have to wa= it for now.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3e81db774e0fc1a3c2251c89b7629e1b>