upvote
there is upstream code but it's not well-integrated, and google's tree is largely optimised for their own payload called Deptchcharge. mrchromebox tweaks coreboot for use with edk2 so you can use normal operating systems, and the modifications that they make are extensive, e.g. mechanism in EDK2 to update EC firmware at boot time. mrchromebox is, for our purposes, a coreboot distro or indeed its own upstream. libreboot takes mrchromebox and makes several of its own modifications. "just use coreboot" is easier said than done :)
reply
This is Libreboot, not Coreboot. Libreboot removes binary blobs and Intel ME. It’s a freedom-oriented distribution of Coreboot.
reply
I realize that, but what's the selling point of Libreboot on Chromebooks when Coreboot is already supported, and it merely merged in support from Coreboot?
reply
Assurance that binary blobs and Intel ME support has been properly removed. It’s possible to do this with Coreboot if you know what you’re doing, but this is an off the shelf configuration.
reply
Nothing has changed about modern Intel CPUs requiring binary blobs. Libreboot is no longer blobless. Canoeboot is blobless. Libreboot is like decaf. It's not caffeine free, it's decreased caffeine.
reply
You’re correct, I guess haven’t been following this over the last few years. It looks like blobs are now merely minimized and ME is neutered with me_cleaner. So the only difference versus stock coreboot is that these minimizations are now the default configurations.

Old Libreboot is now apparently Canoeboot, same dev but different project name.

reply