Age | Commit message (Collapse) | Author | Files | Lines |
|
The `witherspoon-tacoma` machine utilizes the same JSON config files as
the `witherspoon` machine so override the PKG_DEFAULT_MACHINE variable
for tacoma to be set to the witherspoon machine name "witherspoon". This
will then install the witherspoon machine JSON config files into the
tacoma image.
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I6ce40547ebe536ca149930c439b0ee21d66061fb
|
|
The `p10bmc` machine's JSON config files should now use the JSON config
files installed from the repository.
Change-Id: Ibd9bbc055e4d00a5f799a291e9fd3a9955d774c5
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
The `witherspoon` and `p10bmc` machines' JSON config files should now
use the JSON config files installed from the repository.
Change-Id: I47669745aa7047c4de64ee8aedc98437593a3b62
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
The `witherspoon` and `p10bmc` machines' JSON config files should now
use the JSON config files installed from the repository.
Change-Id: Ie40264435ca5278a50f2aa3c688d882d72cb376b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
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>
|
|
Witherspoon uses a specialized phosphor-fan-control@.service file and
uses the phosphor-fan-control-init@.service file still to just set the
fans ready target. To correctly be included in the FILES directive,
these services need to be explicitly added on wiherspoon machines.
Change-Id: I76129a7833337aaf74fd83b0e28f3083f1a41b0a
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built rainier and verified the fan files were installed, ex:
obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,rainier-4u/zones.json
obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,rainier-2u/zones.json
obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,everest/zones.json
Change-Id: I10edb9e30716cffa3f510fe94822eadb08326912
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The 1s4u is just like the 2s4u except it has two less fans.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I56ed73ee573df250072bd014a0e4c8a4072e974e
|
|
The 1s4u is just like the 2s4u except it has two less fans.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I35333e49c883fb9ac8c84223545fe3b903a66d7d
|
|
This application resides in the phosphor-fan-presence repo and creates
phosphor-logging based event logs for temperature threshold alarms.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Id5a7ce7590efe82eb1f9615853cabd58ac269c24
|
|
This will start phosphor-fan-presence at the multi-user target. It
doesn't need to know about the power state when just checking GPIOs and
tach sensors, so let it run all the time. It also avoids a race
condition with phosphor-fan-monitor if it starts earlier.
This commit also adds a JSON vs YAML packageconfig so service files can
be installed to different places based on how it is configured. And
since the service file has different contents based on when it starts,
the phosphor-fan-presence-tach@.service file was moved into the repo so
that the repo itself can determine which one to install based on how the
JSON vs YAML configuration option is set.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I4c00f0854974c70efb5097d0344c45385dbcb085
|
|
Install all the fan application config files into a rainier image
(From meta-ibm rev: dd3117e5c3b6768ca6975b04ebc70f8e716529b2)
Change-Id: I51d017b3a6ad34595bc9dce0fd1693c0012fc52e
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Use the latest bumped upstream commit of the phosphor-fan-presence repo.
(From meta-ibm rev: a5824115356901e363c55f0d013a9821a51eba1b)
Change-Id: Ib5f3e4718de3f288bf71321680d42234512d1be9
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Witherspoon should still use YAML based configs for fan control instead
of JSON. Once all of fan control's JSON support is available and
witherspoon's YAML fan configs are converted to JSON, this can be
removed to enable JSON.
*Temporarily pin to 8e1b382122fed73e788d44f3a67cecbfbcc6972e to pass CI
(From meta-ibm rev: 7ec9b860b5ea1d986702bb978b528ddcd28f2ce5)
Change-Id: Ic31f5ab915d5478b9a2027732bd3ffd44f50b02f
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
In prep for switching the witherspoon machine over to using a runtime
fan monitoring JSON configuration, install the configuration file into
the image now.
Tested:
Verified both `monitor.yaml` and `config.json` in phosphor-fan
Built/installed witherspoon image and config.json file present
Verified YAML config still used instead of present JSON config
(From meta-ibm rev: 36206800a699a1429d30ad32a36e4f960ac6c7b4)
Change-Id: I75d72a2731f201d37d38c9d436eff2af522bc6da
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Configure the fan monitor and fan control services to be protected by
the fan watchdog. In the event that any of those services fail to run
on the BMC, the fan watchdog would trip and push fans to 100% PWM.
(From meta-ibm rev: 0860865b6c1003d5440a2be4990fc399931be92c)
Change-Id: I6be11de61cae544089553f8791cf599f98ca04f6
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
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>
|