Age | Commit message (Collapse) | Author | Files | Lines |
|
Upstream bbclasses changed to typically use the `:${PN}` override
syntax, including the SYSTEMD_ variables. Change our systemd.bbclass
to do the same for consistency and perform a tree-wide variable
replacement.
Spot checked by building bletchley and witherspoon and checking
some of the SYSTEMD_LINK directives on installed packages under qemu.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20a9dd809bff8af8759488734f80486c7228c6eb
|
|
It was observed that we have different approaches to modifying the
EXTRA_OEMESON variable across our recipes. The bitbake manual
implies that override syntax (":append") is slightly better and the
poky meson bbclass also prefers it:
meta/classes/meson.bbclass:EXTRA_OEMESON:append = " ${PACKAGECONFIG_CONFARGS}"
Switch all recipes to use the ":append" override syntax for the
EXTRA_OEMESON variable.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I24e9a27a87c61f374acfb03a63955821fce0dd20
|
|
While debugging another issue, it was noticed that this service,
obmc-led-group-start/stop@power_on.service was installed within a
synchronization target. Specifically within the
obmc-power-stop@0.target. This target is only meant to be used as a
synchronization target, where other services use Wants/After/Before type
syntax to synchronize when they run.
For installing a service, the standard action targets should be used,
obmc-chassis-poweron@.target and obmc-chassis-poweroff@.target.
Tested:
- Verified services are in correct target and still run during chassis
on and power off.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I5fecc8236e20f83fb5636445710621bbc8b46b57
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
|
|
phosphor-led-manager has migrated from autotools to meson, and it needs
to be built with the correct led.yaml.
This will check if there's a led.yaml in the order of:
1. where LED_YAML_PATH specifies
2. default path of virtual/phosphor-led-manager-config-native
3. where SRC_URI += puts files to
and copies it to the right location.
Tested:
devtool modify phosphor-led-manager and checked if led.yaml is the
right one.
devtool reset, built the image and checked if led-manager are hosting
the correct led groups on dbus.
tried five different scenarios:
1. don't use phosphor-led-manager at all: yosemitev2
2. use config-native: romulus
3. use config-mrw-native: witherspoon
4. overrides the native path: hr855xg2
5. puts led.yaml in SRC_URI: created a custom one and tested that
Signed-off-by: Seires Li <seiresli@pcpartner.com>
Change-Id: Iacfbe633befd3f50f5ea685fd234a49e0eeb7b6f
|
|
We don't want to spend cycles building tests we won't use.
Change-Id: Ic7890e60e736189290caa1f528002b31f438a179
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
The intent behind this commit to build phosphor-led-manager with
meson and remove autotools.
Tested: built phosphor-led-manager successfully and worked.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Id90338dabd1862cced26a9d4f25204e4f8c36ec4
|
|
Currently, the phosphor-fru-fault-monitor updates the Asserted
property of the Led Group D-Bus object by monitoring the
`/xyz/openbmc_project/logging` object path.
The intent behind this commit is to add another way to monitor the
`xyz.openbmc_project.State.Decorator.OperationalStatus` interface
of the Inventory D-Bus object, and check whether the Inventory
D-Bus object is associated with the LED group D-Bus object, and
then update the Asserted property of the LedManager.
Since both these methods handle the faults differently,
Only ONE of these 2 methods can be enabled and NOT both.
The first way is supported by default. To turn OFF the default way
AND turn ON this second way, Enable monitor-operational-status.
Change-Id: I03701e599b6a120bc1f83da6f473b12f38660d64
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
phosphor-led-manager has 3 packages
- phosphor-led-manager : Default
- phosphor-led-manager-ledmanager : Packages phosphor-ledmanager
- phosphor-ledmanager-faultmonitor : Packages phosphor-fru-fault-monitor
Because of this, it was not possible to install files via Makefile and
that always needed a corresponding update to FILES_{PN}-ledmanager.
Removing phosphor-led-manager-ledmanager will eliminate this problem.
Change-Id: I00ca4c34346a47f887872464b9050a46d8f5e8e9
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
This commit enables phosphor-ledmanager to do lamp test
Change-Id: I4933ec034911198f99ae1289f681f15057310c33
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
This enables phosphor-ledmanager to use JSON configuration file
Change-Id: I3cbd0bf6b60e81f9f0a479ad51dab438c708c6c1
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Latest commit in phosphor-led-manager put a bash script
led-set-all-groups-asserted.sh. This commit packages it
to be installed in /usr/bin and also adds right RDEPENDS
(From meta-phosphor rev: 3c3dfb751869331d162790a4523257f6a383eafe)
Change-Id: I3c37b1eb22eea9fd2294be978413f1100a402a07
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-phosphor rev: b9d88f84b494d7e2a2d7ef2d30504dd07381dd66)
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I40b5f05f8245b78447d2211c2e9c14d3b738fa6e
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Some recipes have abstracted the git revision into a separate file
and have a line 'require ${PN}.inc'. The issue with PN is that it
changes to have a -native or -nativesdk for those contexts. The
variable ${BPN} (base package name) should be used instead.
(From meta-phosphor rev: c7d848ec9b524114550f80276f7b5e45b9ad8d46)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib875fd9904b16379b20dc7891087b8e0bf90fe69
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
sdbusplus has changed the package layout so that sdbusplus-native and
sdbus++-native are now ${PYTHON_PN}-sdbus++-native. Update recipes
that need to use sdbus++ (or its associated python modules) or remove
the DEPENDS if it is no longer necessary.
(From meta-phosphor rev: 2bebd1247cb78567441158b152c7a13f476afd4f)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I30f9c2220da9145ef0a7067e067aed1396d8b40d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-phosphor rev: 2d8cb275e2ed8dea767988d52e196e945e081a52)
Change-Id: I8b1f9c50c5ba13f11ea6be0d9bc062cfcda6667d
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Python dependencies for phosphor-led-manager is currently being
satisfied by inclusion of sdbusplus in the recipe. This will break
if sdbusplus changes its dependency list and hence adding python
dependency here
(From meta-phosphor rev: 48821f55ec14ab698b3ebcb568e30fc17ae1c8f6)
Change-Id: I9b4cf14e4f9f9b6ac8296368a179678196a33298
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
A number of corequisites exist so squashing these all into one patch.
meta-ingrasys - refresh master bc513127f4..67bcaf389f
meta-hxt - refresh master 86a4df514f..8fe0d38bbb
meta-phosphor - refresh master 06c09d7cce..df6ddae3d2
meta-quanta - refresh master 4f126361a1..53f3025271
Change-Id: I3daeef2a0467d8ea4f1fd1c617e526f8b11258af
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Patrick Venture (1):
build: install into bin instead of sbin
(From meta-phosphor rev: 5c9bbc1f349a591de14d971ff88cb75e36acfd83)
Change-Id: I566a3d4fe608f67f830b84b6694c7eb42f4aabe8
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Out of the box bitbake examines built applications, automatically adds
runtime dependencies and thus ensures any library packages dependencies
are automatically added to images, sdks, etc. There is no need to list
them explicitly in a recipe.
Dependencies change over time, and listing them explicitly is likely
prone to errors - the net effect being unnecessary shared library
packages being installed into images.
Consult
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-RDEPENDS
for information on when to use explicit runtime dependencies.
(From meta-phosphor rev: 26873c99d30b55e21a920c9851f21c3e2eab19f7)
Change-Id: I38640d75a2d834c07d45ddcdb0162f1a23f848d9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add missing explicit git PV variable to phosphor-led-manager git
recipes.
(From meta-phosphor rev: 6dc4c9ae971c0766357a2ebe84cf13fdaa106778)
Change-Id: I87c24ed53586d52ff8e89aa14b7d1fe3641ea964
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Rename phosphor-led-manager.bb to phosphor-led-manager_git.bb per OE
norms.
(From meta-phosphor rev: 6a7c3f325fd1289042aedf71c73dbc73ce4770d8)
Change-Id: I8ab28a360b4ff0b3eeaf030ce39dfc08be0c0736
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|