No datasheet for the SoC either. Again.
There are vastly better SBCs out there.
No datasheet for the SoC either. Again.
There are vastly better SBCs out there.
Plus, the Pi 4 will have something approaching mainline kernel support and a large community of people working on it.
The RPi3 has in fact mainline support, but is not "fully compatible" (at least, in the x86 sense). I guess this will be the case for the RPi 4 also.
This is a shame, since any ARM board has essentially an expiry date. For this reason, my next board will be an x86 SBC (the "famous one"), however, it costs considerably more.
Which ones would you recommend for this price?
Can you provide some examples please?
Always keen to try out any alternatives
https://www.friendlyarm.com/index.php?route=product/product&...
Has an eight-core 1.4GHz CPU, and is otherwise mostly comparable to the new Pi: 1G RAM, 1Gb ethernet. Has an SD card slot and no built-in storage.
The RPi has such a big community that I imagine performance and optimisation will quickly surpass other chips, eg. Rockchip RK3399 [1] (2xA72 and 4xA53) and will probably end up on par with an Amlogic S922x [2](4xA73 and 2xA53).
[1] http://rockchip.wikidot.com/rk3399 [2] https://www.cnx-software.com/2019/02/01/amlogic-s922x-benchm...
To get the full performance out of the RPi, you are going to need a beefy heatsink or it will thermal throttle very quickly.
But yeah, perhaps it's better to have a lot of small cores for a cluster.
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc....
Edit: Ouch if this turns out to be true... https://www.raspberrypi.org/forums/viewtopic.php?t=243410
Edit 2: Ah, also RPi3B and 3B+ didn't have those extensions. Oh well.
Edit 3: Just tested my bog standard RPi3B+ running Raspbian. It could do "openssl speed -elapsed aes-256-cbc" 43 MB/s AES-256-CBC. Tried also with "-multi 4" and it resulted 144 MB/s using all 4 cores. So perhaps RPi4 will be fast enough with CPU only crypto... would still love to have HW assist.
Edit 4: RPi4 running 32-bit OS can do about 65 MB/s per core aes-256-cbc. 85 MB/s per core for aes-128-cbc. So by using two CPU cores for encryption (+ heatsink + fan :-)) 1 Gbps ethernet can be saturated.
I think it would be pretty tricky to get LUKS to use it, though. At least writing a kernel module, but most likely LUKS patch would be required. You'd probably have to choose between 3D acceleration and full disk encryption.
Looks like VideoCore VI is getting some compute shader support:
https://gitlab.freedesktop.org/anholt/mesa/tree/v3d-cs/src/g...
In fact, being slow can be considered a feature in this scenario.
https://github.com/ThomasKaiser/sbc-bench/blob/master/Result...
See PineH64 for example.
Hmm, anyone know if the VideoCore VI would be any good for crypto?
We'll see.
[0]: https://www.phoronix.com/scan.php?page=news_item&px=Broadcom...
So if you need to go through/process gigabytes of data on encrypted drive, having to do encryption in SW will slow you down massively, especially if you also need to process the retrieved data somehow.
Shipping from them used to be horrendously expensive, but I'm happy to notice that changed. Thank you.