New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 644290 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Sep 2017
Cc:
aaboagye@chromium.org
█ rspangler@chromium.org
█ wfrichar@chromium.org
█ bhthompson@chromium.org
adurbin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Create new package that builds all ToT EC boards

Project Member Reported by aaboagye@chromium.org, Sep 6 2016 
We should create a package that will build all the EC images for all boards supported in ToT in the EC repo. Just running "make buildall" does that, and runs the unit tests too. Then we'd only need to do that once on a trybot and CQ.

The firmware shellball found in chromiumos_image.bin gets its firmware blobs from BCS. They're only put up there and marked valid after they've run through FAFT and other tests.

Any EC firmware blobs that are being built as part of a specific target disk image aren't being used, so there's no need to be doing it on every builder.

Comment 1 by bhthompson@google.com, Sep 6 2016

Cc: aaboagye@chromium.org
Are you looking at just having an ebuild that does this (e.g. chromeos-ec-all) or to have a builder which actually builds these?

This sounds kind of like something I was thinking about previously for the consumers of the EC in non traditional EC cases (e.g. type c adapters and such), making a sort of 'peripherals' build target (e.g. board=peripherals). Today these get hooked into some existing board (e.g. samus) to build the binaries, but it would be cleaner if they had their own build target(s).

Comment 2 by aaboagye@chromium.org, Sep 6 2016 

I guess both? Having a builder that will build and publish those EC binaries (for all boards, peripherals included) would be nice. Not sure about how release branches would look like though.

Comment 3 by wfrichar@chromium.org, Sep 6 2016

Cc: rspangler@chromium.org
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 7 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by aaboagye@chromium.org, Sep 8 2017

Labels: -Hotlist-Recharge-Cold
Status: Archived (was: Untriaged)
This kind of fizzled out. Feel free to reopen if it's deemed important again.
►

Sign in to add a comment