<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 13/10/16 20:45, Zoran Stojsavljevic
wrote:<br>
</div>
<blockquote
cite="mid:CAGAf8LwyJCeW18gMf2dNW-3UKnNngLe6riL8b5dO-56f4aBP5Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="font-size:12.8px">> John Lewis has some upstream
firmware for the older SandyBridge/IvyBridge models,</div>
<div style="font-size:12.8px">> but his Haswell firmware is
build from Google's tree/branches not upstream.</div>
<div style="font-size:12.8px">> He also has no plans for any
future upstream firmware.</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">Once upon a time when John worked
for SAGE Electronics. I remember this time, about 3 and more
years ago. ;-)</div>
<div style="font-size:12.8px"><br>
</div>
</div>
</blockquote>
I never worked for Sage.<br>
<blockquote
cite="mid:CAGAf8LwyJCeW18gMf2dNW-3UKnNngLe6riL8b5dO-56f4aBP5Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="font-size:12.8px">SAGE was the first company (FSP
echo system partner) to accept and adopt INTEL FSP (midst of
2013, IVB was the first child). Since then, lot of things have
changed. Lot of... SAGE is not anymore in this business, and,
and... .. . (you all fill in the dots). :-)</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">Zoran</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 13, 2016 at 4:53 PM, Matt
DeVillier <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:matt.devillier@gmail.com" target="_blank">matt.devillier@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Emi,
<div><br>
</div>
<div>I think this is what you're looking for: <a
moz-do-not-send="true"
href="https://www.coreboot.org/Supported_Motherboards"
target="_blank">https://www.coreboot.org/<wbr>Supported_Motherboards</a></div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>cheers,<br>
Matt</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div class="h5">On Thu, Oct 13, 2016 at 6:49 AM,
Emilian Bold <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:emilian.bold@gmail.com"
target="_blank">emilian.bold@gmail.com</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">
<div dir="ltr">Hello,
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>I see on <a moz-do-not-send="true"
href="https://support.google.com/chrome/a/answer/6220366?hl=en"
target="_blank">https://support.google.com/<wbr>chrome/a/answer/6220366?hl=en</a> <wbr>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.</div>
<div><br>
</div>
<div>I know that Coreboot does not distribute
builds, but the little Custom roms section on <a
moz-do-not-send="true"
href="https://www.coreboot.org/users.html"
target="_blank">https://www.coreboot.org/us<wbr>ers.html</a>
seems insufficient.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Posting an official SHA-256 hash for a ROM
would solve this.<br clear="all">
<div>
<div
class="m_8499266955393221105m_4448321613720898651gmail_signature">
<div dir="ltr">
<div><br>
</div>
<div>--emi<br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
<span class="HOEnZb"><font color="#888888">--<br>
coreboot mailing list: <a moz-do-not-send="true"
href="mailto:coreboot@coreboot.org"
target="_blank">coreboot@coreboot.org</a><br>
<a moz-do-not-send="true"
href="https://www.coreboot.org/mailman/listinfo/coreboot"
rel="noreferrer" target="_blank">https://www.coreboot.org/mailm<wbr>an/listinfo/coreboot</a><br>
</font></span></blockquote>
</div>
<br>
</div>
<br>
--<br>
coreboot mailing list: <a moz-do-not-send="true"
href="mailto:coreboot@coreboot.org">coreboot@coreboot.org</a><br>
<a moz-do-not-send="true"
href="https://www.coreboot.org/mailman/listinfo/coreboot"
rel="noreferrer" target="_blank">https://www.coreboot.org/<wbr>mailman/listinfo/coreboot</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>