He/Him | Hu/En/some Jp | ASD | Bi | C/C++/D/C#/Java

  • 3 Posts
  • 21 Comments
Joined 4 months ago
cake
Cake day: March 16th, 2024

help-circle













  • SBCs already had a few issues.

    • ARM Mali driver absence from most distros.
    • Compute modules are now standard with 5V rails, making battery operation clunkier, because data centers.
    • And for a very long time, the 4x MIPI buses were hidden on Raspberry Pis, locking users out from most screens to hack to them.
    • MIPI itself relies on custom “ignition” codes (don’t know what the actual architectural names were for them), that can in theory, be so personalized each individual display and camera could be locked to the SoCs to the point the display itself would need the “ignition” code.

    My speculation: I think a lot of these were made to hinder making actual portable devices a lot more clunkier than they need to be. For displays, many use the HDMI port instead. Even official stuff has its own clunk, like the Pi 400 using USB specifically for keyboard, all while an I2C or SPI would have been more than sufficient. The GPIOs of those SoCs were made for this kind of purpose.


  • Raxda. Profit-oriented from the get-go, but has excellent support. You might still need to fiddle with the official Mali drivers though (tougher than the Linux NVidia drivers).

    Otherwise, if you just need a quick solution for let’s say, a NAS built around USB storage, you can just use anything as long as it has proper support for Armbian (Chinese manufacturer’s own Linux distros sometimes have spyware and stuff that make one of the cores run 100% all the time, also no Mali drivers).