Date: Thu, 6 Feb 2025 10:00:22 -0800 From: Mark Millard <marklmi@yahoo.com> To: Tomek CEDRO <tomek@cedro.info> Cc: Mario Marietto <marietto2008@gmail.com>, Marco Devesas Campos <devesas.campos@gmail.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Raimbow screen installing / booting FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img on the raspberry pi zero 2w Message-ID: <AE01A763-CD87-4BD8-B12D-C1DD27060FDF@yahoo.com> In-Reply-To: <CAFYkXjmw8odDrJQvnjcyE4nN4NgqZdGDxi4pOsRGTcz8hQspSA@mail.gmail.com> References: <CA%2B1FSig9coHK-k1dNaong=rOSGGNW170gf%2B-13S7J3syORU_DA@mail.gmail.com> <5E12B96C-20A2-4FFB-A31E-00B259450707@gmail.com> <CA%2B1FSih6jzcy7po3Ux_nSfN6UF%2BzwBfp-iM1vzVgpPObnN3ukA@mail.gmail.com> <CA%2B1FSih9TauSj4YteGij2BFO7C4irxDE=RFoBtnKK6-EMzwV5Q@mail.gmail.com> <FEDBC538-E7B2-49CA-AD27-3641A1BF6E56@gmail.com> <D1B3EA48-16B7-4E9A-940E-A88B0E75F1DA@yahoo.com> <CA%2B1FSijy9OSoaMi%2BLfeiD4zqj=_0OkYcM3OrMEwGZqxrV7X4pg@mail.gmail.com> <E9F79146-A973-4AC0-BFFB-28EF15FF9AE7@yahoo.com> <CAFYkXjkdaD8n6rYUrv0kdMwXkqA%2BENu0FAP-n8d7fydRKzwaYw@mail.gmail.com> <1EC055A5-EA4C-4857-BFC6-9C0C29573ED2@yahoo.com> <CAFYkXjmw8odDrJQvnjcyE4nN4NgqZdGDxi4pOsRGTcz8hQspSA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 6, 2025, at 09:34, Tomek CEDRO <tomek@cedro.info> wrote:
> On Thu, Feb 6, 2025 at 3:04=E2=80=AFPM Mark Millard =
<marklmi@yahoo.com> wrote:
>> On Feb 5, 2025, at 23:51, Tomek CEDRO <tomek@cedro.info> wrote:
>>> Yup, I can confirm rpi-firmware/bcm2710-rpi-zero-2-w.dtb works with
>>> FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img :-)
>>=20
>> FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img contains the
>> u-boot from:
>>=20
>> /usr/ports/sysutils/u-boot-rpi-arm64
>>=20
>> and, so, also contains and should be used with a copy of:
>>=20
>> /usr/local/share/rpi-firmware/config_arm64.txt
>>=20
>> as config.txt :
>>=20
>> # grep -rA1 config_arm64 /usr/src/release/
>> /usr/src/release/arm64/RPI.conf: chroot ${CHROOTDIR} cp -p =
${DTB_DIR}/config_arm64.txt \
>> /usr/src/release/arm64/RPI.conf- ${FATMOUNT}/config.txt
>>=20
>> /usr/local/share/rpi-firmware/config_rpi3.txt is for when:
>>=20
>> /usr/ports/sysutils/u-boot-rpi3
>>=20
>> is is use instead. No modern snapshot or release uses that:
>>=20
>>> One thing to mention too is config_rpi3.txt -> config.txt (not
>>> config_rpi_0_w.txt) :-)
>>=20
>> config_rpi3.txt is likely not fully appropriate and
>> config_arm64.txt is likely what should be used. But
>> it was already in place as config.txt in:
>>=20
>> FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img
>>=20
>> FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img is for
>> all the aarch64 / arm64 RPi*'s that FreeBSD happens
>> to support. (RPi5's not being supported as stands.)
>=20
> ACK! I confirm that config_arm64.txt -> config.txt works on rPI-0-2W
> and should remember its the default :-)
>=20
> % diff -u config_rpi3.txt config_arm64.txt
> --- config_rpi3.txt 2025-02-06 08:21:34.000000000 +0100
> +++ config_arm64.txt 2025-02-06 08:21:34.000000000 +0100
> @@ -1,7 +1,11 @@
> +[all]
> arm_64bit=3D1
> dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don
> dtoverlay=3Dmmc
> -dtoverlay=3Dpwm
> dtoverlay=3Ddisable-bt
> device_tree_address=3D0x4000
> kernel=3Du-boot.bin
> +
> +[pi4]
> +hdmi_safe=3D1
> +armstub=3Darmstub8-gic.bin
>=20
> Thank you Mark! :-)
> Tomek
>=20
> ps/2: Is there a video console so I can for instance run mpv / sdl2
> applications without xorg / wayland as on amd64? What driver? :-)
I have no clue about the RPi-0-2W for that. My use is rare and
very temporary for any setup and use of any video on any RPi* ,
no mpv or sd12 use involved.
Side note:
For the [pi4]: It is common to delete, comment out, or
instead assign 0 for the hdmi_safe assignment. (Not that such
matters in your context.)
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AE01A763-CD87-4BD8-B12D-C1DD27060FDF>