Date: Sun, 9 Feb 2025 22:40:01 +0100 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Mark Millard <marklmi@yahoo.com>, freebsd-arm@freebsd.org Subject: Re: fdt based rework Re: Raspbery Pi support (release notes/wiki page) update? Message-ID: <5197CCFA-114C-4D7B-A7E5-D36C383610E4@googlemail.com> In-Reply-To: <E164C348-1E2B-4546-8DE9-9721FB128E11@yahoo.com> References: <668r286o-584q-616o-5nq3-0233r3259qsr@yvfgf.mnoonqbm.arg> <0B39AEF3-27E8-4715-9FA4-6B95D8AFFB3C@googlemail.com> <DB4B0655-E981-474F-989F-EAEAE820268B@yahoo.com> <F9CF948E-2591-4A97-8225-3563268593EA@googlemail.com> <E164C348-1E2B-4546-8DE9-9721FB128E11@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As you saw, the rp1 driver is compiled into the specific U-Boot version = that I used and the devicetree is handed over to the fbsd-kernel...=20 Or let's say: a hacked u-boot could currently be considered operational = (except currently USB)...=20 but of course freebsd is not ready for use yet... I'm afraid we need an rp1.c driver... The original is available here: https://github.com/raspberrypi/linux/blob/rpi-6.6.y/drivers/mfd/rp1.c but as long as no fbsd developer comes forward who wants/can work on it, = we don't need to talk about it any further or we have to do it = ourselves.. but huh, not that easy and not for everyone Regards K. > Am 09.02.2025 um 18:18 schrieb Mark Millard <marklmi@yahoo.com>: > =E2=80=A6 > .. >=20 > FYI: The U-Boot fdt print output is sufficient to essentially > reproduce the live DTB with: It is a complete source and has > vastly bigger output to capture. With a dtc that follows the > same conventions, it can be compiled to produce such a .dtb > file. > =E2=80=A6.. ... >=20 > =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?5197CCFA-114C-4D7B-A7E5-D36C383610E4>