|
|
|
|
|
by thom_nic
3036 days ago
|
|
I think "ecosystem" doesn't actually matter much (if "ecosystem" means maker/ tinkerer mindshare) for commercial applications. All you need is (1) kernel support for the chip including drivers e.g. for video/ peripherals, and (2) good userland support for aarch64. You can debootstrap a Debian rootfs that will work on any aarch64 chip. As mentioned elsewhere, it sounds like the H5 chip has good kernel support which covers (1.) Actually there's a (3), which is bootloader support. I don't know if the H3 typically uses u-boot or some other bootloader. What differs is what each chip actually supports. E.g the Pi/BCM2835 doesn't have onboard ethernet MAC/Phy. Neither Pi nor H3 have onboard CAN but maybe neither of those things matter. Point is these days most of the details of the chip are abstracted away; if you have good kernel support there's not a lot to worry about. |
|
This does not mean that other boards won't work or won't have a place, but are highly unlikely to cover the same global space the Pi does.