| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
| |
Resolves openbmc/openbmc#941
Change-Id: I3e5672af468185f6bae50c438820a10d57d60d55
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
|
| |
|
|
|
|
|
| |
This has the changes that enables LED group manager on Palmetto
Change-Id: Iaf4d4cc4c798c70e557009e9928225facb1d7d86
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
There is already a folder for led related
recipes.
Change-Id: Ic137555b04786844831ec9ff08f3b0488d111293
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
