Blob Matrix: Difference between revisions

From coreboot
Jump to navigation Jump to search
No edit summary
No edit summary
Line 25: Line 25:


We think the Alpha had an EC, which was closed and had a blob; it was otherwise blob free.
We think the Alpha had an EC, which was closed and had a blob; it was otherwise blob free.
So:
{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
! align="left" | Mainboard
! align="left" | EC Blob
! align="left" | ME Blob
! align="left" | Mask blob
! align="left" | VGA blob
! align="left" | Reset vector blob
! align="left" | Microcode Blob
|- bgcolor="#dddddd"
| pixel
| No
| Yes
| No
| Yes
| No
| Yes

Revision as of 20:59, 16 February 2014

This the the Blob Matrix. What is the Blob Matrix? It is a table in which we define, for different systems, what blobs there are. The goal is to have a common reference of types of blobs. Until we're sure we have the right list we don't need the matrix yet.

Consider, for example, the Google Pixel laptop. We can identify the following CPUs that affect coreboot or that it uses: EC, ME, main CPU.

For this example, we have the following blobs: ME, blob from Intel (replaceable, signed); main CPU: microcode (not practically replaceable), MRC (not practically replaceable), VGA BIOS (replaceable, proof of concept in repo).

Here is another system, the Snow Chromebook. It has an EC and a main CPU. The blobs are main CPU: BL0 (not replaceable), and BL1 (replaceable, signed).

My old x60, with coreboot on it: EC: EC OS (not replaceable); ME, blob from Intel (replaceable, signed); main CPU: microcode, BIOS, VGA BIOS

Let's consider the first coreboot systems, the l440gx, PowerPC, and Alpha

The l440GX had no CPUs save the main CPU, and all of linuxbios was open. There was no ACPI or SMM.

The PowerPC was, similarly, blob free.

We think the Alpha had an EC, which was closed and had a blob; it was otherwise blob free.

So:


Mainboard EC Blob ME Blob Mask blob VGA blob Reset vector blob Microcode Blob
pixel No Yes No Yes No Yes