pietrushnic
commented
1 year ago This is just the first stage of a multistage strategy:
- when we can reliably deliver open-source firmware 'as is' and handle potential problems by simple recovery or bug reporting, we have a good base for creating a roadmap for Dasharo
- if we know the potential drawbacks of 'as is' deployment, we can evaluate how far we are from creating Dasharo for a given platform
- if the quality of deployment, potentially with additional code from Dasharo forks, is good enough, we can lead in the direction of Dasharo self-certification by running the dedicated test suite
From that point amount of supported hardware can grow organically and increase the pool of devices that use open-source firmware and Dasharo.
- next stage would be to provide tools for people to attest software stack running on the device according to user-chosen policy
- next stage would be to have some paid guarantees for given workflows e.g. safety-critical application
The problem you're addressing (if any)
There are many platforms on which we can flash coreboot internaly. Unfortunately, this requires some (sometimes quite a lot of) knowledge to properly compile the binary, backup the current firmware and perform the flashing procedure. DTS could help here, for example by detecting whether open-source firmware can be installed on a given hw. Maybe even compile code and deploy firmware
as iswhich mean the state that coreboot (or other firmware) is right now for given platform.Describe the solution you'd like
Simple script that basing on HCL report detect and tell what is on given platform and if we can flash open-source firmware on it.
Where is the value to a user, and who might that user be?
Any open-source community member or someone that just want to become a member and check potential of open-source firmware on his platform.
Describe alternatives you've considered
Additional context