Age | Commit message (Collapse) | Author | Files | Lines |
|
Remove RDEPENDS usage to bring in the webui and move to the new
IMAGE_FEATURE
Tested:
- Confirmed system1 has webui
Change-Id: I942509a3b5db2de8caf693f81f78850afd90f58d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Enable ipmbsensor to read Intel PCH temperature over
IPMB.
Tested: After updating entitymanager config the temperature
can be read using ipmbsensor.
Change-Id: Ifd57dcf380267a5b009c48da1fac960106ded901
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
phosphor-ipmi-ipmb is used for Intel ME communication to
get thermal sensor data and to set Intel ME into recovery mode
when doing an x86 BIOS update.
Tested: Intel ME responds to commands and returns thermal sensor data.
Change-Id: Ie4fadafdc98d611420629011a38922cd11692d41
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
p10bmc utilizes entity-manager in a variety of ways. For examples,
openpower-process-host-firmware.service depends on EM's compatible name.
IBM is moving more and more of it's inventory function over to EM so
add it in by default to p10bmc images.
Change-Id: I0b97a90009e058694f88aec6b7d9bb48a7040419
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add some example port associations to support FabricAdapter and Port.
The assocication is defined by
https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/62881.
FRU examples are added via
https://gerrit.openbmc.org/c/openbmc/openpower-vpd-parser/+/66540
These associations will be used for bmcweb Port schema implementation.
Tested:
- Verify bmcweb Port schema https://gerrit.openbmc.org/c/openbmc/bmcweb/+/61097
Change-Id: I8e892f029210d5391456e0ff5827b3d6a18d9c7a
Signed-off-by: Myung Bae <myungbae@us.ibm.com>
|
|
A few paths were missing callouts
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I617085b4a1305ed264f8008b4577567d93e7150e
|
|
On Rainier and Everest the code to put the power supply input history
maximum and average values on D-Bus is being removed and replaced with a
single peak input power sensor.
Remove the associations to them since they are no longer around.
Note: The associations for the new sensor will be handled by the
psu-monitor application.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I07bb6523f60be0e56db5d85932da9193719c7406
|
|
The NVMe SSDs on the ruler drives are already found by FruDevice.
Enable nvmesensor to read temperatures as soon as the x86 is
powered on.
Change-Id: I2191f909ab1b9e4bc79ae0d24de9042fe54291eb
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
This file is used to know which location codes to call out in error logs
when I2C and other accesses fail.
There are still a few missing callouts, but most are there.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ic0c61e362c5dcab4d374168da84bb7128d0bb22e
|
|
There is no in-tree user of this package. Remove it so we can archive
the repository.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I777ac0e0ffaf14508a49d5160831e59d3044fe5e
|
|
The phosphor-gpio-util that was being used was a custom tool that can be
replaced by gpioset. It was also just removed from its repo.
The service now has to be a oneshot because otherwise it isn't allowed
to have multiple ExecStart lines.
Tested:
Powered on multiple times, ensured the power supply input history was
cleared on each power on.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ib181c67b70e2feb109c1a2aabba8d046e7dfe380
|
|
Makes SOL and obmc-console-client working again.
Change-Id: I3d98319c2278794ba3db9ace4c89932c305d66d8
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
Change-Id: I2a3e8bb54e07fc9d3e7b9bbc400c98c44f8d2810
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
Change-Id: I55bc9fc8195b5954492d6ba31d9a2cbc10ddbfba
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
currently admin user created with home directory '/' and there is an
error while deleting admin user.
this commit updates admin user home directory to /home/admin.
Tested by: Notice admin home directory and Delete admin user
Change-Id: I32210435ac0a94555d2f369e226df7e04f49d88c
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
|
|
The reset-fan-watchdog service needs to toggle a GPIO in order to unlock
the fan watchdog circuit so fans can be controlled after the watchdog
has expired and locked them at high speed. This gets called on every
power on to bring the fans under control again in case the watchdog had
expired on the previous boot.
This was done previously using a custom application which used libgpiod
under the covers, which was written before gpioset was around.
Now that gpioset is available, just use it instead to toggle the GPIO so
there's less custom code we have to worry about maintaining.
The actual minimum timing requirement of the toggle is around 5ns, so
the 1us being used by all the config files meets that.
Tested:
Expired the watchdog by stopping the fan-watchdog service, then powered
off and back on and made sure the fans can still be controlled.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ibd36ff17e83b57d521364f0092dfa1f5abf34856
|
|
Change-Id: I5be5a644de26648d194b66ae70148201b4dafd58
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
Modify ACBEL PSU configuration file to read output voltage from sysfs
in2_label and to read the output current from curr2_label.
Testing: Placed the modified config file in
/etc//default/obmc/hwmon/ahb/apb/bus@1e78a000/i2c-bus@200/power-supply@5a.conf
then verified the output voltage and current output shows up on the BMC
sensors web page and redfish.
Change-Id: Iacf1469295b99f6a7363d26983786f9c7ed8826a
Signed-off-by: Faisal Awada <faisal@us.ibm.com>
|
|
Adjust meta-ibm to add support for the new machine.
Change-Id: I2eb61f3d9c85c23b16f026f8f9eb4506c78e97ad
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
Dbus timeout for PLDM is set to 5 secs. After reset reload BMC is
too busy and cannot return in 5 secs. Increasing the dbus timeout
value to 10 seconds to address this issue.
Change-Id: I1f513062a617d53061ec3e0a4aca03c996f11d0e
Signed-off-by: vkaverap@in.ibm.com <vkaverap@in.ibm.com>
|
|
Patrick Williams (6):
clang-format: copy latest and re-format
writefrudata: remove vla
strgfnhandler: suppress unused parameter warnings
frup: suppress stringop-truncation warning
scripts: accept absolute paths to YAML
build: enable meson builds
build: install strgfnhandler into ipmi-providers dir
Vernon Mauery (1):
Set new maintainer as Patrick Williams
Willy Tu (1):
fru-parser: Remove the use of mktime
Switch to Meson.
Change-Id: Iec9c41cc17a72f84248b8cd75f70353e053f17e2
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
There is a desire to add non-openpower systems to the meta-ibm layer. To
do that, need to ensure the bbappend files that are appending to
openpower recipes are only included if the machine being built includes
the meta-openpower layer.
Tested:
- Confirmed a system not including meta-openpower builds ok with this
- Confirmed p10bmc still uses the bbappend files
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I32a08e9f20a20152d51c77cdfca6bbc15b5e93d4
|
|
Tell phosphor-buttons the proper power button profile to use for IBM
p10bmc systems so it meets IBM's requirements.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I48337c9b2d31c47c9e3aa0bfaa5f8ebda80e8577
|
|
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>
|
|
Clearly define the optional features and their defaults within the PSM
repo.
Change-Id: Ibf466d9319b4176c816ef22c4cdbfd8cd693a90b
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
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>
|
|
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>
|
|
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
|
|
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>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I3792c2aa7f4bcd92254717c5bd00bc438f9101be
|
|
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>
|
|
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>
|
|
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>
|
|
Andrew Geissler (1):
systemd: no installation in templated targets
Includes needed service installation.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I22023bee9be60928a1ab990d627dc3d5553f30ad
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Patrick Williams (1):
clang-format: copy latest and re-format
Change-Id: Ib3888ded06c8d0766b158293420b64644d600d7e
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
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
|
|
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>
|
|
-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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iced76041c1207dc9ab28a83fd849ba3cd0a07bb5
|
|
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>
|