| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Required for SOL support
Tested:
- Confirmed expected conf file was in system1 image
Change-Id: I3b655b7cf46d1fb06b2b72d3531dccb7a37717ad
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Makes SOL and obmc-console-client working again.
Change-Id: I3d98319c2278794ba3db9ace4c89932c305d66d8
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
Adjust meta-ibm to add support for the new machine.
Change-Id: I2eb61f3d9c85c23b16f026f8f9eb4506c78e97ad
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
|
|
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>
|
|
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>
|
|
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>
|
|
A fork of it is maintained but its upstream layer has largely been
unmaintained.
No future products are planned to be based on this layer.
Mihawk is similar to Witherspoon.
Signed-off-by: Myung Bae <myungbae@us.ibm.com>
Change-Id: I82f7d777b78cd126237d51e42f1e11abdf80ae68
|
|
The Rainier and Tacoma using of both virtual UARTs provided by the
AST2600. Expose them both to the network via obmc-console.
where ttyVUART0 Exposer name is @obmc-console
and ttyVUART1 Exposer name is @obmc-console.guests
@obmc-console.guests initial exposed to access to phyp guests over that
interface that why its name is guests, but now we are using that
socket-it to run PHYP debug shell.
So it is good to change the name of that exposer socket-id "guests" as
"hypervisor".
Signed-off-by: Abhishek Patel <Abhishek.Patel@ibm.com>
Change-Id: I47dc71095795afbda8fb544fde4bcae78712093a
|
|
In the spirit of consistency with the new upstream override
syntax, change phosphor-discovery-service.bbclass to use it
and make tree-wide changes as appropriate.
After the change checked on Witherspoon on QEMU:
```
root@witherspoon:/etc/avahi/services# ls
obmc_console.service obmc_redfish.service obmc_rest.service
```
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib1fe3cce57a0130378af789abd83b457e0c3a318
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
This variable was added to bitbake.conf so lets use it. Using it is
best pratice and enables things like alternative base_libdir paths.
Change-Id: I9adcec7856c6242d86f0ffad8646a23219ccca21
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The hostboot team has started utilizing VUART1 for extra debug data
during a boot. This extra debug data is enabled within the CI
infrastructure. This extra debug data causes the critical information
going to VUART0 to get wrapped out of the default
/var/log/obmc_console.log file. Redirect the VUART1 data to its own
/var/log/ file.
The only other user of VUART1 on p10bmc systems is the PHYP software.
That is mostly used for interactive purposes so writing its data to a
separate log file should be fine.
I will work with the test teams to ensure this new file is collected as
a part of the standard debug data collection process.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I248e5e8536e58e137b5de35d7572789215566763
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built rainier and verified the console files were installed:
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/obmc-console/
Change-Id: Ida1010ae6c6c0e1eecf2b62521c06bfe055b0d88
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
