Add ivy bridge/ sandy bridge IFD and ME extracted blobs

[Thierry Laurion]

Hello there,

Can Lenovo x230, x220, t430 and t420 (sandy bridge/ivy bridge) ME/IFD
binary blobs be added into coreboot-blobs without licensing issues?

Non-neutered ME and ifd blobs are already distributed here:
https://github.com/coreboot/blobs/tree/master/mainboard.

Some are distributed with a license file:
https://github.com/coreboot/blobs/blob/master/mainboard/facebook/fbg1701/lic...

Others are distributed without:
https://github.com/coreboot/blobs/tree/master/mainboard/google/parrot

How does coreboot proceeds into adding board specific blobs into the tree?
What is the deal with Intel regarding the ones present without license? Do
they tolerate them? Would it be an issue to distribute x230/x220/t430/t530
to ease CI  reproducible builds?

Asking because nobody dares to answer from the legal perspective. Can we
extend coreboot-blobs?
https://github.com/osresearch/heads/issues/307#issuecomment-578524123
https://github.com/osresearch/heads/issues/307#issuecomment-552961256
https://github.com/osresearch/heads/issues/307#issuecomment-588264758

Thanks

[Frans Hendriks]

Hello Thierry,

Adding ME/IFD binaries might require an license.
(This depends on the original license supplied with the system)

For Facebook fbg7101 license has been arranged with Intel.
Google Parrot is uploaded 7 years ago. I don’t know if there was a license at the time.

Note: INAL

Best regards,
Frans Hendriks
Eltan B.V.

From: Thierry Laurion [mailto:[e-mail]]
Sent: zondag 1 maart 2020 18:59
To: Coreboot 
Subject: [coreboot] Add ivy bridge/ sandy bridge IFD and ME extracted blobs

Hello there,

Can Lenovo x230, x220, t430 and t420 (sandy bridge/ivy bridge) ME/IFD binary blobs be added into coreboot-blobs without licensing issues?

Non-neutered ME and ifd blobs are already distributed here: https://github.com/coreboot/blobs/tree/master/mainboard.

Some are distributed with a license file: https://github.com/coreboot/blobs/blob/master/mainboard/facebook/fbg1701/lic...

Others are distributed without: https://github.com/coreboot/blobs/tree/master/mainboard/google/parrot
How does coreboot proceeds into adding board specific blobs into the tree?
What is the deal with Intel regarding the ones present without license? Do they tolerate them? Would it be an issue to distribute x230/x220/t430/t530 to ease CI  reproducible builds?
Asking because nobody dares to answer from the legal perspective. Can we extend coreboot-blobs?
https://github.com/osresearch/heads/issues/307#issuecomment-578524123
https://github.com/osresearch/heads/issues/307#issuecomment-552961256
https://github.com/osresearch/heads/issues/307#issuecomment-588264758

Thanks
--
Thierry Laurion