[coreboot] Recommended workflow with Chromebook support

[Matt DeVillier]

On Fri, Jan 5, 2018 at 6:19 PM, <tturne at codeaurora.org> wrote:

> Folks,
> This question is directed at the Coreboot developers who target a
> Chromebook device.
>
> Do you tend to do bulk of development and testing within chromiumos
> coreboot tree or directly in coreboot.org tree?
>
> As we get going we are trying to decide if it makes more sense to work
> directly in chromium tree and then rebase our commits onto coreboot tree
> and test compile prior to submission upstream?
> Cheers,
> T.mike



personally, I do all my work upstream, as I'm not building for ChromeOS.
If I were, I might use the device's Chromium branch instead, but it would
depend on the age of the device and how out of date its branch was.  Older
devices were originally committed in the Chromium tree then upstreamed, but
it's the opposite for newer devices (APL/KBL and newer).

I've also been working the past few years to upstream as many older devices
as possible, and to push my own fixes where appropriate.  I think all
that's left now are Skylake/FSP 1.1 devices, at least on the Intel side,
and those are next on my list.

-Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20180107/7ab0b468/attachment.html>