| 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>
|
|
'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>
|
|
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>
|
|
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
|
|
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
|
|
Supreeth Venkatesh (22):
meta-amd: Add recipe for power control.
meta-amd: Override watchdog recipe.
meta-amd: Override fans and sel-logger recipes.
meta-amd: Define OpenBMC AMD package group applications.
meta-amd: Add Linux kernel recipe for EthanolX.
meta-amd: EthanolX platform configuration
meta-amd: Enable bmcweb and phosphor-webui
meta-amd: Enable LED Group Management for Ethanolx
meta-amd: Enable OOB BMC firmware update
meta-amd: Enable SOL host console
meta-amd: Modify device tree to enable thermal sensors for EthanolX
meta-amd: Enable hwmon to monitor thermal sensors and fan
meta-amd: Enable ipmi fru and sensor configuration
meta-amd: Add ipmi config, host and fru .bbappend files
meta-amd: Add entity-manager and ipmitool modules
meta-amd:linux: Added I2c0 and I2c1 which cater to AMD's APML Interface
meta-amd: Remove device tree patch
meta-amd: Add device tree patch
meta-amd: Add chassis control application
meta-amd: Add phosphor host logger application
meta-amd: Add fan tach sensor for fan 0 and fan 1
meta-amd: Remove bmcweb bbappend file
Change-Id: I53d6f4be203eefce1475d588b55fdf785b2b2024
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
