Bug 11133 - RMC: Multiple fingerprints per Board
Summary: RMC: Multiple fingerprints per Board
Status: RESOLVED OBSOLETE
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.4
Assignee: Todor Minchev
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-03-07 10:36 UTC by Mikko Ylinen
Modified: 2017-05-18 16:36 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mikko Ylinen 2017-03-07 10:36:01 UTC 
It seems different BIOS versions for a board may result in different RMC fingerprints. This means the board detection will fail, e.g., if the fingerprint maintained in the database does not match with the BIOS info.

With the current design, the fingerprint-board mapping is 1:1, i.e., for each board there's only one fingerprint. Every time the fingerprint needs to change, either a new copy of the board is needed OR the old fingerprint is updated (and the old versions are no longer supported by the db).

To ease the maintenance problem, each board must be able to store multiple fingerprints (N:1 mapping).
Comment 1 Todor Minchev 2017-05-18 16:36:04 UTC 
Does not apply to RMC2. Files can be shared between platforms by creating links between fingerprint directories.