Aspeed SuperIO runtime management

[Michael Richardson]

Zev Weiss <zweiss at equinix.com> wrote:
    > For reasons I don't fully understand but that I think are orthogonal to
    > this particular issue, the platform in question can't use the Aspeed
    > VUART, and so instead uses two SUARTs configured back-to-back via the
    > UART mux to provide the host's serial console.  The host's firmware thus
    > enables its UART early in the host boot sequence, which requires that
    > the AST2500's built-in SuperIO device be enabled (SCU70[20]=0).

I don't really understand much about these SUARTs and the SuperIO.

I guess the SuperIO is supposed to now be provisioned only by the BMC,
except for this exception.
I use the word provisioned here, because I think that the host would get to
configure the UARTs speed, stop bits, etc. via it's normal process.

My question is: what if the BMC just did all the provisioning necessary and
the host either just didn't, or perhaps if it really wants to do this, that
it be faked into writing to some other thing that isn't really those
registers.

    > 1. Does anyone know of any better ways of handling this problem?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 511 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20231004/98988c68/attachment.sig>