From owner-freebsd-arm@freebsd.org Fri Sep 4 19:48:04 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 18B4B3CDD98 for ; Fri, 4 Sep 2020 19:48:04 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wm1-x344.google.com (mail-wm1-x344.google.com [IPv6:2a00:1450:4864:20::344]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BjpBB5rf8z4X24 for ; Fri, 4 Sep 2020 19:48:02 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wm1-x344.google.com with SMTP id q9so7467393wmj.2 for ; Fri, 04 Sep 2020 12:48:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=p5zNZEJBPmflL8Kjfk80umJWDSXwjkM1dWT27XUJ9e4=; b=qBcQOwNpKxyTeVCzhq/nAeKFVjGchYVaoiQxQ/4H3kDwF4veIei64En35OcezLxXId P9Xe5UtZDu+LIcOmsw6zAsWP3k62T0x+N0yG/JsoPqVNVj2tCcPL5hE2OsbEcKqUf2rf toxwvqdxa/42golSoLIGcW+k5rpa7Z7PZ290dd4WDdB3XEc96Ym0m2vRCLkzvj3nP1XY bls7Ib304+Yff/VvxOfdMBDNdrt9vVp/63Tn+CCob8irMCkTuHPLSuIuO6ov2+LyNaY6 m3fFh4MHZk/3OHrLAnjZQQ0Vq9a/GVVga1qQKyyMAesIX2IligE53yEruZA3qetLAIoL Hhng== X-Gm-Message-State: AOAM531LqlL/1n5dlvELJFAimXaRS7FBSawK+8YP2s70nFcFP9NABEWq YqzNzAFOvL8Vg4GohUuufSc= X-Google-Smtp-Source: ABdhPJwxnOP8V8kVbxxTcWuRX+0TYqBFPV/tVK5tGqqy8iUr1bXlTMXjnQ3s4groYUc8O1ex/kriew== X-Received: by 2002:a7b:c7cd:: with SMTP id z13mr9145586wmk.160.1599248881241; Fri, 04 Sep 2020 12:48:01 -0700 (PDT) Received: from localhost.localdomain ([46.114.111.198]) by smtp.googlemail.com with ESMTPSA id 185sm5922156wma.18.2020.09.04.12.47.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Sep 2020 12:48:00 -0700 (PDT) From: Klaus Cucinauomo Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.0.3\)) Subject: Re: onboard wireless on rpi4 Date: Fri, 4 Sep 2020 21:47:58 +0200 References: <20200904134619.GB80905@bastion.zyxst.net> <69934262-D9D3-4986-849D-9E8221D1E387@kronometrix.org> <20200904142255.GC80905@bastion.zyxst.net> <5AF83D16-2432-4EA9-BC2F-373DA8BC3360@googlemail.com> <4306A90D-97B9-4DE9-A05A-A91B6F4A587F@yahoo.com> To: Mark Millard , freebsd-arm@freebsd.org, Hans Petter Selasky , Robert Crowston , myfreeweb In-Reply-To: <4306A90D-97B9-4DE9-A05A-A91B6F4A587F@yahoo.com> Message-Id: <1F513B3D-64F7-4391-8460-DBD5E68014FD@googlemail.com> X-Mailer: Apple Mail (2.3654.0.3) X-Rspamd-Queue-Id: 4BjpBB5rf8z4X24 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.61 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[googlemail.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; NEURAL_HAM_SHORT(-1.13)[-1.129]; FREEMAIL_TO(0.00)[yahoo.com,freebsd.org,selasky.org,protonmail.com,unrelenting.technology]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.985]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[46.114.111.198:received]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::344:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Sep 2020 19:48:04 -0000 Ah, thanks for making all those extended tests and reporting details ! I thought you=E2=80=99re talking about ACPI but the DMA-thing also = affects DeviceTree,=20 at least in NODEBUG- kernel, as it seems after your report. > Am 04.09.2020 um 21:19 schrieb Mark Millard : > I have not tried this kind of test under a DBG kernel. If you find the time, perhaps you could try it, thanks in advance !=E2=80=A6= . Well, USB/pcie related dma-things(rewriting half the inherited driver = stack, mentioned by ROBoCrow) are the specialty of fbsd-icon HPS :-) , so I also forward this = issue/discussion to him for the first=E2=80=A6. And 'myfreeweb' perhaps is also interested in ;-) ... maybe after 3 months I will switch on the RPi4 again :-) Ha Ha=20 Regards > Am 04.09.2020 um 21:19 schrieb Mark Millard : >=20 >=20 >=20 > On 2020-Sep-4, at 10:44, Klaus Cucinauomo = wrote: >>=20 >> Hi Mark, >=20 > Hello. >=20 >> as far as I remember(didn=E2=80=99t work the last weeks on RPI-stuff) >> the dma-thing only failed on GENERIC-NODEBUG (unexpected controller = detection loops) =E2=80=A6 >=20 > Unless trying to help track down a problem at the time, I use NODBG > kernels. So, for > 3072 MiB, I find that copying huge files and > diffing/cmp'ing the copies reports mismatches. (I tend to use > files larger than the RAM but that large has not been required.) > Note: I boot from and use USB3 SSD without a microsd card being > involved at any stage. >=20 > It is not obvious what the actual file contents are where the > differences show up. >=20 > I've tended to create and use tar's of build trees, created under > the 3072 MiB configuration to establish large files for such > tests. Tests under the 3072 MiB configuration have not failed > when I've tried such. >=20 > I have not tried this kind of test under a DBG kernel. >=20 > The last I heard about the PCIe DMA handling for > 3072 MiB was > on 2020-Jul-19 from Robert Crowston: >=20 > QUOTE > You are right that we are not handling the 3 GB DMA limit in the pcie = driver. Unfortunately, it did not seem easy to thread the appropriate = bus tag through without rewriting half the inherited driver stack, and = in my testing the USB driver always allocated its DMA buffers in the = lower 3 GB without being told. But obviously it is the wrong to rely on = luck, so I=E2=80=99ll have a think about it. > END QUOTE >=20 > I've not noticed anything go by that suggested to me that this > has been addressed. (But I could have just missed it.) >=20 >> But it worked on GENERIC and afaik Greg_unrelenting`s dma-fix isn=E2=80= =99t yet merged to 13-current=20 >> because of that unfixed issue=E2=80=A6 >> (but you can apply his patch and test)..it should work under GENERIC = without the 3GB-limit(4GB & 8GB-models)=20 >>=20 >> Klaus >>=20 >>> Am 04.09.2020 um 19:33 schrieb Mark Millard via freebsd-arm = : >>>>=20 >>>=20 >>> Has the mishandling of the DMA been fixed? I'm still back >>> at head -r363590 and it was not fixed as of then. I've >>> had to use the 3072 MiB limit in the uefi/ACPI selections >>> in order to have a reliable environment. >>>=20 >>=20 >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar)