| 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
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The phosphor-gpio-presence application is no longer needed for power
supply presence detection after the updates to using libgpiod in the
phosphor-psu-monitor application.
Remove the systemd parts of the bbappend, and remove the obmc conf
files.
Signed-off-by: B. J. Wyman <bjwyman@gmail.com>
Change-Id: I18a7f36e21d18a22f7625aadc3229ce5439c8d6a
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built rainier and verified the files were installed as expected:
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/default/obmc/gpio/phosphor-power-supply-0.conf
Change-Id: I6539c71cfc37fa67027204b17c68a0c7f8fec5a6
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The firmware code in these power supplies takes about 1500 milliseconds
to boot after they are inserted, and the presence line goes active.
Until the firmware has completely booted, the power supplies will not
respond to the I2C traffic initiated by the BMC device driver code as it
attempts to probe the hardware.
Adding in a DRIVER_BIND_DELAY_MS environment variable, set to 1500
(milliseconds), to delay the device driver binding in order to hold off
the probe until the power supply firmware should be ready, in order to
avoid ENXIO errors.
Change-Id: I101f8e3b7ff1c2c9e76df758c4551c7793006266
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
|
|
The rule of thumb within OpenBMC is to utilize a wants relationship with
targets, especially the multi-user.target. This follows the general
design of always allowing the system to continue whenever possible.
For example I'm doing some bringup in simulation where these services
are not required, but their failure is impacting my ability to reach
a successful multi-user.target state which impacts other targets that
depend on it.
Tested:
- Verified multi-user.target completes successfully now on my bringup
system
(From meta-ibm rev: f2f6d38efdfa1a88a5f41b9871e0d3aa76f193d1)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I687fbbb7006a3d9b9abe1d308802914d64224410
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
