Age | Commit message (Collapse) | Author | Files | Lines |
|
Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this don't help.
(From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b)
Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Change-Id: I0bd40c9c583053864b312b4ed60f084ee29152ea
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This needs to be done so phosphor-logging will know to grab
the error log's metadata from the journal and add it to
the log in the AdditionalData field.
Resolves openbmc/openbmc#3015
Tested: Check that the LED errors now show up in the elog-lookup.cpp
file generated during the build by phosphor-logging.
Change-Id: I9bcbf1b1c8d7499e4ef8e384005c34b858d25a7d
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
Change-Id: I6373776531963351831420fea39d88fc3995e8bf
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Change-Id: I9eb363c6538b8e7d4eff622355b73fc99c48334e
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Replace invocations of mapper call with a call to busctl and mapper
get-service. This provides equivalent functionality but opens the
door for dropping a systemd patch we have carried for some time.
Change-Id: Iea0cce89341939b49b095d1f5010415578331d4d
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Change-Id: I270b213e29d80c99110a626ddf7b3ade4c602b2a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Change-Id: Ib7058accd115fa78c3b7801066c668be26ac8163
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
A number of recipes remove PN from the package list. While this
seems to work it is unconventional and puts us into dusty corners
of oe-core/bitbake.
Adopt a more conventional approach with ALLOW_EMPTY_${PN} = "1".
Change-Id: I1956784d05573749d356977f71dae0fd6bde2adf
Tested: Built phosphor-led-manager and validated package contents
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Change-Id: Ib8f0c8b345ded40100d89f2ca42cf118156d3c37
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Change-Id: I65745c91b154a6741e4ed920e03363ff4358678e
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Change-Id: I9de34dc5261a6a00674873d4b40a3ef963886ff0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Change-Id: Ic03f9947f93465140789dcb9ff7fd10bcb71be6d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
There were a number of places that inherited this class but did not
use it. A number of classes that did use it did not inherit it.
This was possible because the class was pulled in by the distro
configuration but that has been removed here as well.
Tested: Built and verified a witherspoon image
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I73511cdcc609875b4fe016967c1b84c5200fb703
|
|
Using MRW or not is distro policy. As such remove the obmc-mrw
machine feature.
Do not enable the remaining obmc-mrw distro feature in the base
phosphor distro configuration.
Create new distro configs for the systems that use MRW today
(i.e. Witherspoon) that enables the obmc-mrw distro feature and point
the local.conf.sample at the new distro configuration.
Change-Id: If4cedc745b3ee942518fbfd4d5cf2cd5b60f346d
Tested: Built a Witherspoon image and validate the manifest
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Create an mrw-xml bbclass that has variables for the
MRW XML filename and path to it. Then, changes all users
of the MRW XML to inherit that class and use those variables.
The filename will default to ${MACHINE}.xml if it hasn't already
been set to something else, such as in a .conf file.
This is done so that the file can be something other than
${MACHINE}.xml.
Change-Id: Ia7021e5a5d5e7946829e58688250aa64250cb00e
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
Change-Id: I3b0f57e6c64e061b460e06c7f16f14d1253a159d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Change-Id: I7b7089f1035db89442e9db8404c63fba21235055
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Change-Id: Ib610cbfb865233880524c3bf70d7440ee0630f40
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Change-Id: Ib612c9be64954ca79cc66cdb7b534e9e19385022
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Change-Id: I7156fc9bae33a9c11e9ec62251555b346cdc773a
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
This commit enables patches from the /usr/local path by replacing
absolute paths to /usr/sbin or /usr/bin in every service file with
"/usr/bin/env ". Additionally, SyslogIdentifier is added to each
file to ensure that journal entries are still distinct.
In two cases, service files also had to change due to references
to ${{PATH}}, which doesn't work with /usr/bin/env. These
references - and the corresponding definitions - were changed to
${{DEVPATH}}.
Resolves openbmc/openbmc#2149
Change-Id: I12c5c6e5101eef6820b985a563313836250ff2c7
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
|
|
It is a requirement that Firmware notifies users about it's
READY state and the mechanism was to assert 'bmc_booted` group
which would result in user defined behavior on corresponding
physical LED. Blinking a particular physical LED is one of the
most common ways to let users know.
The code was asserting the 'bmc_booted' group soon after the LED
daemon was alive and this was incorrect since LED daemon would
start early in the boot and not after reaching READY state.
This patch waits until reaching READY before asserting the needed
LED group.
If applied, this commit will resolve openbmc/openbmc#1919 only for
systems that are not based on MRW. For fixing this issue on Witherspoon
machine, a change needs to be made in openbmc/phosphor-mrw-tools to
make sure latest XML is chosen during build. Currently, its pointing to
an old XML.
Change-Id: Idc711942140295f2cf5d7b691eb9371f4da671d5
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Change-Id: Ie5696085a3fed98791a080c753454d38226e5f7b
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
As part of PowerOn, group 'power_on' gets asserted via
a service file that is associated with PowerOn and that
results in driving corresponding physical LEDs.
This works fine for a single PowerOn and does not work if
there is a PowerOff followed by a PowerOn.
Service file had RemainAfterExit set and did not have a stop
condition. This commit puts a Conflicts relationship with
appropriate stop service file and vice versa.
Fixes openbmc/openbmc#1918
Change-Id: Ie0e6b554b3ab7beacd3ad15a0ff76e4d6481f648
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Change-Id: I61ec574d6f1cbeb89df0a8654949b9712e378124
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Physical LED controller expects a sysfs path where it can find leds.
Current UDEV rule is passing $devpath and that works fine.
Because '-' is converted to '/' when systemd unit file processes it,
application needs to put a workaround to fetch the name of LED
correctly if the LED itself contains '-' in it.
Although $devpath still works to apply that workaround, it becomes
difficult for the workaround to look for a particular directory to
go beyond looking for led-name since not all LEDs would be having
/sys/devices/platform/leds/leds. However, all of those would share
'sys-class-leds' and hence passing 'sys-class-leds' with $name
makes it appropriate.
Change-Id: Iab5c71cf0c6f601a25b9b4470b46d7fc4d930223
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Change-Id: Ia4084f673f67364298b7c2d7d0a29f7d47b759d2
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Change-Id: I1758f55ed0cd9379d7fb0a362631f06620ee2e03
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Change-Id: Ic849953fc7fd1b055d0f5d01bf91edcb7da226cb
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Change-Id: I4b181982062eeaa87eb8581765cc495097df0c85
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Change-Id: Icc388ce122baf4351e4ade1264b860065b624cfd
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Resolves openbmc/openbmc#941
Change-Id: I3e5672af468185f6bae50c438820a10d57d60d55
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
|
|
Change-Id: Ifd09d7f13a0991211fdfecd9cd530fa8557bf33f
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Change-Id: Idddad95a0ea07c3f16fcf2b5186b19701c20984f
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Regardless of the machine type, there needs to be standard set
of LED groups that would get asserted / de-asserted under these
conditions:
1) BMC booted
2) Power On
3) Power Off
This makes sense on hardwares that have physical LEDs.
However, QEMU does not have physical LEDs associated with the
groups but the groups themselves can be in asserted state so that
if physical LEDs are implemented in future, they can be used.
Change-Id: Iaa081e59a356670b9f713db11bd45dbda55a6bd4
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Change-Id: I0d0caa5fcf4e67a80eed34f430649d090a17847e
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Change-Id: Iade01cf5027660a15734e226560c52d50fa17834
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Now that the changes are made to use the new phosphor-ledmanager,
the old ledcontroller will need to go away
Change-Id: Idffbffbd180334278af740322c140908069b7ceb
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
phosphor-fan-presence.bb: bump version
phosphor-inventory-manager.inc: bump version
phosphor-ipmi-host.bb: bump version
skeleton-rev.bbclass: bump version
phosphor-led-manager.inc: bump version
phosphor-mapper.bb: bump version
phosphor-ipmi-fru.inc: bump version
phosphor-state-manager.bb: bump version
phosphor-logging.bb: bump version
openpower-fru-vpd.inc: bump version
Resolves openbmc/openbmc#1112.
Change-Id: Iaf32b0e828dc4f2da021eae9b8e1d440042841d8
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
This fixes a build warning
WARNING: phosphor-led-sysfs-1.0-r1 do_package_qa: QA Issue:
phosphor-led-sysfs rdepends on phosphor-dbus-interfaces, but it isn't
a build dependency, missing phosphor-dbus-interfaces in DEPENDS or
PACKAGECONFIG? [build-deps]
and occasional build failures due to phosphor-led-sysfs:do_configure
running before phosphor-dbus-interfaces is built.
Signed-off-by: Xo Wang <xow@google.com>
Change-Id: Id59e0ffff5befa66e90a0d29373368ab0a0a36ee
|
|
Change-Id: I660be705473dacdaa1a9b9e555daab0487830afc
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Fixes openbmc/openbmc#1308.
Change-Id: I10bbbec6113df49e6d6c0480eb8bf3cc06d017f4
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
Change-Id: I6a0bb20fe94ad87b049799e698684df6930fe3b4
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
This has the changes that enables LED group manager on Palmetto
Change-Id: Iaf4d4cc4c798c70e557009e9928225facb1d7d86
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
phosphor-led-manager-config is a meta-recipe that pulls in other native
recipes based on mrw enablement.
Switch from being a target recipe to a native recipe. A native recipe
is more appropriate since a target recipe will cause bitbake to
create -dev packages and attempt to install those into an SDK.
Change-Id: I42af0796960cefe19d182afb2957e5c4853c6d28
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The busname directive in the sd unit template did not match
the claimed busname.
Change-Id: Ide67cd91b0fd560f06726736fbba8f5177b05164
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Change-Id: Ib9f511441dc2475baf575cd610c96b67cc3af8bb
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
phosphor-led-manager took a change to correct the DBUS names
complying to DBUS conventions and this change is to use that updated
object path.
Previously, it was /xyz/openbmc_project/ledmanager/groups
Updated to : /xyz/openbmc_project/led/groups
Change-Id: I1a8db82ef50f2da25d1c2e743d5a1403d5153df1
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Change-Id: Ief0c4f3081ae316dc659107825c01a6b77ec5dfc
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|