summaryrefslogtreecommitdiff
path: root/meta-ibm/meta-witherspoon/recipes-phosphor/packagegroups
AgeCommit message (Collapse)AuthorFilesLines
2019-07-24meta-ibm: use ibm-ac-server MACHINEOVERRIDEBrad Bishop1-5/+4
Use an override in bbappends in meta-witherspoon as described and recommended in the "following best practices when creating layers" section of the the Yocto development tasks manual. ibm-ac-server represents common machine configuration shared by all of IBMs "Accelerated Compute" class of servers. Apply it wherever any variables are un-bounded by any override. This enables more flexible use of meta-witherspoon in build configurations, and easy addition of machines to the layer. (From meta-ibm rev: bb0e1d0699a4b9905c053c94af7d882cd71779fc) Change-Id: I82f7338b0d7a64b5e7a67e19bcdff07f48a332d4 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-24meta-ibm: use machine overrides instead of distroBrad Bishop1-1/+2
Using a distro feature here might be a case of too much abstraction. Instead, just enable them because that is what is desired for those systems. This is slightly easier to comprehend. Revisit, if at a later time, several phosphor-software-manager users enable signature verification and file syncing when using UBI (making the abstraction useful). If/when that occurs, those configure options and packages should be enabled via the distro feature in the base recipe and not in a bbappend. (From meta-ibm rev: 50eebe208babfe35ccd5a3ed8d560669381e82a5) Change-Id: Ic4ac7f89eeb4575e6dabb68bb61aa55835316864 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-29meta-ibm: spoon/palmetto: op-apps: remove fansBrad Bishop1-1/+0
obmc-control-fan is no longer included by the OpenPOWER layer, so there is no longer a need to explicitly remove it here. (From meta-ibm rev: 446d589ce72cebf974ffaca2dca61de2823a140d) Change-Id: Iba5fc8a745ffb128b83903dc0ad3ad787ebbcd21 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-25meta-ibm: op-apps: remove obmc-button-resetBrad Bishop1-1/+0
There isn't an obmc-button-reset package in op-apps in the first place, so this line is a noop. Remove. (From meta-ibm rev: 748c1192bf2f2fa6be2cdf5e6f3b88829f28835b) Change-Id: If34a02d6603834919ab969579c0fca0e0ab28f1a Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-29wspoon: remove obmc-button-resetMatt Spinler1-0/+1
This system does not have a reset button. Resolves openbmc/openbmc#3442 (From meta-ibm rev: 32afb9391c2745e1a887aae055ce74553d30f6ac) Change-Id: If1c9bd34c3749ddba1d39a7fd3dc08cf9327be1a Signed-off-by: Matt Spinler <spinler@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-08-23[Subtree] Bring openbmc machines to top levelDave Cobbley2-0/+6
The new subtree model brings the subtrees up from the openbmc-machines layer. Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0 Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>