nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq05gxtz00vfxzdela6xrhyvtqxmaxqz65d9hws3d56e72trqgcmvsxk52hs Cool. Would love to know what the bit is and how to finagle it.
Oh Good News. My ...
@nprofile1q... I can't get into too much detail regarding the bit. I'm more inclined to work on real solutions to these problems than I am to pander to those working on projects that don't really solve them (ie coreboot, etc).
The real solution to the x86 problem (AMD has something equivalent to the ME and is likely also backdoor'd) is moving away from x86. However it's easier said than done as most SoCs you could build off incorporate other problematic parts. Wifi is always an issue for any device that incorporates wifi. Sure, you can get around this, but I'm more interested in real solutions. Not hacks.
The real solution is building something off an Allwinner SoC like the R40 or A20. Those are older SoCs with I think a max of 2GB of ram. The current best solution I think is going to be one of the Rockchip SoCs.
I've built images for a device my company is working on that is geared at being a solution to automatically deploy a self-hosted mail server. What is near about it is the images are built without any proprietary bits. The ARM trusted firmware is typically a blob, but it's possible to build it from sources. It's just that no one does and the crazy part is everyone is pulling this blob from some sketchy Chinese gdrive equivalent. There is also a DRM component for the video, but the images I built are for a device that doesn't have an HDMI video out and I haven't had a chance to verify whether or not the HDMI video out with I think one of the Mali graphics components these SoCs are typically paired with will work without it. I think the answer is there is some minimal amount of accelerated graphics and video acceleration and the proprietary DRM component is related to digital restrictions on the HDMI side. So a PC w 32GB ram is possible.
The real solution to the x86 problem (AMD has something equivalent to the ME and is likely also backdoor'd) is moving away from x86. However it's easier said than done as most SoCs you could build off incorporate other problematic parts. Wifi is always an issue for any device that incorporates wifi. Sure, you can get around this, but I'm more interested in real solutions. Not hacks.
The real solution is building something off an Allwinner SoC like the R40 or A20. Those are older SoCs with I think a max of 2GB of ram. The current best solution I think is going to be one of the Rockchip SoCs.
I've built images for a device my company is working on that is geared at being a solution to automatically deploy a self-hosted mail server. What is near about it is the images are built without any proprietary bits. The ARM trusted firmware is typically a blob, but it's possible to build it from sources. It's just that no one does and the crazy part is everyone is pulling this blob from some sketchy Chinese gdrive equivalent. There is also a DRM component for the video, but the images I built are for a device that doesn't have an HDMI video out and I haven't had a chance to verify whether or not the HDMI video out with I think one of the Mali graphics components these SoCs are typically paired with will work without it. I think the answer is there is some minimal amount of accelerated graphics and video acceleration and the proprietary DRM component is related to digital restrictions on the HDMI side. So a PC w 32GB ram is possible.
1