summaryrefslogtreecommitdiff
path: root/meta-ibm
AgeCommit message (Collapse)AuthorFilesLines
5 daysmeta-ibm: system1: Add bios version packageAsmitha Karunanithi4-0/+97
This commit includes changes to update the bios version flashed in x86 PCH SPI flash. The version is updated in the dbus as well and cached for later use to avoid reading SPI flash subsequently. This service is started after "xyz.openbmc_project.Software.Version.service", typically during boot or when flashing a host firmware via BMC to update version information. Tested By: Built openbmc, and verified that the service is installed on the bmc. The host firmware version is updated on the dbus [1] and updated in the `/var/cache/bios_version` file, when PCH is in standby. [1] busctl get-property xyz.openbmc_project.Software.BMC.Updater /xyz/openbmc_project/software/bios_active xyz.openbmc_project.Software.Version Version Change-Id: Ic7b4bb1250b8f1b8fc62fc7fd46654375937a459 Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com>
10 daysmeta-ibm: Add MAXVALUE to fan hwmon configsMatt Spinler4-0/+36
Add this so that phosphor-hwmon fills in the MaxValue D-Bus property with the values. This will be used in upcoming Redfish work. Tested: ``` The fanX_0 values: $ for i in {0..5}; do busctl get-property xyz.openbmc_project.Hwmon-75e29b8640dca44a8648ec8aeb240d520bd5eb91b19a8ebe4bbc48ef236d856c.Hwmon1 \ /xyz/openbmc_project/sensors/fan_tach/fan$i"_0" xyz.openbmc_project.Sensor.Value MaxValue; done d 18000 d 18000 d 18000 d 18000 d 18000 d 18000 The fanX_1 values: $ for i in {0..5}; do busctl get-property xyz.openbmc_project.Hwmon-75e29b8640dca44a8648ec8aeb240d520bd5eb91b19a8ebe4bbc48ef236d856c.Hwmon1 \ /xyz/openbmc_project/sensors/fan_tach/fan$i"_1" xyz.openbmc_project.Sensor.Value MaxValue; done d 18000 d 18000 d 18000 d 18000 d 18000 d 18000 ``` Change-Id: Id33cf407a427ff2d23083078b7eaea9265cb8359 Signed-off-by: Matt Spinler <spinler@us.ibm.com>
11 daysmeta-ibm: system1: add phosphor-software-managerAndrew Geissler1-0/+8
phosphor-software-manager is required to pull in the new bios-version functions. Change-Id: Ic4987fcda81ce56cf9f5af59986663ed8ce70cce Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
13 daysmeta-ibm: Remove forward_pass in GoogleAuth configAsmitha Karunanithi1-1/+1
Modified the PAM configuration for Google Authenticator by removing the 'forward_pass' option. This change ensures that TOTP is no longer passed to subsequent modules. Change-Id: Id167c2ac2d9309da4e7393e64d778280fbf0334f Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com>
2024-09-11meta-ibm: system1: Turn on serial GPIO configNinad Palsule1-0/+1
Turn on SGPIO config for the IBM system1 bmc. system1 bmc uses it to query fpga for example fault status. Change-Id: I19a5e87a252ce7b8f21235edfed079c8d98d9f93 Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
2024-09-10meta-ibm: Include google-auth PAM config filesAsmitha Karunanithi3-0/+56
This commit installs custom versions of common-auth, common-account that enables google authenticator pam configuration. Tested By: * Verified that PAM config files are installed based on the distro feature enablement Change-Id: Ifa721907b7f56847444edca3c5f2428ac3793583 Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com>
2024-09-10meta-ibm: Enable new hypervisor system optionGunnar Mills1-0/+2
bmcweb is introducing a new hypervisor computer system meson option. We use this hypervisor system to get/change the state of the hypervisor and to get/set the hypervisor ethernet interface. bmcweb is moving to meson option to reduce a call on non-ibm systems and to move forward with the multihost stuff. See the bmcweb commit for more info: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/73891 Tested: I built this with 73891 and see the hypervisor system. { "@odata.id": "/redfish/v1/Systems", "@odata.type": "#ComputerSystemCollection.ComputerSystemCollection", "Members": [ { "@odata.id": "/redfish/v1/Systems/system" }, { "@odata.id": "/redfish/v1/Systems/hypervisor" } ], "Members@odata.count": 2, "Name": "Computer System Collection" } Change-Id: Iffc01d60f79914cd8261a1c2c1b97e817947e12e Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
2024-09-05Add Google Authenticator PAM module for 2FAAsmitha Karunanithi2-0/+2
Google authenticator PAM module enables two-factor authentication for logging in to servers. It provides both HMAC-based and Time-based OTPs as the second factor on top of usual password authentication. This commit adds a new distro feature for google authenticator and can be enabled or disabled for any machine based on the requirement. Tested By: * Built openbmc for p10bmc * Verified that the google-authenticator was pulled and the binary is installed Change-Id: I586715a924eddd90c9cb6f967db35824767330ca Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com>
2024-09-04meta-ibm: Add a chrony configuration filePavithra Barithaya2-0/+46
The huygens machine is based on the new pstbmc machine family from IBM. It will be our first redundant BMC system [1]. This new system expects to have chrony daemon to run along with the existing systemd- timesyncd deamon. The commit adds a custom chrony configuration file in order to achieve syncing of time between redundant BMCs. [1]: https://gerrit.openbmc.org/c/openbmc/docs/+/70233 Tested: Configuration file is updated. Change-Id: I6fb6787055bdfc423ef439c43b9c17db679d062f Signed-off-by: Pavithra Barithaya <pavithrabarithaya07@gmail.com>
2024-09-04meta-ibm: Add SMBIOS support in meta-system1Asmitha Karunanithi3-0/+4
This commit pulls: 1. smbios-mdr recipe that is responsible for parsing the smbios table sent down by the host, and publishes the system information on the dbus objects. 2. phosphor-ipmi-blobs: this is an alternative implementation of IPMI blob transfer API. The blob handler writes the data into `/var/lib/smbios/smbios2` path (the local persistent cache for the SMBIOS table) and triggers smbios-mdr to reload and parse the table from that file. Tested By: Verified that the smbios data is transferred via IPMI to the BMC and the smbios-mdr service reads that data and populates the dbus object. Change-Id: I7eb54695c46cd8d0392b8ce7c942fedeb56b5d14 Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com>
2024-09-03linux-aspeed: Rename APB nodes, PT5161L support, Catalina updatesAndrew Jeffery56-336/+63
The notable change is to the phosphor-hwmon configuration paths for all Aspeed-based platforms. The changes were generated with the following incantations: ``` git ls-files -- :/:*/ahb/apb/bus@1e78* | while read -r S; do D="$(echo $S | sed -E 's|ahb/apb/bus@1e78a000/i2c-bus|ahb/apb@1e780000/bus@1e78a000/i2c|')"; mkdir -p "$(dirname "$D")"; git mv "$S" "$D"; done git ls-files -- :/:*/ahb/apb/pwm-tacho-controller@1e786* | while read -r S; do D="$(echo "$S" | sed -E 's|ahb/apb/pwm-tacho-controller@1e786000|ahb/apb@1e780000/pwm-tacho-controller@1e786000|')"; mkdir -p "$(dirname "$D")"; git mv "$S" "$D"; done sed -Ei 's|ahb/apb/|ahb/apb@1e780000/|g' meta-ibm/meta-palmetto/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-ibm/meta-romulus/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-ibm/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-ingrasys/meta-zaius/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-quanta/meta-f0b/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-quanta/meta-q71l/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend sed -Ei 's/i2c-bus@/i2c@/g' meta-ibm/dynamic-layers/meta-openpower/recipes-phosphor/vpd/openpower-fru-vpd_%.bbappend meta-ibm/meta-palmetto/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-ibm/meta-romulus/recipes-phosphor/logging/files/callouts.yaml meta-ibm/meta-romulus/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-ibm/recipes-phosphor/chassis/vrm-control/ibm-ac-server/ir35221-unbind-bind.sh meta-ibm/recipes-phosphor/fans/phosphor-fan-presence-config/swift/config.yaml meta-ibm/recipes-phosphor/logging/ibm-logging/ibm-ac-server/policyTable.json meta-ibm/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-ingrasys/meta-zaius/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-quanta/meta-f0b/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend meta-quanta/meta-q71l/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend sed -Ei 's|/ahb:apb/|/1e780000.apb/|g' $(git grep -lE 'ahb:apb/.*1e78') sed -Ei 's|ahb:apb:i2c@1e78a000|1e780000.apb:bus@1e78a000|g' $(git grep -l ahb:apb:i2c@1e78a000) sed -Ei 's|ahb:apb|1e6e0000.apb|g' meta-phosphor/recipes-phosphor/video/uart-render-controller/uart-render-controller.service git ls-files -- :/:meta-ibm/*/ahb--apb/* | while read -r S; do D="$(echo "$S" | sed -E 's/ahb--apb/1e780000.apb/g')"; mkdir -p "$(dirname "$D")"; git mv "$S" "$D"; done; sed -Ei 's/ahb--apb/1e780000.apb/g' $(git grep -l ahb--apb -- meta-ibm) git ls-files -- :/:*i2c-bus* | while read -r S; do D="$(echo "$S" | sed -E 's/(1e78a..0).i2c-bus/\1.i2c/g')"; mkdir -p "$(dirname "$D")"; git mv "$S" "$D"; done; sed -Ei 's/(1e78a..0).i2c-bus/\1.i2c/g' $(git grep -lE '(1e78a..0).i2c-bus') ``` What couldn't be automated was cleaning up the ibm-logging policy table, which had many duplicate keys that needed manual inspection to remove. It's worth noting that even for the remaining, non-duplicate keys, the sysfs paths are not correct: The physical address of the I2C controllers needs to map to the assigned device index, but in the file they all have address 1e78a100 despite changes to the device index. From eslint in CI: ``` meta-ibm/recipes-phosphor/logging/ibm-logging/ibm-ac-server/policyTable.json 9999:10 error Duplicate object key json/* 10020:10 error Duplicate object key json/* 10041:10 error Duplicate object key json/* 10062:10 error Duplicate object key json/* 10083:10 error Duplicate object key json/* 10104:10 error Duplicate object key json/* 17097:10 error Duplicate object key json/* 17118:10 error Duplicate object key json/* 17139:10 error Duplicate object key json/* 17160:10 error Duplicate object key json/* 17181:10 error Duplicate object key json/* 17202:10 error Duplicate object key json/* 17223:10 error Duplicate object key json/* 17244:10 error Duplicate object key json/* 17265:10 error Duplicate object key json/* 17286:10 error Duplicate object key json/* 17307:10 error Duplicate object key json/* 17328:10 error Duplicate object key json/* 17349:10 error Duplicate object key json/* 17370:10 error Duplicate object key json/* 17391:10 error Duplicate object key json/* 17412:10 error Duplicate object key json/* 17433:10 error Duplicate object key json/* 17454:10 error Duplicate object key json/* 19575:10 error Duplicate object key json/* 19596:10 error Duplicate object key json/* ``` Andrew Jeffery (1): ARM: dts: aspeed: Rework APB nodes Cosmo Chou (3): dt-bindings: vendor-prefixes: add asteralabs dt-bindings: trivial-devices: add Astera Labs PT5161L hwmon: Add driver for Astera Labs PT5161L retimer Potin Lai (2): ARM: dts: aspeed: catalina: add pdb cpld io expander ARM: dts: aspeed: catalina: update io_expander7 & io_expander8 line name Rob Herring (Arm) (1): arm: dts: aspeed: Use standard 'i2c' bus node name Change-Id: I32ca7579eabd59ed20da3f481da687589a361763 Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
2024-08-28update configurations for phosphor-led-managerAlexander Hansen4-0/+298
phosphor-led-manager no longer assumes any default led priority. The behavior was changed in https://github.com/openbmc/phosphor-led-manager/commit/5a9f651949c133ed0868d72734c4ac82c75a7656 and https://github.com/openbmc/phosphor-led-manager/commit/55badf7979f57d5f9ed2db726eebf35e84d0dac5 The led priority needs to be configured, so updating all configurations here. Before, led-manager assumed a default led priority of 'Blink'. So this patch is just making that explicit in the existing configurations. There should be no behavior change from this patch. Change-Id: I74aabb567ccf6682d56877f8bb42e636fc1746f6 Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
2024-08-22meta-ibm: Update ncsi-linkspeed serviceEddie James1-1/+1
The ncsi-netlink tool has changed, requiring the OEM command to be prepended to the payload. Signed-off-by: Eddie James <eajames@linux.ibm.com> Change-Id: I349a992360d35bc0703979adfcc62d96789bff85
2024-08-19meta-ibm: Add an override for chrony daemonPavithra Barithaya4-0/+60
The huygens machine is based on the new pstbmc machine family from IBM. It will be our first redundant BMC system [1]. This new system expects to have chrony daemon to run along with the existing systemd- timesyncd deamon. The purpose of installing chrony in rootfs is to run chrony only in time server mode so that it can allow other BMC to obtain time from it. This commit adds an override to the chrony configuration and allows us to run both the daemons as per our use case. [1]: https://gerrit.openbmc.org/c/openbmc/docs/+/70233 Tested: Both the daemons run parallely without any conflict. Change-Id: I9de73ab135977847121daabefaf81265000e371e Signed-off-by: Pavithra Barithaya <pavithrabarithaya07@gmail.com>
2024-08-01meta-ibm:Use device path for p10bmc hwmon configsMatt Spinler11-19/+11
With https://gerrit.openbmc.org/c/openbmc/phosphor-hwmon/+/72996, phosphor-hwmon can be told to use the device path as the path to the config file and not the OF_FULLNAME udev env var. Enable this option for the p10bmc image, and rename all of the config files in the image to be based on the device path. This is being done because the Rainier and Everest follow-ons, BlueRidge and Fuji, have a different name for the max31785 in the device tree, even though it shares the same fan card. With this change, the config files can be shared. This also deletes the Bonnell config file, because it is at the same device path as on Rainier but requires different contents. It will just be handled with something downstream. Tested: Things still show up on D-Bus: ``` $ busctl tree xyz.openbmc_project.Hwmon-75e29b8640dca44a8648ec8aeb240d520bd5eb91b19a8ebe4bbc48ef236d856c.Hwmon1 `- /xyz `- /xyz/openbmc_project `- /xyz/openbmc_project/sensors `- /xyz/openbmc_project/sensors/fan_tach |- /xyz/openbmc_project/sensors/fan_tach/fan0_0 |- /xyz/openbmc_project/sensors/fan_tach/fan0_1 |- /xyz/openbmc_project/sensors/fan_tach/fan1_0 |- /xyz/openbmc_project/sensors/fan_tach/fan1_1 |- /xyz/openbmc_project/sensors/fan_tach/fan2_0 |- /xyz/openbmc_project/sensors/fan_tach/fan2_1 |- /xyz/openbmc_project/sensors/fan_tach/fan3_0 |- /xyz/openbmc_project/sensors/fan_tach/fan3_1 |- /xyz/openbmc_project/sensors/fan_tach/fan4_0 |- /xyz/openbmc_project/sensors/fan_tach/fan4_1 |- /xyz/openbmc_project/sensors/fan_tach/fan5_0 `- /xyz/openbmc_project/sensors/fan_tach/fan5_1 ``` Change-Id: Ie413778b0383cc8115973337dd53d6aa06f45302 Signed-off-by: Matt Spinler <spinler@us.ibm.com>
2024-07-29meta-ibm: Remove local-tty from VUART0 configNinad Palsule1-1/+0
local-tty is used as a tty handler where the data read from VUART0 is copied. The local-tty was set to ttyS0 which is actually hypervisor console device. That means console server was writing data to hypervisor console which it read from VUART0. Remove local-tty variable from the config file same as prior releases. Change-Id: If5578a47d72acb3a622c934d4d8b0e21a9b4ada8 Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
2024-07-24meta-ibm:Install inventory association filesSunny Srivastava1-0/+6
The commit updates recipe to install inventory association files for BlueRidge and Fuji systems. Change-Id: I8bd7db8e54e03bf9647fe8c4177be3b7514ddfb0 Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
2024-07-17meta-ibm: system1: add GPIO for PHR buttonJinu Joy Thomas1-0/+5
Added the GPIO definition for the pin hole reset button based on the GPIO it is connected as seen in the schematics. Change-Id: I713417f72ebaf5e3df06997332d243b4fbe3b8a1 Signed-off-by: Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com>
2024-07-15meta-ibm: sbp1: virtual_sensor_config: Add SSB power sensorsPatrick Rudolph1-0/+2668
The SSB provide only current and voltage sensors, but no power sensors. Assume current and voltages are sampled at the same time and calculate the output power of each SSB by taking the voltage and current sensor as input. Tested: Confirmed that new sensors appear in webui and provide sane sensor readings. Change-Id: Idf187eb01e792ad3716c3ba62fc4792cd770568d Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
2024-07-15meta-ibm: sbp1: virtual_sensor_config: Update board input power sensorPatrick Rudolph1-23/+2
Use existing virtual sensor P380V_INPUT_POWER_TOTAL as total_power. Tested: Confirmed that board power is still working in webui. Change-Id: Ib844714a9b02b255a8439c785f2c559a6647955d Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
2024-07-15meta-ibm: sbp1: virtual_sensor_config: Add sensor HW groupsPatrick Rudolph1-0/+1187
Group sensors and sum the current sensor readings for: - CPUs - DIMMs - FANs - RulerDrives - AUX - NICs - PSUs - P12V (main power rail) Based on the current calculate the power used by the sensor groups. Tested: Confirmed that new sensors appear in webui and provide sane sensor readings. Change-Id: Ia1a03eadc3e75db0832431b48f3906a16d7cc38d Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
2024-07-15meta-ibm: sbp1: phosphor-virtual-sensor: Calculate input current for IR3826xPatrick Rudolph1-0/+486
The IR38263/IR38060 cannot measure the input current or input power, thus calculate it from the output power, output current and input voltage using predefined power offset and internal resistance. Tested: Confirmed that new sensors appear in webui and provide sane sensor readings. Change-Id: Ic2e75496da3609c14b11cf3f7eb94654a331d1c9 Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
2024-06-28meta-ibm: Add more FabricAdapter Port AssociationMyung Bae6-33/+309
A few example associations were added by [1]. This is to add additional or missing port associations between FabricAdapter and Port, and to fix some typos. The assocication is defined by https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/62881. Some FRU examples were added before via https://gerrit.openbmc.org/c/openbmc/openpower-vpd-parser/+/66540 These associations are used for bmcweb Port schema implementation. This also fixes Redfish Service Validator related to Cables & Ports. Tested: - Verify bmcweb Port schema under `/redfish/v1/Systems/system/FabricAdapters` - Verify the content of `/redfish/v1/Cables/` tree. - Redfish Service Validator passes on Cables & Ports [1] https://github.com/openbmc/openbmc/commit/9f0b0adcf1e79e676df0f879c5be4a7a1cb6cfa7 Change-Id: If047a672c99da54aaa12f5d0206d2dc0334590bf Signed-off-by: Myung Bae <myungbae@us.ibm.com>
2024-06-28meta-ibm: Reduce max log size for ibm-ac-serverNinad Palsule1-1/+0
ibm-ac-servers machine has tiny /var space hence we need to reduce its max console log size. This patch reduces the max console size to the default 16K from previous 256K. Change-Id: I437c7d6823780a80b14041473e97c8de7941b0f9 Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
2024-06-28meta-phosphor: Reuse dreport utility functionGopichand Paturi1-1/+1
install_dreport_user_script function is intended to be reused in meta-openpower layer. To enable this, the function is being moved to a bbclass which would be inherited in the openpower-debug-collector recipe in the meta-openpower layer. dreport.conf file is a variable, hence making it an argument to the function, so that other layer can give a custom dreport.conf as input. Tested: Verified that plugin scripts are getting installed from openpower-debug-collector repository and BMC Dump collection is successful. Change-Id: I8d13bc7e381cd1b957d5770926fb712165a07185 Signed-off-by: Gopichand Paturi <gopichandpaturi@gmail.com>
2024-06-28meta-ibm: p10bmc: disable deprecated power-thermalMyung Bae1-0/+1
Redfish service validator reports ``` 1 err.Edm.Decimal errors in /redfish/v1/Chassis/chassis/Power#/PowerSupplies/0 1 failProp errors in /redfish/v1/Chassis/chassis/Power#/PowerSupplies/0 1 fails errors in /redfish/v1/Chassis/chassis/Power#/PowerSupplies/0 ``` ``` curl -k -X GET https://${bmc}/redfish/v1/Chassis/chassis/Power { ... "PowerSupplies": [ { "@odata.id": "/redfish/v1/Chassis/chassis/Power#/PowerSupplies/0", ... "PowerInputWatts": -5.5, <--- ... }, ``` This power-thermal support had been being deprecated and thus this commit is to disable the deprecated power-thermal. With this, some information (PowerCap) would be missing on webui-vue[1]. Webui-vue would need to switch over to use these[2]. Tested: - The deprecated Power is no longer shown from `curl -k -X GET https://${bmc}/redfish/v1/Chassis/chassis` - Redfish Service Validator passes on Power [1] https://github.com/openbmc/webui-vue/blob/8841b7d463a5272a87faaa14cb103f778a772770/src/store/modules/ResourceManagement/PowerControlStore.js#L41 [2] https://gerrit.openbmc.org/q/topic:%22redfish-EnvironmentMetrics%22 Change-Id: I86e46ef74cdce1bc7dea994dced93bb432082774 Signed-off-by: Myung Bae <myungbae@us.ibm.com>
2024-06-28meta-ibm: PIM recipe update to not add empty AssetTagSunny Srivastava1-0/+1
Bitbake recipe file has been updated to skip creating system D-Bus path with empty "AssetTag" property at launch of phosphor-inventory-manager service. This change is required to avoid clearing of "AssetTag" value, every time PIM starts/re-starts. Change-Id: I42c58819f92872c3701bb13d9d3035963b838bfa Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
2024-06-17meta-ibm: disable insecure-tftp-update featureJagpal Singh Gill1-1/+0
Disable insecure-tftp-update feature since its not used anymore. Change-Id: I8ea8063d8519c845edbc537fc24be45dc2fcdd41 Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>
2024-05-16meta-ibm:blueridge: Add new association for BlueRidgeRekha Aparna2-0/+276
This commit adds new association between PCIe slot and PCIe device for BlueRidge 2U and 4U configurations Change-Id: I8a2724d5bf71af030f844321ae1122520df38a81 Signed-off-by: Rekha Aparna <vrekhaaparna@ibm.com>
2024-05-14meta-ibm: Enable system specific bios supportArchana Kakani1-1/+1
Enabling system specific bios support for IBM systems Tested: Poweron successful Change-Id: Iad41ca4c93a76b6357994650b970942910ad06de Signed-off-by: Archana Kakani <archana.kakani@ibm.com>
2024-05-14meta-ibm:blueridge: Add new Association JSON filesAlpana Kumari2-0/+9523
This commit is to add Association JSON files for BlueRidge 2U and 4U configurations. Change-Id: I15109e3583ea74a813ac8a54fcfb09f97972d0b3 Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
2024-05-10meta-ibm: add rainier-1s4u device treeAndrew Geissler1-0/+1
IBM 1s4u systems required a separate device tree with a few modifications on top of the standard rainier system. Change-Id: I50a713448b03238995057d40a3dda844661ed336 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2024-05-03Move bmcweb options to meta-ibmGunnar Mills1-10/+2
These options don't have anything to do with POWER architecture, they are ibm options so move them to meta-ibm. The options are: -Dredfish-dbus-log=enabled \ -Dhttp-body-limit=400 \ and control the body limit, allowing a larger code update image and the use of phosphor-logging. This gives the added bonus of all meta-ibm bmcweb options are in one place and removes these from 2 non-openpower, ibm systems. Tested: It builds. No other testing. Change-Id: Ief31f1bfd8a92720b43b4124c6b25c582231a558 Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
2024-04-23meta-ibm:Fuji:Update association fileRekha Aparna1-1/+1
The commit updates the IM value for Fuji system Change-Id: Id391d2754b6157faebc672e1b1f5fc0aa24c7457 Signed-off-by: Rekha Aparna <vrekhaaparna@ibm.com>
2024-04-23meta-ibm/meta-sbp1: Enable pull-ups on FM_CPU_SKTOCC_NPatrick Rudolph1-4/+4
Enable integrated pull-ups on FM_CPU_SKTOCC_N GPIOs. The previous generation had external pull-ups, while SBP1 does not. This wasn't noticed until now as: - Usually all CPUs are plugged, pulling the GPIO low - When a CPU is not plugged, the system behaves as normal This change fixes the webui presence status and prevents CPU VRs for empty sockets to be enabled, reducing the systems power draw. Change-Id: Ic25873ff3d1ac0d0100ad941f480c5a8ea85d411 Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
2024-04-22meta-ibm: bmcweb: enable redfish-queryGunnar Mills1-0/+1
insecure-enable-redfish-query controls the Redfish expand query parameter. Named insecure because "is experimental, and has not been tested against the full limits of user-facing behavior". Downstream we have done some testing with this enabled and measuring resource usage are okay with the results. webui-vue will use expand for sensor page, etc. Other query parameters such as only are not controlled by this option and already enabled. Change-Id: I8403129fabfbe0752c3b0e85bb2e8bd5ebea2aa0 Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
2024-04-19meta-ibm: introduce new huygens systemAndrew Geissler6-0/+36
The huygens machine is based on the new pstbmc machine family from IBM. It will be our first redundant BMC system [1]. The initial focus on this machine will be the redundant BMC feature. The simulation model we use will just be 2 BMCs initially. Due to this focus and simulation model, this commit strips out all of the host firmware and host processor related features. Tested: - Confirmed in our 2 BMC simulation model that both BMCs come to Ready and only the expected vpd services have failed - Confirmed network into the BMCs worked as expected [1]: https://gerrit.openbmc.org/c/openbmc/docs/+/70233 Change-Id: Ieb42337980c0ec39d16c492c77810473d5105aa0 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2024-04-16meta-ibm: Enable emergency/rescue when root lockedShawn McCarney2-0/+16
When the root account is locked, the systemd emergency and rescue targets fail with an error message. That is because they run the sulogin command, which prompts for the root password. The solution is for those services to specify the sulogin --force option. For more information, see sulogin(8). systemd uses a "wrapper" executable named systemd-sulogin-shell to run sulogin. If the environment variable SYSTEMD_SULOGIN_FORCE is set to 1, systemd-sulogin-shell runs sulogin with the --force option. For more information, see https://systemd.io/ENVIRONMENT/ Create drop-in directories for the emergency and rescue service files. In those directories, create a .conf file that sets SYSTEMD_SULOGIN_FORCE to 1 for those services. Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com> Change-Id: I39359e91d99e490b9e57508f96f56567b49c663e
2024-04-15meta-ibm: Add new association for FujiRekha Aparna1-0/+248
This commit adds new association between PCIe slot and PCIe device for Fuji Change-Id: If8700c61d02ca62631e34e55e46689610e152da9 Signed-off-by: Rekha Aparna <vrekhaaparna@ibm.com>
2024-04-15meta-ibm:Association between PCIe slot & PCIe deviceRekha Aparna3-0/+524
Add association between PCIe slot and PCIe device for Rainier and Everest systems Change-Id: I18323770a94a2e0b3cba441dfa3ec0c5ff577546 Signed-off-by: Rekha Aparna <vrekhaaparna@ibm.com>
2024-04-15meta-ibm: Add new association JSON fileRekha Aparna1-0/+5327
This commit adds association JSON file for Fuji system Change-Id: I0522209591699e96b3e5c7e5112a150ff477156f Signed-off-by: Rekha Aparna <vrekhaaparna@ibm.com>
2024-04-15meta-ibm: Update Association JSON filesRekhaAparna013-1031/+3418
Downstream association JSON changes were not pushed to upstream from long time. So syncing the upstream association JSON files with the downstream association. Change-Id: I11c030dd8295f473718f4465fd96d689a4b64386 Signed-off-by: Rekha Aparna <vrekhaaparna@ibm.com>
2024-03-29meta-ibm: introduce new pstbmc machineAndrew Geissler2-0/+4
The pstbmc machine (the acronym meaning is still confidential) will be IBMs next generation server line. For now, just have it based on p10bmc. Change-Id: If980484b3acc44455f558661247886a15955c6bb Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2024-03-29meta-ibm: remove swift machineAndrew Geissler11-98/+2
This machine is no longer in use Change-Id: Icad284c92fa1cf9c5fc5f0afacb58e287a9557e2 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2024-03-29meta-ibm: remove p10bmc-distributed machineAndrew Geissler3-7/+0
We are pursuing a different design point and no longer have use for this machine. Change-Id: I68f9333ebdb9f3a88efa784eaef2226d9d59478b Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2024-03-29meta-ibm: organize packagegroups-obmc-appsAndrew Geissler1-7/+9
No functional changes, just ordering things a bit more logically Change-Id: Ib510d5a06bbf6d955c31664c23f8022d50ba1737 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2024-03-22treewide: remove meta-poky usagePatrick Williams3-3/+0
Upstream poky made a commit that adds an `/etc/motd` with a strong warning that meta-poky is not intended to be used for production purposes. There isn't anything we use directly from meta-poky anymore, so clean up all references to it. See poky commit a226865c8683398b5f58628ba2ec5aee1ee6c19d for additional context. We could potentially switch from using the `poky` subtree to picking up OECore directly, but right now it also provides us a qualified set of OECore + bitbake. Tested: Built yosemite4 and confirmed `motd` output is absent when SSHing in. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I9c08650d2278b3ba26794c009adad3e593767f58
2024-03-19Remove bmcweb logging and rely on defaultsEd Tanous2-5/+0
Once https://gerrit.openbmc.org/c/openbmc/bmcweb/+/69480 is merged, any system not taking the defaults can be removed. Across the project we should be consistent to make sure that the default behavior doesn't cause log spamming or performance degredation. Signed-off-by: Ed Tanous <ed@tanous.net> Change-Id: I95f319e6247f9b7dcf61e0d00c4366809bf3eba5
2024-03-19meta-ibm:system1:kernel: utilize correct device treeAndrew Geissler1-3/+1
The system1 device tree is now in openbmc/linux so utilize it Change-Id: I1e4214483b17e4fe98375d5d3f56e98934d5eedd Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2024-03-03meta-ibm: disable forced warm reboots on p10bmcAndrew Geissler1-0/+3
p10bmc systems don't support forced warm reboots Change-Id: I73dbe055597152d783276edd2f1f173892d3fca7 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-09-30 01:55:27 +0300