summaryrefslogtreecommitdiff
path: root/meta-ibm/meta-witherspoon/recipes-phosphor/dbus
AgeCommit message (Collapse)AuthorFilesLines
2019-05-11meta-ibm: witherspoon: fix up bbappend wildcardsBrad Bishop1-0/+0
A number of bbappend wildcards matched more than what was desired. Reduce the scope accordingly. phosphor-dbus-monitor-config-native%.bbappend -> phosphor-dbus-monitor-config-native.bbappend phosphor-ipmi-fru-read-bmc-inventory%.bbappend -> phosphor-ipmi-fru-read-bmc-inventory-native.bbappend phosphor-ipmi-fru-read-bmc-inventory%/bmc-fru-config.yaml -> phosphor-ipmi-fru-read-bmc-inventory-native/bmc-fru-config.yaml phosphor-ipmi-fru-read-not-sent-by-host-inventory%.bbappend -> phosphor-ipmi-fru-read-not-sent-by-host-inventory-native.bbappend obmc-op-control-power%.bbappend -> obmc-op-control-power_%.bbappend (From meta-ibm rev: c828be02d177ece43006329ee99ca4d2ef733c58) Tested: bitbake-layers show-appends still shows the witherspoon bbappends Change-Id: I5133261a33c4101d6d526355817a0adbac0ce0d9 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-10-22meta-ibm: witherspoon: dbus-monitor: drop symlinkPatrick Venture2-2/+1
Drop symlink and rename bbappend for phosphor-dbus-monitor. (From meta-ibm rev: b21533febcb99b14fc9d7c3817921bc4c0a3900c) Change-Id: I85f2c2fd0b889de1ee77f5edd095b8a10e95aee9 Signed-off-by: Patrick Venture <venture@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-10-17meta-ibm: witherspoon: dbus-monitor: set version wildcardPatrick Venture1-0/+1
Set the wildcard for version for phosphor-dbus-monitor.bbappend (From meta-ibm rev: dade96460c2ea6a377a95206ccb83ed2d955953e) Change-Id: Ibf7d4999f74c7c997a68614037f5e06dc5ff1d2d Signed-off-by: Patrick Venture <venture@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-09-26Remove mapper nice priorityAndrew Geissler2-9/+0
This is a revert of eff3d02a180ef60102f1f25d765b2ddf72831be3 A direct revert is not possible due to our subtree refactoring Prioritizing one application over another seems to cause more problems then it solves. In this case it appears that mapper can starve other process's in which mapper depends on responding. So that dependent process times out, restarts, which then causes the whole cycle to start over. Hoping this is the fix to openbmc/openbmc#3369 but will require some testing. Tested: George was kind enough to run this through some BMC reboot tests and a regression bucket. openbmc/openbmc#3369 did not recreate but not willing to declare success yet with that bug. (From meta-ibm rev: 9effdef83644fff90a2bcb6f4d6fb97ac28fcb28) Change-Id: I9af8ab369966a69c09d807d888b0bf5a0f0b3e07 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-08-23[Subtree] Bring openbmc machines to top levelDave Cobbley4-0/+14
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>