New issue
Advanced search Search tips

Issue 672861 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Mar 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

factory: Maintain reference boards in public source repo

Project Member Reported by hungte@chromium.org, Dec 9 2016

Issue description

We've previously removed factory code (chromeos-factory-board) for follower projects on ToT/master, since follower projects should only have their code in factory branch, private overlay.

However maintaining follower boards by cloning from reference board overlay is still not the best approach.

We should move reference board implementations into public overlay, so follower boards can easily create a "ToT working toolkit" by inheriting right reference board.

In other words, currently in py/device/boards we only have
 LinuxBoard
 ChromeOSBoard
 AndroidBoard

In future we should move reference boards here, i.e.
 ReefBoard
 GruBoard
 OakBoard
 StragoBoard

So follower boards can do things easily like
 class ElmBoard(OakBoard):
   pass

Or even better if we can in future have some platform reference so follower projects can "auto select right board".
 

Comment 1 by hungte@chromium.org, Jan 25 2017

Owner: hungte@chromium.org
Status: Started (was: Untriaged)

Comment 2 by hungte@chromium.org, Jan 25 2017

Almost all x86 boards can be empty implementation now.

Still need to revise for ARM boards and chromebox.

Comment 3 by hungte@chromium.org, Mar 13 2017

Status: Fixed (was: Started)
Not seeing much difference in ARM boards after we've finished migration.

Comment 4 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 5 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 6 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment