Date: Sat, 5 Sep 2020 16:40:53 +0200 From: Klaus Cucinauomo <maciphone2@googlemail.com> To: Robert Crowston <crowston@protonmail.com>, myfreeweb <greg@unrelenting.technology>, Hans Petter Selasky <hps@selasky.org>, Mark Millard <marklmi@yahoo.com>, freebsd-arm@freebsd.org Subject: Re: onboard wireless on rpi4 Message-ID: <3A935200-8545-4A86-80D5-3E0DEA156F56@googlemail.com> In-Reply-To: <sinTekBDB_YOboAoJU0Uld7IaGBlIJ68dPgxuO3kcUuZpTH9KxyTquRgPxU7-0qlvofrr_8HzdCbNL-nRNaT6-OeIyIuLUUvYSGEwEzRVbc=@protonmail.com> References: <20200904134619.GB80905@bastion.zyxst.net> <69934262-D9D3-4986-849D-9E8221D1E387@kronometrix.org> <20200904142255.GC80905@bastion.zyxst.net> <CACNAnaHRn5VGM8G6_kxj7S%2B0LQOSG3CK9=umxj74Qc5v%2BNOLeA@mail.gmail.com> <BE2FA7D2-1266-496E-B808-55204B1AB21A@yahoo.com> <5AF83D16-2432-4EA9-BC2F-373DA8BC3360@googlemail.com> <4306A90D-97B9-4DE9-A05A-A91B6F4A587F@yahoo.com> <sinTekBDB_YOboAoJU0Uld7IaGBlIJ68dPgxuO3kcUuZpTH9KxyTquRgPxU7-0qlvofrr_8HzdCbNL-nRNaT6-OeIyIuLUUvYSGEwEzRVbc=@protonmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Did someone tell me this is *not* a problem at all on NetBSD/OpenBSD? while I have to update my knowledge of what happened the last weeks @ = fbsd/netbsd/openbsd src(I didn=E2=80=99t work on it for some weeks)=E2=80=A6= For OpenBSD that was probably me, for NetBSD must have been Mark... both NetBSD and OpenBSD do NOT have an exclusive pcie-driver for the = DeviceTree mode like Fbsd has , thanks to you. You remember the discussion with HPS and myfreeweb... : https://github.com/pftf/RPi4/issues?page=3D2&q=3Dis%3Aissue+is%3Aclosed so for PCIe/fdt it=E2=80=99s an exclusive thing for you (and in terms of = inheritance HPS, as far as I remember) > I can submit the patch I have but it=E2=80=99s not a 100% fix. Of course, please submit if you have something newer than already exists = in Phabricator : I=E2=80=99m sure that Mark(Millard) is already sharpening his knife to = give you test-feedback from his large-file tests;-)=20 And yes, your last dma-fix significantly reduced the problem of = unexpected controller resets, but according to Mark not the=20 large file-copy-handling(I didn=E2=80=99t test that issues). thank you, kls > Am 05.09.2020 um 10:59 schrieb Robert Crowston = <crowston@protonmail.com>: >=20 > Regrettably the DMA problem is not fixed. After fixing the bus tag to = correctly represent the DMA limit of the device, it reduced the problem = incidence a lot but sometimes it still happens when the controller is = under load. I think to do with the inbound/outbound memory view on the = controller, i.e. maybe there is crosstalk between inbound and outbound = DMA? I can submit the patch I have but it=E2=80=99s not a 100% fix. >=20 > Did someone tell me this is *not* a problem at all on NetBSD/OpenBSD? >=20 > =E2=80=94 RHC. >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A935200-8545-4A86-80D5-3E0DEA156F56>