[coreboot] Official builds for EoL Chromebooks

[Matt DeVillier]

Emi,

I think this is what you're looking for:
https://www.coreboot.org/Supported_Motherboards
It contains the commit hash, build config, and a few other logs for each
device/commit.  It is user submitted though, since there doesn't exist a
test setup for every supported device.

Right now, I'm the main builder/distributor of upstream coreboot firmware
for ChromeOS devices; I support all Haswell, Broadwell, and some Baytrail
devices, the former with both UEFI and Legacy Boot variants. When time
permits, I'll expand that to cover the rest of the Baytrail devices, then
move on to adding support for Skylake.  No plans for Braswell support
unless I acquire a device on which to test.

John Lewis has some upstream firmware for the older SandyBridge/IvyBridge
models, but his Haswell firmware is build from Google's tree/branches not
upstream.  He also has no plans for any future upstream firmware.

cheers,
Matt

On Thu, Oct 13, 2016 at 6:49 AM, Emilian Bold <emilian.bold at gmail.com>
wrote:

> Hello,
>
> Now that Coreboot has reproducible builds, could you provide a list of
> build hashes for Chromebooks that are or will soon reach End of Life?
>
> I see on https://support.google.com/chrome/a/answer/6220366?hl=en that 2
> Chromebooks will reach End of Life in 2016 and 3 more in 2017 then 7 in
> 2018. I assume the number will increase each year.
>
> I know that Coreboot does not distribute builds, but the little Custom
> roms section on https://www.coreboot.org/users.html seems insufficient.
>
> It's easy making a build, you just need to have the certainty you did it
> well. Or that the one you are downloading is correct.
>
> Posting an official SHA-256 hash for a ROM would solve this.
>
> --emi
>
> --
> coreboot mailing list: coreboot at coreboot.org
> https://www.coreboot.org/mailman/listinfo/coreboot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20161013/b9bddd92/attachment.html>