From nobody Fri Jan 06 22:35:05 2023 X-Original-To: uboot@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NpdSp2wgBz2qvQc for ; Fri, 6 Jan 2023 22:35:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NpdSp1vL2z430q for ; Fri, 6 Jan 2023 22:35:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1673044506; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=nbTDaDwF9TQxMGMBn0ALnaVLMeOC72U10Lsrfavu1pE=; b=L7n0m06s/1ZD78Q1FDnMGzS5h8+RGFZ/tUYkKSnl0QtgQhFUd8Bpixhz3RKAGna9MXiDbb seq2sGAF9xT1IdGe4hds+LjLi6q6DD6wuU+11z2agLrO5hr9PSXnK09gkIckBYl41JZFUa Dm4UzXedDWVjOOrap+2hRthAVgmdnPLo+udm+VgKC8dBbeRhnKmDRSZxTnHdLzOycfOqA0 6+eNywf1LUGpmGEvR6ROSa6eKJCk2Haj6Wp/pGbE0i5oWjTAH0n2x5ctm8Cjo10mGZjR86 EsuaGCnR5OeQSCM8y8n3Syz9Wv76RgNkvNbZMj1DW0jBJBV468xaC2mRXxc02w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1673044506; a=rsa-sha256; cv=none; b=rnTOl10NRTDo9uNYck9LBMirJA19vVYE9VOBk4ANGiZRkbKTx1GNvnAVmujepsNhi5aq3k +wJiUx0OOMqgj8i1MB05mwCJACBWDmCQf72g8FvGGhXPQQ2XXUEPkUINwF02Ltc+fz0ZiU 2A32aBpasLltQTVOTaVBaO5hOOG8G1Tdt7LBhIBEZXeus1RHaEhExc57KUvTZGwCsk5BXp o02iGMiVFytaW05zO/c3QdrzZsOTjrAvHrkducHFXuoAusXiD7UrAhT1odhE1sSmygvo/K cqlcAnsU5Fbr8NOtN8Y5/1gCAMFZBJlQnq83qgLpvYXsnvXtGs2nTdK7qVuiRg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4NpdSp0xkKzmSZ for ; Fri, 6 Jan 2023 22:35:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 306MZ6iG079076 for ; Fri, 6 Jan 2023 22:35:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 306MZ6Qe079075 for uboot@FreeBSD.org; Fri, 6 Jan 2023 22:35:06 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: uboot@FreeBSD.org Subject: [Bug 261147] sysutils/rpi-firmware/ RPI Zero 2 W boot files Date: Fri, 06 Jan 2023 22:35:05 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-uboot List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-uboot@freebsd.org X-BeenThere: freebsd-uboot@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261147 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #8 from Mark Millard --- (In reply to J=C3=BCrgen Weber from comment #7) I expect that you likely need to get a serial console going and to capture and report its output in order to provide enough context to be likely to get help. Going in another direction . . . One possible contribution is being sure that bcm_dma has been initialized in an earlier pass in order to avoid used-before-defined issues that happens in some vintages of some .dtb files for the kernel as-it is now. main [so: 14] has _devclass useage removed so main vs. stable/13 and the like need separate patches to make bcm_dma initialize in an earlier pass on the fdt. # git -C /usr/main-src/ diff sys/arm/broadcom/bcm2835/bcm2835_dma.c diff --git a/sys/arm/broadcom/bcm2835/bcm2835_dma.c b/sys/arm/broadcom/bcm2835/bcm2835_dma.c index 5f9ecb0b7981..d901447df1e9 100644 --- a/sys/arm/broadcom/bcm2835/bcm2835_dma.c +++ b/sys/arm/broadcom/bcm2835/bcm2835_dma.c @@ -764,5 +764,6 @@ static driver_t bcm_dma_driver =3D { sizeof(struct bcm_dma_softc), }; -DRIVER_MODULE(bcm_dma, simplebus, bcm_dma_driver, 0, 0); +EARLY_DRIVER_MODULE(bcm_dma, simplebus, bcm_dma_driver, 0, 0, + BUS_PASS_INTERRUPT + BUS_PASS_ORDER_LATE); MODULE_VERSION(bcm_dma, 1); # git -C /usr/13S-src/ diff sys/arm/broadcom/bcm2835/bcm2835_dma.c diff --git a/sys/arm/broadcom/bcm2835/bcm2835_dma.c b/sys/arm/broadcom/bcm2835/bcm2835_dma.c index cab8639bb607..6d521d6dcace 100644 --- a/sys/arm/broadcom/bcm2835/bcm2835_dma.c +++ b/sys/arm/broadcom/bcm2835/bcm2835_dma.c @@ -766,5 +766,6 @@ static driver_t bcm_dma_driver =3D { static devclass_t bcm_dma_devclass; -DRIVER_MODULE(bcm_dma, simplebus, bcm_dma_driver, bcm_dma_devclass, 0, 0); +EARLY_DRIVER_MODULE(bcm_dma, simplebus, bcm_dma_driver, bcm_dma_devclass, + 0, 0, BUS_PASS_INTERRUPT + BUS_PASS_ORDER_LATE); MODULE_VERSION(bcm_dma, 1); I am only now starting a round of updates that would apply such patching to all the RPi*'s that I have access to. (Not much variety in type, however: all RPi4B's, either 4 GiByte Rev 1.1's or 8 GiByte Rev 1.4's/1.5's. The Rev 1.5 is also a "C0T" part instead of a "B0T" part. But for what I've tried so far, I've been able to boot the more recent RPi* firmware vintages that I've tried based on bcm_dma having been initiated before it was used. Note: It took me months to discover EARLY_DRIVER_MODULE and that it was appropriate for needing a resource initialized earlier for fdt based booting. I can not make any claim of expertise in the area, just of experimentation. So someone knowledgable would need to judge how appropriate the details are as the technique to deal with the kind of problem it avoids. --=20 You are receiving this mail because: You are on the CC list for the bug.=