Comparison table of various firmware already scored on the Dasharo page

[pietrushnic]

Code that can generate a comparison table of various firmware already scored on the Dasharo page

Looks like out of scope of what the utility does and is supposed to do. Sounds more like another utility to gather the data from docs.dasharo.com. Also does not seem to be related directly to focus on empty space and liberation from binary blobs (a separate issue for that would be better).

What exactly we would like to compare? Just the raw percentage of open/clsoed code ratio/liberation factor? Openness Score report contains much more data which does not necessarily needs to be compared, nor will give meaningful data. For now I don;t see what information could such comparison table provide, except openness/liberation percentage or raw closed source size change over the years of CPU evolution.

Another matter to solve is where to gather the data input for these comparisons. It should be something that is easily parsable and can be quickly imported to an array or something. Simplest would be CSV file...

Feeding it with the same platforms over and over does not increase the variety of results (e.g. feeding the utility with multiple releases of the same platform would just give neglectable differences).

Originally posted by @miczyg1 in #924 (comment)

[pietrushnic]

@miczyg1

What exactly we would like to compare? Just the raw percentage of open/clsoed code ratio/liberation factor? Openness Score report contains much more data which does not necessarily needs to be compared, nor will give meaningful data. For now I don;t see what information could such comparison table provide, except openness/liberation percentage or raw closed source size change over the years of CPU evolution.

Size of TCB in various market segments and versions of firmware. That may resonate with those who looking for balance between hardware cost and level of closed source they dealing with.

Another matter to solve is where to gather the data input for these comparisons. It should be something that is easily parsable and can be quickly imported to an array or something. Simplest would be CSV file...

It would be ideal, but do we have so much results that sorting would be needed? UX is important and paramount for such information. How we would achieve it with CSV?

Feeding it with the same platforms over and over does not increase the variety of results (e.g. feeding the utility with multiple releases of the same platform would just give neglectable differences).

Initial idea was to have it cross market segments. Do you envision that differently?

[miczyg1]

Size of TCB in various market segments and versions of firmware. That may resonate with those who looking for balance between hardware cost and level of closed source they dealing with.

So it basically means just closed source bytes vs open source bytes. The data is there, only need to put it in one place/table and show it. Make some ranking?

• sorting by total code size, the less the better
• sorting by closed-source size removed to total code size ratio, the more the better
• others?

It would be ideal, but do we have so much results that sorting would be needed? UX is important and paramount for such information. How we would achieve it with CSV?

CSV may be consumed by a different utility, oriented on the representation of data. Making a does-everything, good-for-nothing boilerplate from openness score source is not the way to go IMO.

Initial idea was to have it cross market segments. Do you envision that differently?

There is very little comparison of cross market. We don't have real servers for comparison. Embedded Intel segment is not that much different from client segment, in terms of FSP and microcode size, so differences in results would be neglectible. What we can surely observe is a cross microarchitectural closed source increase trend. Feeding the utility with scores made on platforms using different CPU/SOC microarchitecture will give interesting enough results.