From nobody Sun Aug 13 06:11:59 2023 X-Original-To: freebsd-arm@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 4RNnHS3w9Pz4q3NT for ; Sun, 13 Aug 2023 06:12:04 +0000 (UTC) (envelope-from titus@edc.ro) Received: from eatlas.ro (eatlas.ro [86.126.82.18]) (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 (2048 bits) client-digest SHA256) (Client CN "eatlas.ro", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RNnHR6vx7z4DxP for ; Sun, 13 Aug 2023 06:12:03 +0000 (UTC) (envelope-from titus@edc.ro) Authentication-Results: mx1.freebsd.org; none Received: from mail.edc.ro ([10.1.4.58]) by eatlas.ro (8.16.1/8.16.1) with ESMTPS id 37D6BxDd021712 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Sun, 13 Aug 2023 09:12:00 +0300 (EEST) (envelope-from titus@edc.ro) Received: from [192.168.1.9] (86-120-200-242.rdsnet.ro [86.120.200.242] (may be forged)) (authenticated bits=0) by mail.edc.ro (8.16.1/8.16.1) with ESMTPSA id 37D6BwF6092386 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 13 Aug 2023 09:11:58 +0300 (EEST) (envelope-from titus@edc.ro) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=edc.ro; s=mail; t=1691907119; bh=BeKvdduCF+epGP7+W9WM35zDaqyTvfxkfXJQBnXa64Y=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=graXxoyJdHvPMJeUONPLeA3blEyPQYNA1oD9npOXDFsSos99Arnb+/cDWC18oF6VX K3wS4sQRN/ucfuwXjC+a80wblmsW3mLkWbvhXHQatqfmZPwBkDgUFnHV03L7z6bA9t FQXNTHA232oS7xKqajSlPH4wlohOspfaIggOflIo= Content-Type: text/plain; charset=utf-8 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\)) Subject: Re: ALPHA1 on Raspberry Pi 3B+ [added: and RPi4B] From: titus In-Reply-To: Date: Sun, 13 Aug 2023 09:11:59 +0300 Cc: Mike Karels , freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <1C94FEAF-C616-498F-8562-2E99CF12417D@edc.ro> References: To: Mark Millard X-Mailer: Apple Mail (2.3445.104.21) X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ns.edc.ro X-Rspamd-Queue-Id: 4RNnHR6vx7z4DxP X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8708, ipnet:86.120.0.0/13, country:RO] the failed devices are all linked to raspberrypi,bcm2835-firmware (gpio, cpufreq_dt,=E2=80=A6) which does not see to be probed / attached check fdt ls at the loader prompt and ofwdump -a=20 and boot -v and nm /boot/kernel/kernel|grep bcm2835_firmware_get_revision > On 13 Aug 2023, at 07:25, Mark Millard wrote: >=20 > On Aug 12, 2023, at 17:42, Mike Karels wrote: >=20 >> I booted 14.0-ALPHA1 on a Raspberry Pi 3B+. It boots and runs, but = there >> are some rough edges that probably indicate things that are broken. = During >> the boot, there are 56 occurrences of this sequence: >>=20 >> clk_fixed2: disabled on ofwbus0 >> clk_fixed2: Cannot FDT parameters. >> device_attach: clk_fixed2 attach returned 6 >=20 > The large count is from a small number of examples. Each > internal scan repeats the messages for each example, > unless eventually found. I learned this when I had > something being looked for too early, before the > definition was added to match up with. Everything worked > because of the retries eventually finding things after > they had been added, but it produced lots of messages > first. But, in that case, there was material to find. >=20 > The RPi4B's get clk_fixed4's instead, with a similar > overall count. For the RPi4B the cause is the > "fixed-clock" material below (from a diff of .dts > files produced from the .dtb files): >=20 > - cam1_reg { > + cam0_clk { >=20 > + #clock-cells =3D <0x0>; > + compatible =3D "fixed-clock"; > + status =3D "disabled"; > + }; > + cam0_regulator { > + > compatible =3D "regulator-fixed"; > enable-active-high; > - gpio =3D <0xa 0x5 0x0>; > - regulator-name =3D "cam1-reg"; > + regulator-name =3D "cam0-reg"; > status =3D "disabled"; > }; > + cam1_clk { > + > + #clock-cells =3D <0x0>; > + compatible =3D "fixed-clock"; > + status =3D "disabled"; > + }; > + cam1_regulator { > + > + compatible =3D "regulator-fixed"; > + enable-active-high; > + gpio =3D <0xb 0x5 0x0>; > + regulator-name =3D "cam1-reg"; > + status =3D "okay"; > + }; >=20 > I doubt that cam0_clk and cam1_clk are ever added to later > find, as stands, making every scan report the 2 fixed-clock > references each time. >=20 > This is something that I reported on on the lists back on > 2022-Apr-30. But it was mixed with a crash report that > turned out to be a separate issue (and was fixed some time > ago). >=20 > It would be possible to decompile the .dtb used for RPi3B+'s > to see if cam?_clk fixed-clock's are present. >=20 >> Two other failures: >>=20 >> bcm2835_cpufreq0: on cpu0 >> bcm2835_cpufreq0: Unable to find firmware device >> device_attach: bcm2835_cpufreq0 attach returned 6 >> gpioled0: on ofwbus0 >> gpioled0: failed to map pin >=20 > Those are more than noise messages. >=20 >> The red LED that's on when the system is halted stays on after boot; = not >> sure if that's related to the last item. >>=20 >> Looks like the kernel needs adjustments to correspond with the new = DTB. >>=20 >> I'll append the full dmesg.boot. > . . . >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com >=20 >=20