Date: Wed, 12 Feb 2025 10:39:43 -0800 From: Mark Millard <marklmi@yahoo.com> To: Florian Smeets <flo@smeets.xyz> Cc: =?utf-8?Q?S=C3=B8ren_Schmidt?= <soren.schmidt@gmail.com>, freebsd-arm@freebsd.org, Nenhum_de_Nos <lojas@arroway.org> Subject: Re: Nanopi R5S and U-boot from Ports Message-ID: <06E04145-A74D-472E-B345-A594B0EC6BAE@yahoo.com> In-Reply-To: <bcb1f570-f353-4616-b3ee-e79a7148074d@smeets.xyz> References: <aa13b88f36d8b4f608093fe5e4d2ea84.squirrel@10.1.7.91> <20250211121727.290f4ddccf5aa4d901f681d7@bidouilliste.com> <d0ba5a92dd1c51077b6246dd77a53e62.squirrel@10.1.7.91> <C9AC9AB3-1048-423F-9293-75A7EDB41835@gmail.com> <bcb1f570-f353-4616-b3ee-e79a7148074d@smeets.xyz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 12, 2025, at 09:59, Florian Smeets <flo@smeets.xyz> wrote: > On 11.02.25 17:20, S=C3=B8ren Schmidt wrote: >> I use several of those boards and they work OK, granted with at = modified src tree=E2=80=A6 >=20 > Can we get what's needed for these boards committed to the tree? My understanding is that FreeBSD does not maintain any *.dts* sources or *.dtb binaries of itself. It uses what it considers upstream: For all but the RPi*'s: mainline Linux the source directory tree(s) for the *.dts* files are copied over. Those supported are built as part of FreeBSD building for the platform involved. For the RPi*'s binary files are grabbed via the sysutils/rpi-firmware port/package and those are used. The port Makefile controls which vintage it gets and normally it is an older vintage (rarely updated). The mainline Linux tracking does not really allow for using different vintages of mainline for different small arm boards. Also, any FreeBSD kernel update to track Device Tree changes is a separate effort that only happens at some point after discovering any incompatibilities with the pre-existing kernel code. Similar status for something new, like the RPi5 variations: the kernel has no expect support and any *.dtb is far from sufficient on its own. U-Boot is a separate issue but is also involved. To my knowledge, FreeBSD does not claim any support of a small arm board via the likes of EDK2, neither UEFI/ACPI nor UEFI/DeviceTree style. (Device Tree style need not track mainline Linux.) But there is a EDK2 port with flavors for a few contexts, even if FreeBSD makes no use of any of the flavors. > I'm also using an OrangePi5, I was able to get a stable/14 working = with patches gathered from https://personalbsd.org/images/download/. If the patches aren not based on tracking mainline Linux on the schedule FreeBSD ends up using for updates, it seems unlikely that FreeBSD will go that direction: no signficant, sustained deviation from the upstream context seems likely. =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?06E04145-A74D-472E-B345-A594B0EC6BAE>