4 ms·
The flipside is-- if you have a 1GB pi, you're going to be wasting a whole lot of RAM on wider pointers, and you may be more constrained by RAM than CPU through
by mlyle 7y ago
The flipside is-- if you have a 1GB pi, you're going to be wasting a whole lot of RAM on wider pointers, and you may be more constrained by RAM than CPU throughput.
(Also, 64 bit Pi is not nearly as well supported as 32 bit currently. Does hardware GL work yet? What about if you're going to do MIPI, etc?) IMO it's worth waiting for a little more maturity.
- DagAgren 7y agoHas nobody tried to implement an aarch64 equivalent of the "x32" ABI? That is, using the 64-bit instruction set but keeping pointers 32 bits long?
- louwrentius 7y agoI have not used or had a need for hardware GL. Don't even know what MIPI is. I use it as very cheap bare metal. Still plan to use 3 of them as Ceph monitors.
- guug 7y agoSounds like you're using them as servers. Doesn't the lack of ECC worry you?
- mlyle 7y agoNot everything needs ECC memory. Ceph monitors aren't in the data path and Paxos is robust against byzantine failure, so...
- unwind 7y agoIt used to be Mobile Industry Processor Interface [1] but no longer is used as an acronym. High-speed serial links for driving displays and cameras in cell phones, originally. Proprietary. [1] https://en.m.wikipedia.org/wiki/MIPI_Alliance https://en.m.wikipedia.org/wiki/MIPI_Alliance