no wifi, no sound, not adapted and slow C compiler, unreliable pkg software, heavily wayland in there, no webbrowser on Xorg (just links works).
The resulting executable turned up in /usr/local/bin/chrome, which was
slightly surprising; the port's name is chromium, after all.... It seems
to run, but is too slow to play Youtube videos smoothly. For static pages
it seems fine.
On the ARM mailing list (Dec, 2018) Bob Prohaska successfully compiled and used Chromium
FreeBSD on RPI3b+ is so great !!!
I'm pretty sure it's a broadcom deficiency. The documentation for the BCM2837 processor (that includes the WiFi) isn't freely accessible.FreeBSD'd deficit in that area is more and more glaring by the day.
I totally disagree. What you call a tinker board others would call an embedded computer.Frankly the time when wifi was luxury should simply be over. Especially for a tinker device like the raspberry it should be a hard requirement. FreeBSD'd deficit in that area is more and more glaring by the day.
The same argument could be made about every peripheral. On a $35 device the wifi should be part of the basis. You don't have to activate it. But it is there when ypou need it.I don't want embedded WiFi chip on my embedded computer.
I'm pretty sure it's a broadcom deficiency. The documentation for the BCM2837 processor (that includes the WiFi) isn't freely accessible.
It does not matter to have wifi.But it has no wifi.
Frankly the time when wifi was luxury should simply be over. Especially for a tinker device like the raspberry it should be a hard requirement. FreeBSD'd deficit in that area is more and more glaring by the day.
I don't know the details as far as FreeBSD goes, but SDIO isn't free nor open-source. At the very least in the past, to be allowed to add a SDIO stack to FreeBSD there's more legal than technical stuff.The issue is still (for something like twelve years now) the darned SDIO driver.
I still need to stress that I don't know the details about the FreeBSD implementation/work going on nor any inhibitations. I just want to draw attention to the fact that things aren't always what they seem.SD and SDIO card IP is protected via patents, trade secrets, and copyrights. If you follow the license terms, keep the IP confidential, and make your payments to the right parties, then you can legally ship an SD/SDIO stack.
I don't know the details as far as FreeBSD goes, but SDIO isn't free nor open-source. At the very least in the past, to be allowed to add a SDIO stack to FreeBSD there's more legal than technical stuff.
Quote from this page (2005)
I still need to stress that I don't know the details about the FreeBSD implementation/work going on nor any inhibitations. I just want to draw attention to the fact that things aren't always what they seem.
Linux is generally supported by manufacturers themselves while FreeBSD rarely is. Writing FreeBSD drivers based on a Linux driver isn't that easy though, it's not like code is documentation.
However, you're always free to write a SDIO implementation and a broadcom driver to go with your own private copy of FreeBSD. It'll also give you some insight in what it takes to write an actual device driver.
More knowledge is always useful.
Much open-source stuff is written by people who want to use it themselves but can't find a good alternative. It's always a good thing to keep that in mind.no one would try to make a driver for broadcom 4BSD. There is little points to do so.
The same argument could be made about every peripheral. On a $35 device the wifi should be part of the basis. You don't have to activate it. But it is there when ypou need it.
Dear friggin lord! They did not even start with the bc driver. The issue is still (for something like twelve years now) the darned SDIO driver.
And I am sick and tired of "broadcom does not give dox". There have been Linux drivers for all this for many years now, for anyone to read.
Linux has an awful networking layer, it is slow, hanging while compiling,... and it runs slower compared bsd in overall assessment. Furthermore, softs on it have issues with networking.I think the key here is to abandon FreeBSD for Pi3B and use Linux. I know Devuan works and Xbian if you want a media center. FreeBSD just isn't interested (for good or bad) in these embedded & maker systems; it's the realm of Linux, they dominate and have the best support and/or best chance of support.
You're just giving yourself heartburn waiting for it to change.
I ported kodi on the rpi2 and it works just fine as a multimedia center. The rpi3 is, alas, missing the vchiq driver.I get it, you're a supporter of FreeBSD. I am too. But, I know when it's worth using and when it's not. On the Raspberry Pi 2 and up to 3B+, it's ok as a headless server, but with a GUI and something like audio or tv/media it's not suitable. Linux is the only choice, unless you like waiting for years for supported infrastructure.
Raspbian is their own OS and it's Linux, not FreeBSD based. That ought tell you something.
First the Phone = Nokia OS,I get it, you're a supporter of FreeBSD. I am too. But, I know when it's worth using and when it's not. On the Raspberry Pi 2 and up to 3B+, it's ok as a headless server, but with a GUI and something like audio or tv/media it's not suitable. Linux is the only choice, unless you like waiting for years for supported infrastructure.
Raspbian is their own OS and it's Linux, not FreeBSD based. That ought tell you something.