Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
Part of the functionality contained in the existing `cpuinfo` flag is
now split into a new flag `cpuinfo-peci`. The new flag is still
logically dependent on the existing one, but it gives finer control over
enabled features.
Remove all cpuinfo flags from default PACKAGECONFIG.
Update bbappend based on new defaults.
smbios-mdr: srcrev bump abdccd3af9..4e1cf09955
Jonathan Doman (1):
cpuinfoapp: Make PECI features optional
Change-Id: Ib9a1e634634f046b2ec6ff5629d4498bf0d5914b
Signed-off-by: Jonathan Doman <jonathan.doman@intel.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>
|
|
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>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8ea79d284356629f5b7b24ad3a99336e9e2e297e
|
|
The build option of Intel cpu sensor service in dbus-sensors
repository is changed from "cpusensor" to "intelcpusensor". Update the
build option in openbmc source to match with that change.
dbus-sensors: srcrev bump 0fe0229497..255da6b419
Thu Nguyen (1):
cpusensor: Change cpusensor to intelcpusensor
Tested:
1. No build errors.
Signed-off-by: Thu Nguyen <thu@os.amperecomputing.com>
Change-Id: Ib31f7ce3dd7d5ed1bb226eb991459ec0bf233973
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
phosphor-ipmi-host was recently converted from autotools to meson,
but we miss the moment. Update recipe according new build flags.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I061f3093f9fe482328e4499c80d74b1a7112e019
|
|
The phosphor-ipmi-host has two implemetations of SDR: static and
dynamic. Static SDR implementation requires us to set all coefs manually
for all sensors in the system, while dynamic implementation doesn't
support discrete sensors.
Enable support for mixed mode where both static and dynamic
implementations work at the same time.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I27df9e083f0bd816b9a02515e75a3dea69ea20bb
|
|
This brings a set of the unit-files to make `phosphor-watchdog`
working properly.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
Change-Id: I9763bf7e87753bfd2b9c7c05295dddd18e6f6c48
|
|
Add smbios-mdr daemon to the image. This only parse smbios image binary
which should be delivered to BMC filesystem using some other software
(via IPMI in our case).
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I3a18879630ccbe517030b6f803a6ae5fe42dceac
|
|
Setup ipmi stack for Yadro VEGMAN machines.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I13f5e51dd5b7ac169a71ee046ad61dbfa2bffe9b
|
|
This brings EntityManager sevice to the image.
This also brings dbus-sensors daemons to provide sensors based on EM
configuration.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I4d41f3b8bc98e8859cbfe33a220e79e78e8bbee5
|
|
Add obmc-console configuration for Yadro VEGMAN machines
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I392a6621f1588833d3aaf6187bc277ea661d416f
|
|
This brings LEDs description for phosphor-led-manager. This
configuration only describes LED groups.
Real LED control will be introduced in later commits with
phosphor-dbus-monitor configuration once we set other required
components.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I74b9f86b9d2c43d8b4f5728f330fe06b19b1e08a
|