[coreboot-gerrit] Change in ...coreboot[master]: Add complete per-board coreboot no-blob/blob status

[Nico Huber (Code Review)]

Nico Huber has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/32237 )

Change subject: Add complete per-board coreboot no-blob/blob status
......................................................................

Patch Set 7:

(2 comments)

https://review.coreboot.org/#/c/32237/7//COMMIT_MSG 
Commit Message:

https://review.coreboot.org/#/c/32237/7//COMMIT_MSG@11 
PS7, Line 11: and the entrypoint of coreboot executes unconditionally
            :     to the best of knowledge.
> Would that mean that haveing a ME/TXE/CSE/CSME in the platform should be mentioned as blob as well?  […]

It depends on the configuration of those platforms. I guess
having coreboot support for a board (currently) implies that
they ship in a configuration that executes the reset vector
(not an ACM blob or whatever).

https://review.coreboot.org/#/c/32237/3/Documentation/mainboard-blob-status.... 
File Documentation/mainboard-blob-status.csv:

https://review.coreboot.org/#/c/32237/3/Documentation/mainboard-blob-status.... 
PS3, Line 6: google/daisy,?,Exynos
> I believe the BL1 is signed with a Samsung-owned key,

That's nice to hear.
> so as long as you trust their key management, it's pretty much the same in this case.

Trust their key management and implementation of the verification ;)
> The blobs themselves are actually in the blobs directory and have been there for a long time... they're just in cpu/samsung (rather than soc/samsung) since they were added before we introduced src/soc and I guess nobody thought about moving them when we moved the corresponding source tree.

You mean those ASCII blob fakes that tell you to download it somewhere else?