On Mon, 2023-05-08 at 12:15 +0100, James Addison wrote: > I'd like to understand what is the approach that provides the most > compatibility and free software support with the fewest moving parts. > To me, the reliability and human-time cost savings from simpler, more > open and straightforward systems outweigh many other factors, > especially over the long term.
As an end user, what I would like is everything above the CPU bootrom should be open source, packaged within Debian main and auto-updated on the appropriate schedule considering flash longevity and update types. u-boot probably comes closest to that, although blobs are required on some platforms, vendor forks are numerous and updates are manual only. EDK2 is similar but worse because edk2-platforms is not available in Debian and devices run eventually abandoned proprietary EDK2 forks. ACPI comes from the world of proprietary non-redistribable vendor firmware (some EDK2 forks) provided separately to the operating system. > On Fri, 5 May 2023 at 12:52, Pete Batard wrote: > > > The Raspberry Pi SoC has also some very non-free code running > > Yep, I've still got quite a lot to learn about that, I think. The LibreRPi folks are working on replacing that: https://github.com/librerpi/lk-overlay/ -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
