Date: Sat, 23 May 2020 00:37:23 +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: <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> In-Reply-To: <SBSqkdZA-3beqJyVy2tMuk5GRmV22DVVnz_8sNDhYCNOjNPe1wgoiSCoOitGhtlBspk-Gk2MKFv4sUyJKy58mKOBpXrGtZoRQKqmDvB1xIg=@a9development.com> References: <SBSqkdZA-3beqJyVy2tMuk5GRmV22DVVnz_8sNDhYCNOjNPe1wgoiSCoOitGhtlBspk-Gk2MKFv4sUyJKy58mKOBpXrGtZoRQKqmDvB1xIg=@a9development.com> <sDsSd2a4wzx3y3IiDCx0GjOKgeVqGwVV_Aegg5WuTGWK-cU377qCaUqd09qSXBnGnYHCyEtPMjXObW6PSVanoUFsm7Sy8b11hDW9o6Q-xQI=@a9development.com> <d709b1aae3d33f49fadcce9817cb102a@unrelenting.technology> <LqTdXCGMiTFwSobCq9LtV5QVLOZ42AiBDUTC9UrdM67cUlD_I8Y7no-8F7d_vs3VDJwIFJLgHTSZVrbkIXXeZ_-hcU0FxfWj0dr-GvhKXHA=@a9development.com> <b04385d558850dc1dfa60fc398c9ac6c@unrelenting.technology> <CAPv3WKdyOzegfK4NJjKzXQTp9jGV9VkDRWxY%2BhDudzWQKkRfEQ@mail.gmail.com> <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology> <86119565e5927716a9feebabcb611871@unrelenting.technology> <f801aa134da12d1b4a34b87dbc180b4a@unrelenting.technology> <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology>
index | next in thread | previous in thread | raw e-mail
May 23, 2020 2:32 AM, "Dan Kotowski" <dan.kotowski@a9development.com> wrote: >>> I spent some time looking at that NetBSD Layerscape code - I couldn't figure out how to add it >>> trivially to the current HEAD on my own, so I'm looking forward to seeing how we're going to yeet >>> that in for testing... >>> Something like this: >>> https://github.com/myfreeweb/freebsd/commit/6cbdafbc310b9a0fa4d046f71979aa01302e8b0b >>> https://send.firefox.com/download/ec0419c6d3fa856e/#QOMHO8pBq1dP1K2_4P4CBw >> >> https://gist.github.com/agrajag9/b214aa837d0ed6bb14139770ff5835ff >> Line 404: panic: Misaligned access from kernel space! >> >> oops, I actually have to care about the`bytes` parameter.. >> >> at least I got the ACPI-walking on the first try :) >> >> https://send.firefox.com/download/6406af63fee41a8a/#FnEEayn7igQ_eTGs0Wq0uw > > https://gist.github.com/agrajag9/b47d63484fa51eed535d8a43625a5276 hmmm. there's now a pcib2: <PCI-PCI bridge> at device 0.0 on pci1 and it actually does allocate memory, after the root fails to: pcib1: rman_reserve_resource: start=0x670000000, end=0x67003ffff, count=0x40000 pcib1: pci_host_generic_core_alloc_resource FAIL: type=3, rid=28, start=0000000670000000, end=000000067003ffff, count=0000000000040000, flags=4800 pcib2: allocated memory range (0x70040000-0x7007ffff) for rid 1c of pci1:1:0:0 iiiinteresting. Try to kldload mpr/mps/whatever? Also insert the nvme drivehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7066da0bc417ed047dc27b4741c90e81>