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

Issue 702469 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Graphyte: Instrument plugins handle specific waveform files for each chipset

Project Member Reported by akahuang@chromium.org, Mar 17 2017

Issue description

Originally, we thought we can verify Rx test of each RF chipset with a universal waveform file. But in practice, the feasible waveform for each RF chipset might be different. We should consider a way to assign specific waveform file in each project.

Currently we tar all the waveform files and store it at the private localmirror. When we make the package, we download the file and merge with the source code. If we also put the specific waveform file into the tar file, the size will increase as we integrate more and more projects. Moreover, we might deploy the unrelated waveform files to the next project.

Therefore, my proposal is we still put the additional waveform file at the localmirror but in different zip file. When I make the package, I can choose which additional waveform should be downloaded. Then it can be easily reused by next project, and keep it easy to deploy.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 22 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/vendor/graphyte-litepoint/+/8c2ff28cd149723f8f624ef4ec77eabc9266059f

commit 8c2ff28cd149723f8f624ef4ec77eabc9266059f
Author: Chih-Yu Huang <akahuang@google.com>
Date: Sat Apr 22 04:57:32 2017

Status: Verified (was: Assigned)

Sign in to add a comment