summaryrefslogtreecommitdiff
path: root/meta-ibm/recipes-phosphor
AgeCommit message (Collapse)AuthorFilesLines
2023-07-04meta-phosphor: libpldm: Rework ABI PACKAGECONFIG configurationAndrew Jeffery1-1/+1
Define three categories of ABI configuration via PACKAGECONFIG: 1. abi-production: Only deprecated and stable symbols are exposed 2. abi-maintenance: Only stable and testing symbols are exposed 3. abi-development: All deprecated, stable and testing symbols are exposed This makes it relatively straight-forward to perform broad testing for use of deprecated functions by setting `PACKAGECONFIG = "abi-maintenance"` in a `libpldm_%.bbappend` in the relevant meta layer. However, build for abi-production by default. Change-Id: I9df824e2543829dbe66a7203240e5367ffded3e3 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2023-06-20phosphor-state-manager: add PACKAGECONFIG optionsAndrew Geissler1-3/+4
Clearly define the optional features and their defaults within the PSM repo. Change-Id: Ibf466d9319b4176c816ef22c4cdbfd8cd693a90b Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2023-06-13meta-ibm: first-boot-disable-ipmi-net: Improve performanceAndrew Jeffery1-8/+5
The documentation for systemctl's `disable` verb[1] states: > This command implicitly reloads the system manager configuration after > completing the operation. Note that this command does not implicitly > stop the units that are being disabled. If this is desired, either > combine this command with the --now switch, or invoke the stop command > with appropriate arguments later. [1]: https://www.man7.org/linux/man-pages/man1/systemctl.1.html In simulation, reloads get expensive as they involve a bunch of IO. During boot, under qemu, such a reload can take on the order of 15 seconds. Further, Andrew Geissler states (no reference, private slack): > The service-config-manager is responsible for enabling and disabling > IPMI. On startup, it looks for the service and socket files via > systemd d-bus queries and caches in a file, /etc/srvcfg-mgr.json. If > you don’t run the services once on a fresh startup, > service-config-manager never sees them and therefore never provides a > way to enable/disable them. So on a fresh factory reset boot, you let > them start, service-config-manager sees them and caches them, and then > you disable them from there on out. As evidenced by the `After` statements in the unit, the expectation is that the units we're disabling have already been started. The documentation for systemctl's `mask` verb[1] provides a useful perspective: > Mask one or more units, as specified on the command line. This will > link these unit files to /dev/null, making it impossible to start > them. This is a stronger version of disable, since it prohibits all > kinds of activation of the unit, including enablement and manual > activation. The key insight here is the `disable` keyword tends to best be used to prevent the unit from being started as part of a given target, e.g. the default target. Given that we would only need to reload the systemd configuration to prevent the units from being started as part of a default target, and the fact that they must have already been started in accordance with `After` directive, there's no need to force an immediate reload of the systemd configuration upon disabling the units. Further, it's possible to combine the stop and the disable operation into one with `--now` as demonstrated in the `disable` documentation above. And finally, as the disable verb takes a unit PATTERN and not a singular unit, we can compress the operation down to a single invocation. Tested: 1. Booted up fresh p10bmc (factory reset), verified IPMI disabled by default via Redfish API 2. Enabled IPMI via Redfish API, verified bmcweb indicated IPMI enabled and services running 3. Rebooted BMC, verified IPMI was still enabled after BMC reboot 4. Disabled IPMI over Redfish, rebooted BMC, confirmed IPMI was still disabled Change-Id: I0926e9d16a56c2f022e415f4f40c35695dd155b8 Tested-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2023-06-13meta-ibm: first-boot-disable-ipmi-net: Fix unit conditionAndrew Jeffery1-2/+1
The [Service] section specifies: ``` ExecStart=/bin/touch /var/lib/ipmi-net-disable-one-time ``` However, the [Unit] section specifies the following condition: ``` ConditionFileNotEmpty=!/var/lib/ipmi-net-disable-one-time ``` The documentation for ConditionFileNotEmpty[1] states: > ConditionFileNotEmpty= is similar to ConditionPathExists= but verifies > that a certain path exists and refers to a regular file with a > non-zero size. [1]: https://www.freedesktop.org/software/systemd/man/systemd.unit.html#ConditionFileNotEmpty= And the documentation for `touch`[2] states: > A FILE argument that does not exist is created empty, unless -c or -h > is supplied. [2]: https://www.man7.org/linux/man-pages/man1/touch.1.html Neither `-c` nor `-h` are supplied, therefore the ExecStart= directive will create an empty file. As the ConditionFileNotEmpty= directive is negated the condition will always pass: Either the file doesn't exist, or it does exist and is empty. Therefore, as configured, this unit always runs. Always running the unit is counter to its 'one-time' name. Switch to `ConditionPathExists=`[3] to enforce the one-time nature. [3]: https://www.freedesktop.org/software/systemd/man/systemd.unit.html#ConditionPathExists= Change-Id: I1a8418a03c4fb9c6754f72f8651384b2f7e17715 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2023-06-09meta-ibm: enable only-allow-boot-when-bmc-ready featureAndrew Geissler1-0/+3
IBM systems do not want to allow boot operations unless the BMC is in the Ready state Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ic28cb6df9e7f803998a3fb380b3236ed31d6d4ec
2023-06-06obmc-console: Convert configs from socket-id to console-idAndrew Jeffery5-8/+8
As of 9a8f30ec5b58 ("obmc-console: Introduce console-id, deprecate socket-id") in obmc-console `console-id` is preferred over `socket-id`. Convert all in-tree configurations to `console-id` to enable removal of support for the deprecated `socket-id` configuration option. Change-Id: Ifd50603c378cfed5eb793b829b8296b7964e4194 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2023-06-06meta-ibm: fix some shellcheck issuesPatrick Williams1-119/+119
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I3792c2aa7f4bcd92254717c5bd00bc438f9101be
2023-06-05meta-ibm: Add LED endpoints for SystemAlpana Kumari3-0/+33
LED endpoints with Identifying, Identified_by for System was missing in Association json,as a result of that LocationIndicatorActive for system was null in redfish GET output. Also, from GUI, System identify LED was not functioning. If we try to set it, it goes away once we refresh the page,and no impact on led group. So this has been addressed for P10bmc Rainier and Everest system. Tested:- -Toggling reflects on LocationIndicatorActive as well as LED state of associated LED group. -It Works fine with redfish curl command as well as GUI button. $ curl -k -H "X-Auth-Token: $bmc_token" -X PATCH https://${bmc}/redfish/v1/Systems/system -d '{"LocationIndicatorActive": true}' $ $ curl -k -H "X-Auth-Token: $bmc_token" -X GET https://${bmc}/redfish/v1/Systems/system |grep "LocationIndicatorActive" % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 6262 100 6262 0 0 42026 0 --:--:-- --:--: "LocationIndicatorActive": true, - It shows up the result on hardware as below- ~# busctl introspect xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/enclosure_identify NAME TYPE SIGNATURE RESULT/VALUE FLAGS org.freedesktop.DBus.Introspectable interface - - - .Introspect method - s - org.freedesktop.DBus.Peer interface - - - .GetMachineId method - s - .Ping method - - - org.freedesktop.DBus.Properties interface - - - .Get method ss v - .GetAll method s a{sv} - .Set method ssv - - .PropertiesChanged signal sa{sv}as - - xyz.openbmc_project.Led.Group interface - - - .Asserted property b true emits-change writable ~# cat /var/lib/phosphor-led-manager/savedGroups { "value0": [ "/xyz/openbmc_project/led/groups/bmc_booted", "/xyz/openbmc_project/led/groups/enclosure_identify" ] }# Change-Id: I20dd57cc0c4edb0e28039ca9a276075914adc9f6 Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
2023-06-02meta-ibm: p10bmc-distributed: enable etcd packageojayanth1-0/+1
This feature helps to support a system where multiple BMC's will be a part of a single composed system. etcd is a strongly consistent, distributed key-value store that provides a reliable way to store data that needs to be accessed by a distributed system or cluster of machines. Enabled "etcd" package to install etcd binaries and the required systemd units to start etcd in cluster configuration. Tested: verified image. Installed binaries and systemd unit files. rootfs/etc/etcd.d/etcd-existing.conf rootfs/etc/etcd-new.conf.sample rootfs/etc/systemd/system/multi-user.target.wants/etcd-new.service rootfs/etc/systemd/system/multi-user.target.wants/etcd.service rootfs/lib/systemd/system/etcd-new.service rootfs/lib/systemd/system/etcd.service rootfs/usr/bin/etcd rootfs/usr/bin/etcdctl Change-Id: Iad30df3475b861491492168f975d7b347a1481a6 Signed-off-by: ojayanth <ojayanth@in.ibm.com>
2023-06-02meta-ibm: make search path non-machine specificAndrew Geissler1-1/+1
Would like to make a variant of the p10bmc machine that includes some of the new etcd function. To do that, the search paths need to not include the MACHINE variable. bitbake is smart enough to look under the sub-directory and find the appropriate files. Change-Id: I542b4568c18210870b3e621461585a4c7eee3121 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2023-05-19openpower-vpd-parser: srcrev bump 390fccb10f..99f7a66305Andrew Geissler1-0/+10
Andrew Geissler (1): systemd: no installation in templated targets Includes needed service installation. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I22023bee9be60928a1ab990d627dc3d5553f30ad
2023-05-15phosphor-power: srcrev bump aded7a0d44..8c90f319d5Andrew Geissler1-0/+1
Andrew Geissler (1): systemd: no installation in templated targets Includes changes required to ensure services are properly installed. Tested: -Confirmed services were installed into correct targets when building p10bmc machine Change-Id: I2d675ba083b2901ad1c26485d2f8b075fd6b3a25 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
2023-05-12Revert "Add socket-id for the first console"Andrew Jeffery3-3/+0
This reverts commit ec7cab9378f548e94ee4af83946b2583d1fc7194. ec7cab9378f5 ("Add socket-id for the first console") was only a partial fixup of the obmc-console configurations found in the tree. For historical reasons not all platforms that support multiple consoles install a client configuration file for all consoles. Instead they relied on some default behaviour that was removed in obmc-console's 4e7186918599 ("Fixed broken dbus interface for multiple consoles"). Applying the configuration changes in the manner of ec7cab9378f5 ("Add socket-id for the first console") resulted in an asymmetric configuration between the client and server, breaking some SSH SOL instances. As of ae2460d0b8e8 ("obmc-console: Provide a default value for `console-id`.") in obmc-console the requirement to specify `socket-id`[^1] is lifted. Instead, the configuration can choose to override a default value. This restores the original behaviour and unbreaks SSH SOL. [^1]: Now an alias of the `console-id` configuration key Websocket and IPMI consoles remain broken. A fix is under development that also takes a proper approach to supporting multiple consoles in bmcweb, and the same solution pattern can be applied in ipmid. More discussion of the problems involved can be found here: https://amboar.github.io/notes/2023/05/08/happenings-in-obmc-console.html Change-Id: I274284c791758f336da6d6301dc523bac2b5dd69 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2023-05-12meta-ibm:witherspoon: no installation in templated targetsAndrew Geissler1-1/+1
Upstream yocto introduced a change via e510222 (systemd-systemctl: fix instance template WantedBy symlink construction). This fixes a bug that we in OpenBMC had been taking advantage of in that we were able to document our templated target dependencies without it actually doing anything. The real installation of services within targets occurs in our bitbake recipes due to the complexity of chassis and host instances on a per machine basis. Leave the dependency information in the service files but comment them out. It's useful to be able to look at a service and understand which targets it's going to be installed into by the bitbake recipes. Change-Id: I1bf3bc6ce7a79d6c5847f5f1b4e6a97ca67332f8 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2023-05-12meta-ibm:fans: no installation in templated targetsAndrew Geissler1-1/+1
Upstream yocto introduced a change via e510222 (systemd-systemctl: fix instance template WantedBy symlink construction). This fixes a bug that we in OpenBMC had been taking advantage of in that we were able to document our templated target dependencies without it actually doing anything. The real installation of services within targets occurs in our bitbake recipes due to the complexity of chassis and host instances on a per machine basis. Leave the dependency information in the service files but comment them out. It's useful to be able to look at a service and understand which targets it's going to be installed into by the bitbake recipes. Change-Id: I9c485cbd19eb2804efe9916d4080ba3c662f65e5 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2023-05-11ibm-logging: srcrev bump 35262538d2..6a2b895648Andrew Geissler1-1/+1
Patrick Williams (1): clang-format: copy latest and re-format Change-Id: Ib3888ded06c8d0766b158293420b64644d600d7e Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
2023-05-10meta-ibm: p10bmc: Update OCC to processor associationsChris Cain3-32/+32
This corrects the associations between processor and OCC. The OCC is power_managing the processor. The processor is power_managed_by the OCC. Retrieving the element that OCC is managing: as 1 "/xyz/openbmc_project/inventory/system/chassis/motherboard/dcm0/cpu0" Signed-off-by: Chris Cain <cjcain@us.ibm.com> Change-Id: I45bce16127c34c70dadc133530ece0ed15c10b98
2023-05-09meta-ibm: Enable bmcweb-logging to error levelMyung Bae1-0/+1
bmcweb now supports to specify the logging level by https://gerrit.openbmc.org/c/openbmc/bmcweb/+/60212 This is to enable the Error or higher bmcweb logging levels for meta-ibm. Tested: - Build BMC image - Run bmcweb and verify Error/Critical logging messages - Verify Redfish Validator Change-Id: Ic431eafbaed22d25391201149976bd173a553c4e Signed-off-by: Myung Bae <myungbae@us.ibm.com>
2023-05-02meta-ibm: enable persist-mac flagIsha Sahni1-0/+1
-mac address wasn't persisting after reboot Tested by: 1. Assign a valid MAC address aa:e2:84:14:28:79 to the system using curl -k -H "X-Auth-Token:${bmc_token}" -X PATCH -D patch.txt -d '{"MACAddress":"AA:E2:84:14:28:79"}' https://$bmc/redfish/v1/Managers/bmc/EthernetInterfaces/eth0 2. Now GET and verify if the MAC address has changed using curl -k -H "X-Auth-Token:${bmc_token}" -X GET https://${bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth0 3. Now reboot the BMC and verify if the MAC address remains the same Change-Id: I334f1936f433e3e7e30ca5e669a89112f9879276 Signed-off-by: Isha Sahni <isha.sahni1@ibm.com>
2023-04-27meta-ibm: Using append in override syntaxChirag Sharma1-1/+1
Currently, scripts in install_ibm_plugins link_ibm_plugins are not getting added in BMC image as a result of which changing "+=" to append. Tested: Post change can see the scripts are getting added in the image. Change-Id: I932257e3652d0d6911923d4e9e0a57abeeb392ce Signed-off-by: Chirag Sharma <chirshar@in.ibm.com>
2023-04-21meta-ibm:Adding rsyslog service in P10BMCPavithra Barithaya1-3/+0
This commit adds the rsyslogd process in P10BMC systems. This is the revert of the commit - https://gerrit.openbmc.org/c/openbmc/openbmc/+/59038 The OpenBMC community has defaulted to rsyslog as the more feature rich alternative to syslog. Even though we don’t need the remote offload capabilities of rsyslog, it provides other features (like forwarding other users of syslog to the journal). Change-Id: I5f114d0157ec4d6c2390dccc5972019647f1ab20 Signed-off-by: Pavithra Barithaya <pavithra.b@ibm.com>
2023-04-21meta-ibm: p10bmc: Add occ to processor associationsChris Cain3-0/+176
Adding an association between the OCCs and processors, so that the throttle status can be associated with the applicable processor. The processor is power_managed_by the OCC. The OCC is power_managing the processor. Change-Id: I4f5b9f4ec347665316dae87e1995cebb52ef374c Signed-off-by: Chris Cain <cjcain@us.ibm.com>
2023-04-21Add socket-id for the first consoleNinad Palsule3-0/+3
This drop adds socket-id for first console. This was left out before but with the new design this parameter is required and enforced by obmc-console code. It is decided to set "socket-id = console0" initially because that is the current path used by bmcweb but in future you can change this value to whatever is appropriate. The console information is now available through the DBUS interface. Each console server register it's object path on DBUS. The leaf node of the object path is used to create a console path. For example in the following console0 the leaf node "console0" is used to make up the console path and the GUI will use console path "/console/console0" to connect to the console. busctl tree xyz.openbmc_project.Console.console0 `-/xyz `-/xyz/openbmc_project `-/xyz/openbmc_project/console `-/xyz/openbmc_project/console/console0 Here is a discord thread where new design was discussed. https://discord.com/channels/775381525260664832/1083551792094249051 Tested: Tested on the rainier system. Related commits: 1) phosphor-dbus-interface: https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/61486 2) obmc-console: https://gerrit.openbmc.org/c/openbmc/obmc-console/+/62496 3) bmcweb: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/62525 Change-Id: I5fd06f3aac69872a3e5032d592a9b59711795cfe Signed-off-by: Ninad Palsule <ninadpalsule@us.ibm.com>
2023-04-21meta-phosphor: obmc-console: Convert recipe to mesonAndrew Jeffery1-1/+1
Upstream obmc-console now supports the meson build system. I consider the autotools build system deprecated and intend to remove it. Change-Id: Ic8eea195bee0b3bea1cb9418593596ce1aaceeae Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2023-04-19openpower: Add support for PM eLog trace parsingpremjha2@in.ibm.com1-0/+1
Commit is intended to enable import of trace parser modules from hostboot repo. It aims to pullin modules which parse trace section of eLog committed by XGPE, PGPE and QME. Change-Id: I067af7b9594df13dab7184e568d0d008d4e47c65 Signed-off-by: Prem Shanker Jha <premjha2@in.ibm.com>
2023-04-19meta-ibm: fix some shellcheck issuesPatrick Williams4-19/+22
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iced76041c1207dc9ab28a83fd849ba3cd0a07bb5
2023-04-17meta-ibm:sensors:p10bmc:Add power-supply hwmon configsLakshmi Yadlapati3-0/+28
Add the power-supply configuration files for the acbel-fsg032 power supplies used in the Bonnell systems in order to get telemetry data added to D-Bus via phosphor-hwmon. Bonnell power supplies on bus 3 at 0x5a and 0x5b Change-Id: I97a1e1ba57ee1b2da6462b6921f121683498fe87 Signed-off-by: Lakshmi Yadlapati <lakshmiy@us.ibm.com>
2023-04-17treewide: reduce append operators on SRC_URIPatrick Williams1-1/+1
In a base bb file where we are setting the primary git repository, it is rare that we need to `SRC_URI +=`. This is an unnecessary pattern that seems to have been copied throughout the repository. Remove the pattern where appropriate and simply set SRC_URI directly. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I430186a82f9582ba6196f5bf66b659af4092b48d
2023-04-17meta-ibm: utilize new extra-dev-debug-tools distro featureAndrew Geissler1-1/+0
Tested: - Confirmed tools are in p10bmc flash image Change-Id: I808f38f410eaaad3077bb7eeaf36a166faf5beb4 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2023-04-14meta-ibm:add chassis association for cable cardsSunny Srivastava2-0/+176
The commit adds chassis association for cable cards. This change is with respect to the downstream change where duplicate entry for cable card association has been removed. It was found that chassis association is missing upstream. Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com> Change-Id: I2bb9c80aa50f29e67bba3abe9d5e8fa7de89f4d7
2023-04-06meta-ibm:ncsi-linkspeed: ensure eth device presentAndrew Geissler1-0/+1
IBM is building a system under the "p10bmc" bitbake machine that only has a single ethernet port, eth0, wired up on it. The system is still utilizing an AST2600, but only wired eth0 out of the system for cost purposes. Since the "p10bmc" machine is a shared target there is no way to remove services that assume eth1 is present during the build process. Instead, rely on the fact that the device will be present in /sys/class/net/ if in fact the system supports the network device. Tested: - Verified that a p10bmc Rainier machine with 2 eth ports still ran this script for both ports - Verified that a p10bmc Bonnell machine with only eth0 ran this script for eth0 but not eth1 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ic5dfe4bc772fb4de5eb28f3035cf9952d4bbcb7a
2023-04-04meta-ibm:tacoma: remove liberation-fontsAndrew Geissler1-1/+1
This is added in the line above as the witherspoon-tacoma is included in the ibm-ac-server group. This package does not work on a tacoma though (when building on POWER hardware) so remove it as it is not critical to the function we need on a tacoma. This does not build on POWER hardware due to this QEMU bug: https://gitlab.com/qemu-project/qemu/-/issues/1528 Under the covers, the liberation-fonts repo uses fontcache.bbclass which utilizes qemu-arm in the cross-compile environment. Once the following bug is in a QEMU recipe, this will resolve the issue but there's no reason to include this package on tacoma. Tested: - Confirmed witherspoon-tacoma machine builds on POWER hardware Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I98220a51b838498b572bda07b28ed483e9316889
2023-03-29meta-ibm:dump: Increasing bmcdump size for p10bmcChirag Sharma1-0/+1
Increasing the bmc dump size for ibm systems as the current size 200KB is not sufficient and have seen larger files i.e. journals are getting skipped. Hence increasing the max size of a dump to 20MB. Tested: -After increasing the size journals are getting collected in BMC dumps. Change-Id: I0282bd4ae38831b80309caa59d1e804ca3d2ff1f Signed-off-by: Chirag Sharma <chirshar@in.ibm.com>
2023-03-14meta-ibm: flash: Add Minimum Ship Level formatAdriana Kobylak1-0/+3
Enable the minimum ship level format for p10bmc systems to match a string that starts with some characters such as "ibm", followed by 2 numbers for the processor version such as "10", followed by the tag number. Change-Id: I4f3572db75b4fc1bb3c90c8c952d428d329b5d3a Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2023-03-09meta-ibm: Add max31785 hwmon config for BonnellMatt Spinler2-0/+10
While the max31785 is at the same I2C bus and address as on Rainier, it only has two fans so it needs a unique hwmon conf file, which it has because the name is different in the device tree. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ia2c77e4149f02fe0a9d335cdd0551fb4ddd75108
2023-03-03meta-ibm: p10bmc: Update fault identify associationGeorge Liu3-704/+704
Update the association configuration of fault identify according to the latest association interface[1]. [1] https://github.com/openbmc/phosphor-dbus-interfaces/commit/e7c10bd5cdab6cd898e5cad0daab8c1128adc0c8 Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I166c3dee16d8e709eb96982743fe30688b95012f
2023-03-03meta-ibm: p10bmc: Update identify associationGeorge Liu3-698/+698
Update the association configuration of identify according to the latest association interface[1]. [1] https://github.com/openbmc/phosphor-dbus-interfaces/commit/9eb460c6cfc2d7c2feb29c86f4beb31d4c3d9250 Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I65ef596f3011720b968462f54d7a3b60e7c84002
2023-02-28meta-ibm:tacoma: remove uart-render-controllerAndrew Geissler1-0/+1
This is added in the line above as the witherspoon-tacoma is included in the ibm-ac-server group. This package does not work on a tacoma though so remove it. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ibf1bc79d6e33646bfff1fa4f560b0b3a40ceb270
2023-02-28meta-ibm:tacoma: add entity-manager to flash imageAndrew Geissler1-1/+2
The witherspoon-tacoma system is going to be utilized for some rack controller prototyping. Add entity-manager in as it's required for prototype work. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iee11a5dd554ad9a9bad4dbfb44bdef7381a1101e
2023-02-22meta-ibm: Increase the BMC dump total sizeDhruvaraj Subhashchandran1-0/+2
Set the BMC dump total allowed size as 409600KB. p10bmc machines have an emmc based filesystem so therefore can fit more bmc dumps. Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> Change-Id: I05c1626ce9a03685adfdfd9713b3053ae8e63737 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2023-02-14meta-phosphor: turn off unit-failure-monitorBrad Bishop1-0/+2
This feature requires special configuration and isn't used pervasively, so turn it off by default. Change-Id: Id7398df6c7511ceeb3a18a8759bd890ead3d1cc8 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2023-02-03meta-ibm: phosphor-ledcontroller has movedAndrew Geissler1-1/+1
Recent changes moved this binary from /usr/sbin to /usr/libexec/phosphor-led-sysfs/. Update this service to reflect that. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I16df4cb1942ac93dfb8b487e58ff60ea67c58d28
2023-01-27meta-ibm: update service files in accordance with recent refactoringAndrew Geissler3-5/+5
As noted in the following mailing list thread: https://lists.ozlabs.org/pipermail/openbmc/2022-November/032457.html and implemented via this series of commits: https://gerrit.openbmc.org/q/topic:op-power-control-ref Some systemd services had their names changed. Update the service files in this repo to reflect this. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Idaca9c1a46f8b5d673b4912e3027fc9268aa5dba
2023-01-25meta-ibm: support build of witherspoon-tacomaAndrew Geissler1-0/+1
IBM may have some prototyping use for our old witherspoon-tacoma systems so get it building again. clear_hostdumps_poweroff.service needs to be installed on tacoma otherwise we get a "installed but not shipped" error. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I3ceeabe272636bc37bed040cc7e3b288c1fb15e5
2023-01-20meta-ibm: p10bmc: Update the association between Fan and ChassisGeorge Liu4-0/+212
Per association document[1], add/update the association between Fan and Chassis. [1] https://github.com/openbmc/phosphor-dbus-interfaces/commit/d0aa13b446ee1738d53fb1e04341946f5b0b7616 Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I6c4d74b17fcfcbeb620832485928dcfd3460fc00
2023-01-14meta-ibm:ncsi: ensure eth speeds set to 1 gigabitAndrew Geissler3-3/+44
IBM has run into some issues recently with certain network configurations where eth1 is not getting set to 1 gigabit. This can cause issues in scenarios where a network environment is running on 1 gigabit minimum-speed network switches. Removing link-local support from eth1 seemed to aggravated this. link-local is only on eth0 to avoid subnet issues. But without link-local, the systemd call, systemd-networkd-wait-online, does not always find an active eth1 so it never runs the command to force eth1 up to 1 gigabit. As far as we can tell, there's no appropriate mapping within systemd-networkd-wait-online for it to know when the NCSI stack is appropriately up on a network interface (allowing the 1 gigabit speed to be set). Therefore the solution taken in this commit is to just keep retrying for a period of time. Tested: - Verified new script ran and set eth ports as expected Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I6737e208b59830262f51a8e30c78a97fc698e4fd
2023-01-12meta-ibm: phosphor-state-manager: APR on power loss onlyAndrew Geissler1-0/+3
This option was added to phosphor-state-manager quite a while back via bcbee4a but never set within meta-ibm. By default, all IBM systems should only run APR when an AC power loss has occurred. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Id374781f3c07b019337b1d124ce9d4f3efb7f838
2023-01-04meta-ibm: Switch p10bmc to use ibm-read-vpdSantosh Puranik1-0/+23
This commit switches p10bmc machines to use a variation of the openpower VPD parser called ibm-read-vpd that supports JSON driven inventory configuration and runtime detection of system type. Also supported are VPD writes via the vpd-manager service. Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com> Change-Id: Id61b32846e0cc9750a5cf12297e7d956b1f511cf
2022-12-09ibm-logging: srcrev bump 2d38eda128..35262538d2Andrew Geissler1-1/+1
Patrick Williams (4): python: fix flake8 warnings and format with black black: re-format prettier: re-format markdownlint: fix all warnings Change-Id: Ic9c2b60fbd24b199ed7d69ad0b14499889bca901 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
2022-12-07meta-ibm: Add missing Everest device calloutsMatt Spinler1-13/+147
The TDA38740 regulator has a 2nd I2C address it responds to, so add entries to the callout table for these so that when the address is called out as failed the PEL will get the proper callouts. This file is autogenerated from an XML representation of the system. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I8e03ea17211c030e3fa4c0ffe9f497082c0a1945
generated by cgit v1.2.3 (git 2.39.0) at 2024-09-30 22:00:06 +0300