[ashton314]

Wait, so does this mean FreeBSD will work better on a raspberry pi without having to hack on your config files just to get it to recognize all available RAM? I’ve got FreeBSD running on a rpi4—took some doing. It would be nice to just slap an image on it and have it work.

[maxioatic]

> We will also be suggesting one or more low-cost reference platforms for FreeBSD/arm64.

A boy can dream this would be the Pi.

[kevans91]

This is pretty unlikely, unfortunately. We're generally looking out for a Pi maintainer because it doesn't really have one -- it's not the most desirable platform to hack on, from a developer POV.

[maxioatic]

Hmm, bummer. Curious as to why it's not that desirable, and is there something else you would rather use?

[kevans91]

Speaking from personal experience, it's an absolute pain -- they're already an odd duck (w.r.t. booting, for instance), add on that the documentation is incredibly lacking compared to competitors and you've got a platform that's not too appetizing.

Allwinner and Rockchip tend to be pretty solid, as far as SoC go; start here: https://wiki.freebsd.org/arm

[Decabytes]

I’m curious about what documentation is lacking? I’ve been collecting technical documentation on the RPI4 because I’m trying to understand the platform well, and maybe I’ve come across something that can help?

[kevans91]

Pretty much anything that would need to come from Broadcom, really

The docs that most recently bit us are pcie/ethernet on the RPi4; I got in touch with Broadcom, who is now in a multi-year effort to figure out how to disperse usable docs (under NDA?) to the broader community. I lost faith after 9ish months of poking and getting back "oh, you know how it is" in response.

[Klwohu]

Are you saying this as a FreeBSD core development team member?

[kevans91]

I speak as a FreeBSD developer who has dabbled with RPi, having tested and shuffled in a lot of the initial RPi4 patches and did some not-insignificant hacking to get a single RPi image to actually support RPi3 + RPi4.