Date: Tue, 19 May 2020 20:36:42 +0000 From: Dan Kotowski <dan.kotowski@a9development.com> To: "greg@unrelenting.technology" <greg@unrelenting.technology> Cc: Marcin Wojtas <mw@semihalf.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <JXdx2L0dNn6BmD5KjF5iCCkc-z3xUH-gPmRZGiF4TCDESdw2lmPGWJNuOQWsxoE9Eumz8bFoXkrgr0rxkm9RCxCIw6fF3NrwSQFvsLtOSsY=@a9development.com> In-Reply-To: <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology> References: <Ax3PRJg04l7bMoKmAlH13VNwNlBXYcDTSDYgnxJmZpTX5TQVgvpdQ_BNoqm136KK3iefGdUeCrvnOseWeRVUYK2Ly2n8Umio1yGAlg1ToU4=@a9development.com> <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> <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > I can't find the PCIe cables for my PSU right now, so the RX480 is = out until I have time to dig > > > > through The Cable Box Of Doom. But I do have a spare LSI SAS HBA th= at I'll try after lunch! > > > > > > Yeah, mpr/mps drivers are present, would be an okay thing to try. > > > > Latest dmesg.boot: https://gist.github.com/agrajag9/cf6d203dc3730350182= cb53ba5a8b999 > > The HBA came up as pci1 on pcib1 (line 105). And, as expected since it = came up as a generic PCI > > device rather than MPR/MPS, the attached drive doesn't show up. And yes= , I did confirm that mpr.ko > > and mps.ko are present in /boot/kernel/ > > The problem is not that the driver isn't loaded (you can always just kldl= oad it manually), it's this sadness: > > pcib1: pci_host_generic_core_alloc_resource FAIL: type=3D4, rid=3D16, sta= rt=3D0000000000040000, end=3D00000000000400ff, count=3D0000000000000100, fl= ags=3D2000 > pcib1: pci_host_generic_core_alloc_resource FAIL: type=3D4, rid=3D16, sta= rt=3D0000000000000000, end=3Dffffffffffffffff, count=3D0000000000000100, fl= ags=3D2000 > pcib1: pci_host_generic_core_alloc_resource FAIL: type=3D3, rid=3D20, sta= rt=3D0000000670440000, end=3D0000000670443fff, count=3D0000000000004000, fl= ags=3D3800 > pcib1: pci_host_generic_core_alloc_resource FAIL: type=3D3, rid=3D28, sta= rt=3D0000000670000000, end=3D000000067003ffff, count=3D0000000000040000, fl= ags=3D4800 > > Looking at NetBSD code, we might need to implement support for the custom= NXP0016 config device: > > https://github.com/NetBSD/src/commit/1a0fb037e62e4e3472966e33588957919b5e= 3a97 > > I'll have time to attempt a blind port of that code next week :D > > There is a way to get any stock OS (even Windows!) to work with this PCIe= controller, > but it involves awful hacks and legacy interrupts, unacceptable stuff: > https://twitter.com/linux4kix/status/1260946442346205184 > > so you'll have to wait for now. I've waited this many months to finally get this far, another week is no pr= oblem :D Would you be able to share any patches and kernconfs you're working from so= I have a frame of reference? My own dev skills are certainly nowhere near = yours, but I'd like to at least read through the code you've applied to get= us this far and maybe even learn something new along the way.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?JXdx2L0dNn6BmD5KjF5iCCkc-z3xUH-gPmRZGiF4TCDESdw2lmPGWJNuOQWsxoE9Eumz8bFoXkrgr0rxkm9RCxCIw6fF3NrwSQFvsLtOSsY=>