Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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>
|
|
New docker container is flagging some issues in this shell script:
```
SC2322 (style): In arithmetic contexts, ((x)) is the same as (x). Prefer only one layer of parentheses.
SC2046 (warning): Quote this to prevent word splitting.
SC2219 (style): Instead of 'let expr', prefer (( expr )).
```
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I46dac4da799a9e3256bb5f1829784253be67716f
|
|
To enable Serial-Over-LAN functionality via the standard "ipmitool sol"
command it is necessary to create a DBUS interface
"xyz.openbmc_project.Ipmi.SOL" that would be used for the communication
between the "phosphor-net-ipmid" and "phosphor-host-ipmid"
applications.
Change-Id: I8a63c233f321fe540d73ef33305beb0aa555796a
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Current SoL settings cause 'ipmitool sol' to crash after some
working time. Increase RetryIntervalMS to fix the issue.
Change-Id: I650b7d642f7f3e13df1f2d433b612cee6e1f5616
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Currently with the 'oneshot' unit type the 'ip-to-fpga.service' is
always in the 'running' state:
```
root@ethanolx:~# systemctl list-jobs
JOB UNIT TYPE STATE
88 obmc-led-group-start@bmc_booted.service start waiting
1 multi-user.target start waiting
126 ip-to-fpga.service start running
3 jobs listed.
```
This creates a problem since 'srvcfg-manager' service expects every
startup job to finish.
Change unit type to 'simple' to fix the issue.
Change-Id: I45840ef432ce33be400b547420ab5ceeca949ba0
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
'phosphor-net-ipmid' application now requires
'xyz.openbmc_project.Control.Service.Attributes' interface for the SoL
functionality to work correctly.
This interface is provided by the 'srvcfg-manager' application,
therefore include it to the build.
Change-Id: I0c0473df2d12cf7124dc07fa4c41e84d6e82bb5f
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
'SRC_URI:<machine> +=' syntax creates new variable 'SRC_URI:<machine>'.
'SRC_URI:append:<machine> =' syntax appends the variable 'SRC_URI' when
appropriate machine is selected.
hostlogger and obmc-console recipes incorrectly use the first syntax in
places where they should use the second one. This leads to build error,
when bitbake can't find added files.
Correct recipes to fix ethanolx/daytonax boards build.
Change-Id: Ibf424b95ae5aadf4c2ffd5915d746fb19f2a6d66
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8ea79d284356629f5b7b24ad3a99336e9e2e297e
|
|
If switch SW2-7 is on, FPGA shows BMC IP address on the 7-segment
displays. For that functionality to work correctly BMC needs to write
its own IP address to the paticular FPGA I2C registers.
Add a service that performs this action on every IP change.
Change-Id: Iead978ef3651448f4c32936402607fbb3267ee18
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Drop skeleton_workbook from the machine configuration. This is an
obsolete feature that shouldn't be used for modern systems.
Change-Id: I183044341548708265cd74f3d19c1b2266be3fc6
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Move common machine configurations to the include file.
Change-Id: Iafd07c4d6dc1abdcffede7568e6aef16e2f53ac4
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Add AMD DaytonaX CRB to the meta-amd layer.
Change-Id: I7df37f78640e9cc9c595da257bfc982d8f636acd
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
All configurations that are specific for the EthanolX board are needed
to have ":ethanolx" override.
Change-Id: I7b3381a1f486168bcd12a1ac0fb4756a31fb0487
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
"x86-power-control" doesn't allow to set BMC_READY signal, but besides
that everything is compatible with the upstream code.
Change-Id: Ic60bfa7b7cbb85494c542fea9b3fd480beec0a12
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
The "redfish/v1/Systems/system" page is necessary to fill the
"Server information" panel in the webui-vue application.
Change-Id: Id8ee7b6ab504cd38916f92fd6dda9d99dfdd898c
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
To enable Serial-Over-LAN functionality via the standard "ipmitool sol"
command it is necessary to create a DBUS interface
"xyz.openbmc_project.Ipmi.SOL" that would be used for the communication
between the "phosphor-net-ipmid" and "phosphor-host-ipmid"
applications.
Change-Id: I41eaac0eb53b66d135032c14e69abbe5e97509ce
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Add support for dynamic fan RPM control based on the values from
temperature sensors.
Control is based on PIDs and is splitted to 3 thermal zones:
Zone 1:
- CPU0 SB-TSI temp with a setpoint 60.0 C
- P0 FAN
Zone 2:
- CPU1 SB-TSI temp with a setpoint 60.0 C
- P1 FAN
Zone 3:
- All LM75A sensors on board with a setpoint 35.0 C
- SYS FAN1 - SYS FAN6
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Ifca359ba23777e2b1f46783272cf98ff0b08fe68
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
It's not clear why these patches were added in this manner, but they
can't really remain here from a maintenance perspective. Pinning one
platform on an old version of x86-power-control, as well as setting a
specific patch means that it's impossible for people to test and use
upstream code with it. It is also explicitly called out as item #1 on
the meta layer guidelines for this reason:
https://github.com/openbmc/docs/blob/master/meta-layer-guidelines.md
To the maintainters of this meta layer, please work with Jason and Kwin
(the x86-power-control maintainers) to get your features accounted for
in the normal build, adding build flags and configuration entries where
appropriate.
Tested:
This almost certainly breaks power control on ethanolx, but given the
way this patch was merged, there's really no way to avoid that.
Signed-off-by: Ed Tanous <ed@tanous.net>
Change-Id: I1f6a40e5b01c36441ff8d66e8e73265e0e009a4f
|
|
Switch the u-boot branch from the 2016.07-aspeed-openbmc
to the 2019.04-aspeed-openbmc.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I7f17b31abe32c374b01cb037ba03ed2608c1190d
|
|
The code for obmc-op-control-host is only useful for OpenPower
machines, but somehow it is being included in many other machines.
Remove it from all of them except meta-openpower.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4e7c7365eb320c3fb9ea7a57aca2ed0b1832e85e
|
|
In the AMD EthanolX board CPU0 UART1 is connected to the BMC UART0.
Therefore from the point of BMC UART0 is an upstream (host) UART.
'obmc-console' application gets this information from its configuration
file name ('server.ttyS0.conf').
On the other case setting 'local-tty' inside the configuration file is
intended for the downstream UART settings, which is not present on the
AMD EthanolX board. Therefore remove this setting.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I3daa1528cb5a7b5ff748189f29da3c3d91899ca4
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
|
|
We also need to move the conf-notes.txt files.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic44e015c0216b526de4fec277ad42f162bca1f33
|
|
The latest poky commit is requiring us to have all of
our template configs in a subdirectory instead of directly in
the `conf` directory. Without this we end up with errors during
setup like:
```
Error: TEMPLATECONF value (which is .../openbmc/meta-facebook/meta-bletchley/conf) must point to meta-some-layer/conf/templates/template-name
```
Fix this by moving all of our template files into the 'default'
template subdirectory (following the pattern of poky) and modifying
`setup` as necessary to follow.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iecefde73d55acbb6bc63ae3d68c4311adaf327ae
|
|
Harvey.Wu (2):
dbus-sdr: fix SEL record Generator ID to fit SPEC
dbus-sdr: fix the vector size in sdrWriteTable and sdrStatsTable
Jian Zhang (1):
Add data types to Value to extend setDbusProperty
Vernon Mauery (1):
fix header install
Willy Tu (4):
cleanup: Remove all warning errors for the Meson build support
build: Add meson build for phosphor-host-ipmi
build: move all shared_library/module to library with version suffix
build: Remove dynamicsensor library if it is not enabled
Change-Id: I92503c6625d1ec2bf88c0a28afac9b4eeb8fbd75
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Willy Tu <wltu@google.com>
|
|
The only recipes which use content from meta-perl are openpower
machines:
```
meta-openpower/recipes-bsp/pdata/pdata_git.bb: libxml-libxml-perl-native \
meta-yadro/meta-nicole/recipes-phosphor/logging/openpower-esel-parser_git.bb: libxml-libxml-perl-native \
```
Remove meta-perl from the bblayers of every layer except openpower
machines.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I51f1a8fbfbe879295c64d2339fc115dbd8823681
|
|
This was added with cde0f094f for libseccomp, but shortly after that
upstream moved libseccomp from meta-security to core (241c7d2e6). As
such, meta-security is no longer used or required.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I371e54b11f6336720dfc6edf0ef733d22b7fb4f2
|
|
Per [1][2], Yocto is starting to deprecate ABORT and has replaced
the "ABORT" action in BB_DISKMON_DIRS entries with "HALT".
1. https://wiki.yoctoproject.org/wiki/Inclusive_language
2. https://git.yoctoproject.org/poky/commit/?id=4f77505d94a8f6260933f457e9848d1d2fa98ce5
Tested:
Built obmc-phosphor-image successfully and eliminate the following
warnings:
```
WARNING: The BB_DISKMON_DIRS "ABORT" action has been renamed to
"HALT", update configuration
```
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If57d0ded9fac41e23b31b01e2a0e309ac7388148
|
|
Upstream has removed the image-prelink bbclass[1], so remove it from any
local.conf.sample that still has it enabled.
1. https://git.openembedded.org/openembedded-core/commit/?id=857baaf9e3d181ca18264e85d90b899fd94acff9
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I70f42f8816f5dea207fcf5c34837d6796b3f6bb6
|
|
* Deprecate N-1 release (hardknott).
* Enable N+1 release (kirkstone).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
|
|
The MAINTAINERS files are no longer used and are out of date (references
to IRC still exist in most of them). Remove them and rely on the OWNERS
exclusively.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I0f5d2719ad97e218ce03c4503efe1b1c92ac455e
|
|
This sets u-boot to the package containing the v2016.07-aspeed-openbmc
branch. This ensures there will be no change if the default changes in
the future.
Change-Id: Iea12e1691dbdda34a3f95d6d0862add0b15bcf37
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required.
As it said by Yocto documentation it can be used by `Hob`
https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE
that already removed since Yocto-2.1
https://www.yoctoproject.org/tools-resources/projects/hob
Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
|
|
The obmc-system-mgmt feature is currently used in the image to trigger
inclusion of a virtual-provider which provides a number of packages many
systems need. Partially revert the removal of this feature so that
the outcome is:
1. The empty obmc-phosphor-sysd package is still removed.
2. By default the 'obmc-system-mgmt' feature is included, unless
specifically exempted.
3. All EVB platforms remove the 'obmc-system-mgmt' feature since
they have no system they are managing.
This partially reverts commit 060ad3ff7fcc30aff78a9e504efee9d8fa0d4526.
Tested:
* Built `bletchley` and confirmed `packagegroup-fb-apps-system` and
`entity-manager` are present.
```
entity-manager armv7ahf-vfpv4d16 0.1+git0+6bf41588ab-r0
packagegroup-fb-apps-system all 1.0-r1
```
* Built `witherspoon` and confirmed `packagegroup-op-apps-system` and
`pdbg` are present.
```
packagegroup-op-apps-system noarch 1.0
pdbg arm1176jzs 3.3
```
* Ran `bitbake -p` on `evb-ast2600` to confirm the undefined
`virtual-obmc-system-mgmt` is not being included in the image.
Change-Id: I8b7804d5101cc84a2c57473b3f85672bf7767c67
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Every machine layer treats 'system-management' as either part of a
package-group or removes the feature. The sample implementation in
meta-phosphor is a do-nothing shell script (and up until recently was a
Python script). There appears to be no useful purpose to this feature
as a stand-alone concept, so remove it.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b
|
|
Modify the machine meta-layer configs to remove the use of the
OBMC_MACHINE_FEATURES indirection and favor the Yocto MACHINE_FEATURES
variable instead.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifafb79e4e4c010e9476b9547cd4982f5b645060e
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ia05891430c6c97a89b7bc8ba4558ae496866bf7d
|
|
bitbake offers a choice of DEB, RPM or IPK packaging. To a degree the
choice is functionally arbitrary for image generation but control over
the package format becomes important if we want to:
1. Include runtime package management functionality in the firmware image
2. Mess about with the packages on the build system
With respect to 1 the IPK format and opkg (an ipk package manager) are
designed for embedded systems[1] - by contrast to RPMs have heavier
dependencies and a greater impact on the size and complexity of the
firmware image.
Regarding 2, the embedded nature and the need for opkg to work without
much fuss leads to a lower configuration barrier by comparison to RPMs.
With ipk it becomes possible to reuse the packages built during image
preparation for core analysis without needing to generate an SDK:
```
$ export LD_LIBRARY_PATH=./tmp/work/x86_64-linux/opkg-native/*/recipe-sysroot-native/usr/lib
$ MY_DEBUG_ROOT=tmp/rootfs-debug
$ ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/*/opkg.conf \
-o $MY_DEBUG_ROOT \
update
$ fakeroot ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/opkg.conf \
-o $MY_DEBUG_ROOT \
install dbus-sensors dbus-sensors-dbg
$ gdb-multiarch
(gdb) set solib-absolute-prefix .../tmp/rootfs-debug
(gdb) add-auto-load-safe-path .../tmp/rootfs-debug
(gdb) file tmp/rootfs-debug/usr/bin/nvmesensor
(gdb) core-file obmcdump_17_9597/core.nvmesensor.0.aae91b519d0e4e0e8bbe746e3f6cd25f.2779.9594000000
Core was generated by `/usr/bin/nvmesensor'.
Program terminated with signal SIGABRT, Aborted.
pthread_kill.c:45
45 pthread_kill.c: No such file or directory.
(gdb) bt
pthread_kill.c:45
../sysdeps/posix/raise.c:26
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
"xyz.openbmc_project.NVMeSensor", this=0x488f04) at
/usr/include/sdbusplus/bus.hpp:234
../../../../../../workspace/sources/dbus-sensors/src/NVMeSensorMain.cpp:159
(gdb)
```
This approach documented in the Poky Reference Manual:
https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins
Switch all machines to IPK to align the debugging experience with
upstream's documentation and to facilitate efficient use of packaged
software at runtime.
[1] https://openwrt.org/docs/guide-user/additional-software/opkg
Change-Id: I8ef526add2d7a6790de1b3eb3fb85cd39b864f23
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Make the following changes to fix compilation errors:
- add honister to the LAYERSERIES_COMPAT variable,
- increase CONF_VERSION to 2,
- use new bitbake override syntax
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I971f0f0f7110e0350994ced151ca429444885056
|
|
AMD EthanolX CRB uses 24LC128 EEPROM as a device that is supposed
to store FRU information.
Add necessary Linux driver that adds support for this chip.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Iaf54bfd5bfbc3266d2a18861ee47339df78c777b
|
|
The BMC on the AMD Ethanol CRB uses entity-manager for sensor
configuration. Therefore IPMI configuration YAML file should
use DBus paths to sensors based on the names from the entity-manager
JSON files.
Currently 'ethanolx-chassis.json' exports CPU fans on a DBus as
"P0_Fan"/"P1_Fan". Use these names to correctly populate CPU fans
to the IPMI.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I0425e42771e1bfb36ad067dfcad5a23e5f180d67
|
|
AMD EthanolX CRB is a board with x86-64 CPU, which means it can support
both EFI and Legacy boot.
Add 'boot_type' PACKAGECONFIG option for the phosphor-settings-manager
package to support EFI/Legacy selector in the BMC boot override feature.
This setting is designed for the possibility of setting boot override
as:
- "PC compatible" boot (legacy)
- Extensible Firmware Interface Boot (EFI)
Change-Id: I173c5b439b929e80f3a106f5e7775862f889ee16
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Populate ADC sensor data to the system. This change make ADC data
accessible over DBus, IPMI, Redfish and webui-vue.
The threshold values were calculated as 10% from the target values.
The "PowerState: On" entity-manager parameter on the "*_RUN" channels
is used to make thresholds active only when the board is powered on.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I5322e83fdbfa0815bed454ea81b83725a2221d2c
|
|
Populate voltage regulator sensors to the system. This change make
voltage regulator data accessible over DBus, IPMI, Redfish and
webui-vue.
AMD EthanolX CRB has 4 voltage regulators per each of its CPUs (P0/P1):
-ISL69147 - Px VDD core regulator
-ISL69144 - Px VDD SoC regulator
-ISL68127 - Px VDD Mem / VPP ABCD regulator
-ISL68127 - Px VDD Mem / VPP EFGH regulator
All of these voltage regulators are 1st generation multiphase devices.
They can be covered with a ISL68137 Linux driver initialized with a
"isl68137" parameter, which would bring the necessary "raa_dmpvr1_2rail"
initialization.
The threshold values were spoofed from the original voltage regulators
configuration in the AMD EthanolX CRB.
The "PowerState: On" entity-manager parameter is used to make thresholds
active only when the board is powered on.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I123db2e356f525e0d269aef780d34d218209592a
|
|
Populate SB-TSI CPU sensors to the system.
This change make SB-TSI CPU sensors accessible over DBus, IPMI,
Redfish and webui-vue.
The entity-manager configuration make use of "PowerState: On"
parameter as SB-TSI sensors are active only with a powered on CPU.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I80390bb0baa291e7a9d5b49b2e9542cef719da69
|
|
On the AMD EthanolX CRB only few of the dbus-sensors apps are
relevant. The rest of them aren't needed and will only waste
cpu time and produce ambiguous fail messages at the initilization
stage.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I9ce01d93d79b40386a59757244e8b9b8a6008289
|
|
Some I2C addresses can't be probed for a FRU. For example,
device at this address can be already connected to a driver
or the I2C bus is not scannable like the APML bus.
In this case 'fru-device' app will be producing messages
like this:
'fru-device[XXX]: device at bus X address XX busy'
To avoid these unnecessary log messages add I2C bus blacklist
json file for the 'fru-device' app.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I0618943c9362117d9931defa1e17bcd999621197
|
|
We've typically kept these LAYERSERIES_COMPAT to 2 releases: the current
and the upcoming. Remove 'gatesgarth' is it is now 2 releases back.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20
|