summaryrefslogtreecommitdiff
path: root/meta-ibm
AgeCommit message (Collapse)AuthorFilesLines
2021-04-01ibm: dbus-interfaces: Replace rainier with p10bmcAdriana Kobylak1-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I7bfbbf2310be78a2ae601047710204f5fb9f0da0 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: obmc-console: Replace rainier with p10bmcAdriana Kobylak4-8/+8
The IBM rainier machine name is being replaced with the generic p10bmc. Tested: Built rainier and verified the console files were installed: rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/obmc-console/ Change-Id: Ida1010ae6c6c0e1eecf2b62521c06bfe055b0d88 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: settings: Replace rainier with p10bmcAdriana Kobylak2-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I3947988f73e601ca281b6222a6116bc7f50c8c32 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: skeleton: Replace rainier with p10bmcAdriana Kobylak1-0/+0
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: Id9cbde5f3ccc505635c37c8ffd92efef191e9320 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: logging: Replace rainier with p10bmcAdriana Kobylak1-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I9fa2bb6f199144816bd9d90405afe4fba36fc575 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: software-manager: Replace rainier with p10bmcAdriana Kobylak1-4/+4
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: Iba75dcfe5eee66bcb0afb5a01feddbf26b2c7988 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: host-postd: Replace rainier with p10bmcAdriana Kobylak1-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I430e6ed6bf006a114e185d4adb507d1c5c6e2cd4 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: gpio-monitor: Replace rainier with p10bmcAdriana Kobylak5-2/+2
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>
2021-04-01ibm: rainier: Add p10bmc as MACHINEOVERRIDESAdriana Kobylak1-0/+1
The IBMC POWER10 systems will have a common BMC image, therefore there will be a transition to move from the 'rainier' system name to the generic 'p10bmc' name. This will be done in two stages. The first one is to create a p10bmc MACHINEOVERRIDES and replace the rainier conditionals with p10bmc. Once that's done, the rainier.conf will be replaced with p10bmc.conf. Change-Id: Ic499d36dd7f74a8b7f4a44723f76d1e344e15a32 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-03-30leds: rainier: Create virtual physical LEDsVishwanatha Subbanna3-1/+45
These virtual physical LEDs are a mirror of real enclosure fault and enclosure Identify physical LEDs. However, these virtual LEDs are needed to be able to communicate the effective state of the enclosure fault and enclosure identify LEDs during lamp test. During lamp test, real physical enclosure fault and enclosure id LEDs should not be updated and they must be updated only after the lamp test finishes. However, Hypervisors would need to know the effective state of enclosure level fault and identify LEDs and that problem is resolved by these virtual LEDs. Once the lamp test finishes, these virtual physical LEDs would again be in sync with real enclosure fault and Identify LEDs. Tests: root@bmc:/lib/systemd/system/multi-user.target.wants# busctl tree xyz.openbmc_project.LED.Controller.virtual_enc_fault └─/xyz └─/xyz/openbmc_project └─/xyz/openbmc_project/led └─/xyz/openbmc_project/led/physical └─/xyz/openbmc_project/led/physical/virtual_enc_fault root@bmc:/lib/systemd/system/multi-user.target.wants# busctl tree xyz.openbmc_project.LED.Controller.virtual_enc_id └─/xyz └─/xyz/openbmc_project └─/xyz/openbmc_project/led └─/xyz/openbmc_project/led/physical └─/xyz/openbmc_project/led/physical/virtual_enc_id root@bmc:/lib/systemd/system/multi-user.target.wants# busctl get-property xyz.openbmc_project.LED.Controller.virtual_enc_fault /xyz/openbmc_project/led/physical/virtual_enc_fault xyz.openbmc_project.Led.Physical State s "xyz.openbmc_project.Led.Physical.Action.Off" root@bmc:/lib/systemd/system/multi-user.target.wants# busctl set-property xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/ddimm0_identify xyz.openbmc_project.Led.Group Asserted b true root@bmc:/lib/systemd/system/multi-user.target.wants# busctl get-property xyz.openbmc_project.LED.Controller.virtual_enc_id /xyz/openbmc_project/led/physical/virtual_enc_id xyz.openbmc_project.Led.Physical State s "xyz.openbmc_project.Led.Physical.Action.On" root@bmc:/lib/systemd/system/multi-user.target.wants# busctlset-property xyz.openbmc_project.LED.GroupManager /xyz/op_ebmc_project/led/groups/ddimm0_identify xyz.openbmc_project.Led.Group Asserted b false root@bmc:/lib/systemd/system/multi-user.target.wants# busctl get-property xyz.openbmc_project.LED.Controller.virtual_enc_id /xyz/openbmc_project/led/physical/virtual_enc_id xyz.openbmc_project.Led.Physical State s "xyz.openbmc_project.Led.Physical.Action.Off" Change-Id: Ic0ee5b0f376911650d5489d8bb84a4e83247190f Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-03-26ledmanager: Remove phosphor-led-manager-ledmanager packageVishwanatha Subbanna1-4/+4
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>
2021-03-25Inventory: rainier: Add LED group associations to Inventory objectsVishwanatha Subbanna2-5/+5408
This commit adds below forward and reverse associations "rType": "fault_inventory_object", "fType": "fault_led_group" "rType": "identify_inventory_object", "fType": "identify_led_group" Change-Id: Icaad89e6e690c3c0a635362e8c604874bc3f37fe Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-03-25ibm: Add TMP401 driver to RainierMatt Spinler1-0/+1
This driver supports the TMP435 temperature sensor, which is used on 2 IBM manufactured PCIe cards, an NVME JBOF riser, and a PCIE gen 4 CXP cable card. The former only plugs into Rainier, and the latter into Rainier and Everest. The TMP435 devices on these cards are powered by slot power, controlled by the hypervisor, and so will not be accessible until the hypervisor has started and has turned on slot power. Note that the sensor instances for these cards will not be in the device tree because they are monitored by the hwmontempsensors application which gets its configuration information from the entity-manager application. Entity-manager uses the 'new_device' API to instantiate drivers, which does not need device tree entries. In fact, if these are in the device tree, then the new_device write will fail even though the device driver wasn't truly bound to that instance. As mentioned above, because they are on slot power they cannot be probed as usual on kernel startup. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I8aab28266f4e4b492c8d1c0c256714439ef1b5cd
2021-03-251s4u: support presence config.json for new systemAndrew Geissler2-0/+90
The 1s4u is just like the 2s4u except it has two less fans. Tested: - Booted up system with entity-manager loading rainier-1s4u config and verified fan applications found and loaded new 1s4u files and system was able to chassis power on. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I575a63edb242c1b94e1a6f1eafd86a96e4518e37
2021-03-251s4u: support zones.json for new systemAndrew Geissler2-0/+13
The 1s4u is just like the 2s4u except it has two less fans. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I56ed73ee573df250072bd014a0e4c8a4072e974e
2021-03-251s4u: support fans.json for new systemAndrew Geissler2-0/+30
The 1s4u is just like the 2s4u except it has two less fans. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I35333e49c883fb9ac8c84223545fe3b903a66d7d
2021-03-251s4u: fan-monitor support for new systemAndrew Geissler2-0/+94
The 1s4u is just like the 2s4u except it has two less fans. Thermal profiling may change some of the variable but for now just use the same as the 2s4u. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iab3fd9d1699de779c242bb42456d976697b4da14
2021-03-24kexec: Added to Witherspoon-Tacoma & Rainier imagesBruce Mitchell1-2/+2
For implementing kdump Witherspoon-Tacoma and Rainier kexec is needed. This was done by pulling kexec-tools package into the build. Tested: I successfully build each Witherspoon-Tacoma and Rainier booted each in QEMU and manually verified kexec with no parameters showed the version and help. Presently the kernel's SMP is missing HOTPLUG so further testing of kexec utility is not possible. Signed-off-by: Bruce Mitchell <Bruce.Mitchell@ibm.com> Change-Id: I253dd3e0c46987070b5c252dcd5ab6008b3b09d3
2021-03-24leds: rainier: lamptest: Enable lamp test feature for rainier systemVishwanatha Subbanna1-1/+2
This commit enables phosphor-ledmanager to do lamp test Change-Id: I4933ec034911198f99ae1289f681f15057310c33 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-03-24leds: rainier: Enable PACKAGECONFIG to use jsonVishwanatha Subbanna1-0/+3
This enables phosphor-ledmanager to use JSON configuration file Change-Id: I3cbd0bf6b60e81f9f0a479ad51dab438c708c6c1 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-03-22openbmc: add meta-security layerAnton D. Kachalov3-0/+6
This layer provides libseccomp. Signed-off-by: Anton D. Kachalov <gmouse@google.com> Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
2021-03-22Override the snoop device name to empty for IBM systemsManojkiran Eda1-0/+2
- We have already made the change to make the snooping port optional, which means that snoopd daemon can still run and host the interfaces & Postcode Raw Value property even on the systems with no snooping port. - The intent behind this commit is to over ride the snoop-device name to empty from the meta-ibm layer so that the snoopd daemon will run without the support for snooping port on ibm machines. Tested: - Build images for witherspoon-tacoma & rainier, and made sure the snoopd service runs without any issues. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I622a903f9084a9b94561c1202f8c637d30062112
2021-03-09Correction in debug-collector recipePriyangaRamasamy1-1/+1
For installing gendumpheader plugin, the recipe was including all files from tools/dreport.d/ibm.d. Corrected it to take only gendumpheader plugin so that it wont conflict with installation of other plugins from same directory. Signed-off-by: PriyangaRamasamy <priyanga24@in.ibm.com> Change-Id: I5a1358f07aba6997cb9ae84dba59b3420c7ce968
2021-03-09Rainier: Add a presence to bind delay of 1500msBrandon Wyman4-0/+4
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>
2021-03-09Package phosphor-host-postd for tacoma & rainierManojkiran Eda1-2/+2
- The intent behind this commit is to pull the snooping daemon into tacoma & rainier. - This daemon is used for hosting the necessary dbus interface & Raw Value property for the pldm to write the progress codes into. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I4730046a40345d74d53b19a5058e8e45d2d40e8f
2021-03-03rainier: Add inventory associations JSON filesMatt Spinler4-2/+425
The phosphor-inventory-manager application supports creating associations based on JSON files, where the JSON files have conditions built into them that say which inventory-manager property values are required for the associations files to be valid. Add minimal associations files for the Rainier 2U, Rainier 4U, and Everest systems that just contain the fan inventory associations for now. The condition is the 'IM' property on the com.ipzvpd.VSBP interface on the system/chassis/motherboard path. Change-Id: Ib6807d8982a2efeb94692b917804c53965d6c98a Signed-off-by: Matt Spinler <spinler@us.ibm.com>
2021-03-02wspoon: Add fan monitor start delayMatt Spinler1-0/+4
Now that phosphor-fan-monitor starts at multi-user instead of the fans-ready target, it needs a JSON config option to let it know when to start monitoring after the fans have ramped up. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: If8eef303ee585dd30b3fbe9764a624eeab3b1a8a
2021-03-02native class is not inherited lastJoseph Reynolds4-4/+4
Moved "inherit native" statements to the last position to remove QA Issues. The message is: WARNING: QA Issue: {RECIPENAME}: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: {CLASSFILES} [native-last] Tested: The witherspoon image builds without the warnings. Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net> Change-Id: Ic3c71234abfcac8b26478bc32808e3bec8bba810
2021-03-01Remove phsophor-gpio-keys as a standalone featureJoel Stanley1-1/+0
The feature was implemented as an append to the kernel (BSP) layers in meta-phsophor. This created a three way dance between machine layers, BSP and meta-phosphor, when it should have been the kernel layer providing this feature and machines could then opt in. Fixing this means we could remove the KERNEL_DANGLING_FEATURES_WARN_ONLY workaround. As the feature is simply turning on a pair of kernel options without any other impact, we can implement it by adding the options to our defconfigs. In fact, aspeed and hpe kernel configurations enable the two kernel options: $ git grep CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_KEYBOARD_GPIO=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_KEYBOARD_GPIO=y $ git grep CONFIG_INPUT_EVDEV meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_INPUT_EVDEV=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_INPUT_EVDEV=y Other machines that wish to enable this feature should ensure it is added to their BSP's defconfig, or add it to their machine specific defconfig. Change-Id: I0726836319022f96c1d13d4a0cbd73708047302c Signed-off-by: Joel Stanley <joel@jms.id.au>
2021-02-26Package post-code-manager for rainier & tacomaManojkiran Eda1-2/+2
- This commit would package the post-code-manager deamon support for tacoma & rainier machines. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ieea0b1516419d8cde2b93126fb278ffa16f0c15d
2021-02-25openssl: move to DEPRECATED_CRYPTO_FLAGSAndrew Geissler1-2/+2
Upstream recipe moved the disabling of deprecated crypto algorithms into a new DEPRECATED_CRYPTO_FLAGS variable. (Klaus: also adjust phosphor's EXTRA_OECONF for this package to not double-disable already obsolete ciphers) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I75e2c35ada37c9510a0af347772cdeb2b23d99e9 Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
2021-02-25ibm: Install sensor-monitor on rainierMatt Spinler2-2/+3
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
2021-02-25ibm: Start phosphor-fan-presence at multi-userMatt Spinler1-2/+3
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
2021-02-25hypervisor: introduce new package for state managerAndrew Geissler1-0/+5
This new phosphor-state-manager package allows a user to track the state of their hypervisor firmware. This new software utilizes the BootProgress property to determine the hypervisor state and relies on a different software entity (for example PLDM) to monitor state requests and send the appropriate messages to the hypervisor firmware. Includes the autobump which has the new function: phosphor-state-manager: srcrev bump 58477b5287..75f38ee42d Andrew Geissler (3): hypervisor: state management support hypervisor: monitor boot progress hypervisor: reset requested host state on power off Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I4c4bfc06db3b38b114c28692db808cffceff628a
2021-02-25meta-ibm: Add rainier to example build invocationsJoel Stanley1-0/+2
This is the configuration that CI builds. Signed-off-by: Joel Stanley <joel@jms.id.au> Change-Id: Ib9b2ccc554f7ca2c602cec57a300416105791412
2021-02-23phosphor-tiny: remove distro settingPatrick Williams1-1/+0
This distro feature is not used anywhere. Remove it to reduce the clutter. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I1dd4e5ae52197a377b552a8a0e7d1e6d7e7ebe7f
2021-02-20romulus: remove empty distro indirectionPatrick Williams2-3/+2
Most openpower machines use DISTRO="openbmc-openpower" but Romulus has a "openbmc-romulus" distro config file. This config file has nothing except an inclusion of the openpower one, so remove this useless indirection. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I371ce4137369e4964eed1529f8a8190e31721ecc
2021-02-19meta-ibm:everest: Remove inlet rotors from trust groupsMatthew Barth1-16/+0
Fan monitoring should not need the inlet rotors included in the nonzero speed trust group. This causes the nonfunctional timer to start for these rotors and immediately stop since they are never actually taken into account in the determination of trust. Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Change-Id: I411faab9dcd67fa2409f6be39be54969a0eb2520
2021-02-19meta-ibm:rainier-2u: Remove inlet rotors from trust groupsMatthew Barth1-24/+0
Fan monitoring should not need the inlet rotors included in the nonzero speed trust group. This causes the nonfunctional timer to start for these rotors and immediately stop since they are never actually taken into account in the determination of trust. Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Change-Id: I043f1003319e84e3c93b59f80963525d9d7d4eac
2021-02-16Remove bios configurations from meta-layer & bumpManojkiran Eda5-108/+1
- The intent behind this commit is to enable & set OEM specific options to pldm recipe via the meta-ibm layer. - pldm in its current state, has a configurations folder which contains all the configurations that are consumed by the daemon at runtime. - pldm also has an oem folder(s) that can contain the vendor specific configuration files. - So, removing these files from the meta-layer as they are obsolete. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I91d23c37abff45f3da18676269be843610b6a9d1
2021-02-10sched-host-tran: enable in ibm imagesAndrew Geissler1-0/+5
The plan on IBM systems is that the host software will communicate via PLDM which will utilize the D-Bus properties provided by this function. Note that the new D-Bus interfaces provided by this function could also be supported via Redfish. The PowerOnDelaySeconds and PowerOffDelaySeconds properties within the ComputerSystem object would map to what's provided here. There are no plans currently to do this though as IBM's only use case is controlling this function via the in-band PLDM interface. Tested: - Verified the generated image had scheduling service and function worked as expected scheduling a power on then power off Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I781dfba0871853feafed49faa72bf1c05f657d85
2021-02-04mpreboot: add to rainier and tacoma systemsAndrew Geissler2-0/+2
Both rainier and witherspoon-tacoma systems support the mpreboot feature. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ieeb4724a5cf5678ba0f6ab950b5403db5aebcd88
2021-02-04mpreboot: introduce new distro featureAndrew Geissler1-0/+3
The memory preserving reboot is a feature utilized on IBM systems which allows a system to be rebooted with its memory preserved. This is utilized in situations where the host firmware has crashed and put the processor in an unusable state. The processors are put back in a good state by rebooting the system. Memory is preserved though so host firmware can capture the relevant data from memory needed to debug the cause of the failure. This feature is implemented across a few different repositories within OpenBMC so lets create a distro feature to enable it across all of the software stacks. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ia16626ba6e46aa8de642abef677735ed957f9f9e
2021-01-31meta-phosphor: Add ibmtpm2tss recipe to rainier and witherspoon-tacomaKlaus Heinrich Kiwi2-1/+6
The ibmtpm2tss tools are required to use the Nuvoton NPCT750A TPM from userland. The ibmtpm2tss package also required OpenSSL camellia support, so remove the override disabling that for those two machines. Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com> Change-Id: Ifc0afc58f4a31ea4b6d1750d470738d0d0e82754
2021-01-31meta-ibm: Add meta-security layerKlaus Heinrich Kiwi1-0/+2
There are some machines (Witherspoon-Tacoma and Rainier) that have a TPM device, which will be used eventually. We need access to the recipes in this layer. Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com> Change-Id: I3b10ee4d39a69e651a790ae3238e39c45e21ce72
2021-01-29Package biosconfig-manager for rainier & TacomaManojkiran Eda1-2/+2
- This commit would package the biosconfig-manager for both tacoma & rainier machines. Tested By : - With the changes booted the tacoma machine & observed that the biosconfig-manager services are up & runnning Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I90542368a70284c97e1f33d29770c751a61631ca
2021-01-28pldm: Add squashfs-toolsAdriana Kobylak1-3/+2
The squashfs tools are used by PLDM during inband update. Reference: https://gerrit.openbmc-project.xyz/c/openbmc/pldm/+/37510 Tested: Verified that the rootfs/usr/sbin/mksquashfs existed. Change-Id: Id8d00765e72ce04bc8f039403a570aa7dca98b26 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-01-28meta-ibm: Use fan-monitor for fan errorsMatt Spinler4-3/+123
Instead of using phosphor-dbus-monitor to create errors and handle power offs for fan errors, use phosphor-fan-monitor instead, now that it has the functionality. To do this, add the new rules to the fan monitor config files, and remove the phosphor-dbus-monitor fan rules files. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ia03186132f04087be76d2fd43412c37698407f60
2021-01-28phosphor-ipmi-config: Handle an empty commit numberAdriana Kobylak1-3/+7
The VERSION_ID may not have a commit number for the cases a tag is created, ex: 2.10.1. Since the code is expecting a commit number of 1-4 digits, use a '0' if no commit number exists. Tested: Created a tag 2.10.99 which sets VERSION_ID=2.10.99. Without this change, build fails with: "Exception: IndexError: list index out of range" With this change there are no build errors. Change-Id: I3b56ebc1844ec6748b92cca3484f9aa1f4d983f8 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-01-28add geissonator as maintainer to ibm layersAndrew Geissler2-0/+2
I've been utilizing my gerrit admin abilities to merge autobumps and backup Brad in these meta layers. The OWNERS plugin disabled this path for me. My intention is to keep with this same workflow. I'll merge autobumps and backup Brad as needed. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ib248c6122644dbbd4b024ed07eb7259db85daf1e
generated by cgit v1.2.3 (git 2.39.0) at 2024-08-24 18:32:56 +0300