Re: RPI 4/5 u-boot new port, is there any interest?
"Bjoern A. Zeeb" <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 4 Jun 2025, Klaus Küchemann wrote: > Thanks a lot , Evgenii !!!… > > In addition a link for you all to the u-boot-hacks for RPi5 ( including RP1-driver/ethernet(netboot)) : > > patch sources : https://github.com/xen-troops/u-boot/tree/rpi5-2024.04-xt The last I heard of this was: https://lore.kernel.org/u-boot/[email protected]/T/#m65db26132d42913410023dcd6c9051442941a007 I have a rebase of that for 2025.04[-rc3]; the single patch file I put into a local port in Feb still applies to the 2025.04. Need to go and see; had a few other minor changes. >> Am 04.06.2025 um 23:27 schrieb Evgenii Ivanov <[email protected]>: >> >> Hi, >> >> If anyone is interested in working on this, I've gathered up some notes/links which could be helpful: >> >> • Work by dfr enabling pcie/sd interface: https://github.com/dfr/freebsd-src/tree/rpi-5-pcie (requires a few more if statements to work with 15.0) That's interesting; hadn't kown about that one. >> • OpenBSD commit enabling rp1 child enumeration over device tree: https://github.com/openbsd/src/commit/2ee472d028ecbaf1d25a179e46dc4a0f63034131 (there is also a gpio driver for the rp1) >> • rp1 interrupt handling (GPL code): https://github.com/rsta2/circle/blob/master/lib/southbridge.cpp (there is also code for eth/usb/spi...) >> • Zephyr also appears to have some primitive support for the rpi5: https://docs.zephyrproject.org/latest/boards/raspberrypi/rpi_5/doc/index.html >> • pinctrl for rp1 gpio control via userspace in Linux (BSD license): https://github.com/raspberrypi/utils/blob/master/pinctrl/gpiochip_rp1.c >> • rpi4 baremetal gpu (MIT?): https://github.com/Random06457/rpi4-gpu-bare-metal-examples >> >> >> So far I've only managed to get the rp1 stub driver to enumerate over the child devices and attach them (causing a kernel panic...). I just grabbed mainline u-boot and compiled for rpi arm64, using the device tree blob from rpi-firmware repo. -- Bjoern A. Zeeb r15:7