Bug 10085 - RMC: move RMC feature out of meta-intel
Summary: RMC: move RMC feature out of meta-intel
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
: Low enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-08-04 20:27 UTC by Jianxun Zhang
Modified: 2020-06-25 08:43 UTC (History)
4 users (show)

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


Attachments
Proposal to have a standalone meta-rmc project (33.55 KB, application/pdf)
2016-08-04 20:27 UTC, Jianxun Zhang
no flags Details
(Part of) Discussion to move RMC out of meta-intel (48.85 KB, application/pdf)
2016-08-04 20:28 UTC, Jianxun Zhang
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jianxun Zhang 2016-08-04 20:27:17 UTC
Created attachment 3336 [details]
Proposal to have a standalone meta-rmc project

Initially one goal in design stage of RMC feature is to have zero-change in OE because I feel there are a lot of uncertainty and moves out of our control. A decision to land RMC in meta-intel was also made.

With the recent evolution in our discussion, I don't think meta-intel is the right home  in the long run by asking a BSP to carry a distro feature. Maintainer Tom Zanussi also think RMC should be out of meta-intel and be in OE.

I also suggested to consider to have a new standalone YP project to hold RMC integration and with builtin samples to eliminate any footprint in a well-established BSP like OE and meta-intel. This is not in scope yet since the size of project is too small to be in a new repo.

The current decision is to migrate RMC into OE.

No matter where we want to re-position RMC feature, I kindly remind maintainers some fundamental view points which may cause concerns:

() RMC project is intended to be called by any SW to have a runtime board-specific customization with a generic logic. Modification in (upstream) projects are necessary. Before this new feature is well accepted and patches to these projects are upstreamed, layers RMC takes home must carry these patches. (I don't think recipes could be a huge debt)

() Board-specific data can be anywhere. RMC also present builtin examples for several boards. We also need to think about if these are welcome in a generic layer like OE.

I will attach correspondence in this ticket.
Comment 1 Jianxun Zhang 2016-08-04 20:28:01 UTC
Created attachment 3337 [details]
(Part of) Discussion to move RMC out of meta-intel
Comment 2 Tim Orling 2020-06-25 08:43:57 UTC
Work on RMC has been discontinued and it is no longer supported.