Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 May 2020 14:13:21 +0000
From:      greg@unrelenting.technology
To:        "Warner Losh" <imp@bsdimp.com>, "Dan Kotowski" <dan.kotowski@a9development.com>
Cc:        "freebsd-arm" <freebsd-arm@freebsd.org>
Subject:   Re: FreeBSD on Layerscape/QorIQ LX2160X
Message-ID:  <664db38a87ea8803be72af9738534994@unrelenting.technology>
In-Reply-To: <f5e74382291265f01b2dd29ce9180a55@unrelenting.technology>
References:  <f5e74382291265f01b2dd29ce9180a55@unrelenting.technology> <6E6E4F0C-F85B-428B-B221-C5F704677076@unrelenting.technology> <SBSqkdZA-3beqJyVy2tMuk5GRmV22DVVnz_8sNDhYCNOjNPe1wgoiSCoOitGhtlBspk-Gk2MKFv4sUyJKy58mKOBpXrGtZoRQKqmDvB1xIg=@a9development.com> <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> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <xoiJF1ZUP3-rgbxC8ZmJGQNpsJSyK4zsAXhbLl8Ml96Da1lBPGwPqn0ANf7q-GgthPAWePSR9QDCM5vKysd_3e2aGtp-0egUXu6AW3bhLDg=@a9development.com> <CANCZdfqbd_u35toFYKr4LKkCBwnRhutM5knjnVcGR018Jfo1Vw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
May 24, 2020 5:03 PM, greg@unrelenting.technology wrote:=0A=0A> I also lo=
oked more closely at mps, and actually "just polling I/O" does work. We s=
ee:=0A> mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,=
TransRetry,EventReplay,HostDisc>=0A> and that means mps_request_sync (cal=
led by mps_get_iocfacts) has worked.=0A> =0A> And the command completion =
actually seems to come from interrupts.=0A> =0A> I've heard something abo=
ut MSI(X) not working for the Linux people (not NetBSD though!),=0A> so I=
 guess the next thing to try would be booting with hw.pci.enable_msi=3D0 =
hw.pci.enable_msi=3D1=0A=0A=0Alol, I mean, hw.pci.enable_msi=3D0 hw.pci.e=
nable_msix=3D0



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?664db38a87ea8803be72af9738534994>