> >>> Good day, > >>> will Fedora 30 support Raspberry Pi 4, or we must wait to Fedora 31? > >> a short statement from myself as the BCM2835 maintainer. The sources has > >> been published yesterday. The BCM2835 feature window for Linux 5.3 is > >> closed since 3 weeks. So the first kernel with minimal RPi 4 support > >> could be 5.4. > > Where is the upstream branches for 5.4 been published, from when I > > pulled from the raspberrypi github sources late last night I didn't > > see anything specific to the rpi4 I could see in any of the branches. > > as far as i know there isn't any upstream branch. Some of the RPi 4 > stuff has been prepared for upstream (usually BCM2711 = downstream, > BCM2838 = upstream), but are buried in the rpi-4.19 branch. > > Looks at this for example: > > https://github.com/raspberrypi/linux/commits?author=pelwell > > But there are also lot of hacks. Currently the biggest part on Kernel > side is the PCIe driver which isn't upstreamed yet. Another problem is > that there is no U-Boot support yet. I figured as much, I had looked at the 4.19.y branch as I figured that's where the initial bits would be but I hadn't seen anything that stood out :-/ I was looking through the DT compatible strings from bcm2711-rpi-4-b.dtb and worked out the issues with the PCIe issue, I figured there was either a new driver or enablement to one of the other broadcom drivers, most of the rest looked like fairly generic Arm IP or exisiting broadcom bits so my guess would there would be DT plus probably some enablement bits for the new SoC to find. > Without a real datasheet with register documentation this isn't fun ... For you or the wider community? Peter _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
