coreboot August 2014

coreboot@coreboot.org

43 participants
102 discussions

Re: [coreboot] Chromium Upstreaming / Introduction
by Isaac 01 Aug '14

01 Aug '14

> Do you plan to upstream all Chromebook coreboot and libpayload > branches from Chromium git, or just the individual patches Sage finds > useful and necessary for the boards You currently work on? The goal of this effort is to minimize the differences between the Chromium chromeos-2013.04 branch and the coreboot master branch. As part of this any outstanding patches or differences between the branches will be addressed. > Do we expect the original authors to review the rebased, possibly > modified work, or is the plan these patches just get rubberstamped as +2 > by a 3rd party once they build cleanly? Original authors are automatically added as reviewers if they have coreboot.org gerrit accounts. I try to get approval from the original authors, but they are not always available for comment. If they are not available and the patch is non-trivial, we look for someone else familiar with the area or the original author of the section for review. We would like to avoid too many rubber stamp reviews. > Did you develop some nice method to keep track of which branches from > Chromium we can consider as completely upstreamed? This hasn't been a problem yet since we are only focusing on the chromeos-2013.04 branch at this time. If you know of a good solution for this I would appreciate any information. > Do you have the facilities to do regular board-status script runs for > recent Chromebooks? Not at this time but we're coordinating with Google on this. Isaac

1 0

events from GPIO in ACPI
by Krzysztof Pierwieniecki 01 Aug '14

01 Aug '14

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot August 2014