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

Issue 734738 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

Is FW_BLOBS needed?

Project Member Reported by sjg@google.com, Jun 19 2017

Issue description

In https://chrome-internal-review.googlesource.com/c/375491/

we added FW_BLOBS. We use it to add a file that seems to be related to baseboard-reef.

There is already a mechanism in the coreboot build to use files in /firmware/coreboot-private

How come we don't install the ps8751_a3.bin into /firmware/coreboot-private/3rdparty/blobs/baseboard-reef ?

Also how come it is installed after the emake within the coreboot ebuild? Does the coreboot Makefile not know about this file?

Thanks!

 

Comment 1 by sjg@google.com, Jun 21 2017

Owner: caveh@chromium.org
-> caveh for comment :-)

Comment 2 by caveh@chromium.org, Jun 23 2017

Labels: -Type-Bug Type-Task
Status: WontFix (was: Untriaged)
the scheme we use to import this blob (there will be more)
is modeled after the scheme we use for ec (ec*.bin) and pd (pdrw).
see coreboot*.ebuild:add_ec() and PD_FIRMWARE and PD_SYNC in
the various overlay make.conf files.

if there's enough interest, we can refactor how we import these
blobs, but as far as i can tell, this is WAI at this point.

coreboot itself doesn't care about this blob.
depthcharge needs it to flash the peripheral(s)
during the software sync phase.

Sign in to add a comment