summaryrefslogtreecommitdiff
path: root/meta-phosphor/conf/distro/include/phosphor-mrw.inc
AgeCommit message (Collapse)AuthorFilesLines
2019-05-22meta-phosphor: fans: remove native supportBrad Bishop1-2/+2
All OpenBMC BSP layers have moved to target class config recipes. As such, support for native class config recipes can be removed. (From meta-phosphor rev: f3b437c327b94df6f22c7d821f25d76f1d1c2180) Change-Id: I7729f7e34529a220af36b88017cb48a3ee887acb Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-21meta-phosphor: fans: enable non-native recipesBrad Bishop1-2/+2
There exists a number native class recipes throughout meta-phosphor that simply provide a data (often YAML) file as input to building another application. Having these data file recipes implemented as native class recipes prevents the use of machine overrides because bitbake (rightfully so) discards machine qualifiers from native recipes. Further, data files aren't really any different than library header files and those are consumed by recipes as target class recipes that are DEPENDed on. Do the same thing for data file recipes. A number of steps (patches) are required to ensure backward compatibility while other BSP layers make the transition to target class recipes. This patch is the first step in the sequence. Each native class recipe is duplicated with (approximately) the following transformation applied: 1 - remove "inherit native" 2 - add "inherit allarch" 3 - Add appropriate files to FILES_${PN} Also fixed a couple idiosyncrasies like SRC_URI += and LIC_FILES_CHKSUM that are not required. Finally, add a temporary layer of indirection around STAGING_DIR_NATIVE and STAGING_DIR_HOST to the fan metadata until other BSP layers have fully transitioned to target class config recipes. (From meta-phosphor rev: 19ee51f5cdce2ff2f076a3ca9263dabc79072ba9) Change-Id: I9671cc5343ed29a7ccfcee4cc00ebaaa9327e359 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-03-13MRW: Use a distro override to enable providersBrad Bishop1-0/+14
Now that obmc-mrw is no longer a machine feature we can organize a bit and enable MRW providers off to the side with a disto override, de-cluttering wherever non-MRW defaults are specified. No functional impact but slightly easier for humans to parse. Change-Id: If2731206b94e16e0b0132a385756eb11178118f2 Tested: Built a Witherspoon image and validated manifest Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-03-13distro: Add MRW distro policy includesBrad Bishop1-0/+3
Add MRW distro policy includes to prepare for removing the obmc-mrw feature from the default distro policy. Custom distros can enable MRW by including the MRW include(s) from their distro configuration. The content is a little light at the moment but it is anticipated it will grow in subsequent patches. Tested: No functional changes Change-Id: I9120662618b45f0b73902edc666c7684b499a40c Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>