From the link: "Note: The inbuilt WiFi chip is not natively supported by FreeBSD, so you will need to (temporarily) use a USB WiFi or Ethernet dongle, or (as I will explain) copy some files from a different system to the Macbook. You could also just transplant a different chip into the system."
You say "works perfectly". I do not think it means what you think it means.
To be fair, Linux also has trouble with the Broadcom chip, the driver needs to be installed as a separate step on most distros.
> Broadcom
Here's the real problem.
It's sad how a company that spawned the raspberry pi in earlier times got so evil so quickly.
Broadcom (and to a lesser extent, Realtek) devices had always been anywhere between hit-or-miss and completely unworkable on Linux, LONG before Raspberry Pi came around.
My experience too. Sometimes I did manage to eventually get their cards working under Linux after pulling some proprietary firmware blobs.
Every Raspberry Pi ships with a closed source OS, ThreadX, that boots Linux, BTW.
It's MIT licensed now, which isn't particularly useful when it comes to Pi (there's some Broadcom crap in that boot loader so it won't be open sourced) but otherwise is kind of interesting.
https://github.com/eclipse-threadx
I imagine that is because modern Broadcom is a different Broadcom, Avago bought and took the name in 2016.
I think the intersection between BSD users and people who will buy a dongle or use Ethernet is a perfect circle.
> You say "works perfectly". I do not think it means what you think it means.
Copying some files from a different machine is not that burdensome. The point is, it works.
By that logic, every piece of software ever made can be said to work perfectly in every situation, because there is always some amount of additional work which could be done to make up for its native deficiencies.