From: Timothy Pearson <tpearson@raptorengineering.com>
To: Patrick Venture <venture@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Exposing POST codes
Date: Fri, 13 Apr 2018 19:47:43 -0500 [thread overview]
Message-ID: <5AD14FAF.90109@raptorengineering.com> (raw)
In-Reply-To: <CAO=notzv-4wn7J+uAzPYw1uWzTiN5jOGqHNEDUAzAGS+j5wivQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sounds like multiple folks have been working on similar code. Here's ours:
https://git.raptorcs.com/git/talos-skeleton/log/pyiplobserver?h=04-13-2018
The current version just parses the hostboot codes from the serial
console, it used to use pdbg but over time it was found that using pdbg,
even with the BMC kernel driver, destabilizes the IPL process at key
points. It does however also include state monitoring via BMC mailbox
bits for skiboot and skiroot, allowing the BMC to know when the full IPL
process is complete.
I like the approach of hostboot sending data over LPC, and we're willing
to rework the observer daemon to use that approach. Is there any way to
send status codes over LPC from the SBE?
Thanks!
On 02/28/2018 12:56 PM, Patrick Venture wrote:
> I talked to Nancy and I think it's time to revisit previous conversations
> about POST codes. We have a simple daemon that exposes the information
> over Dbus associated with https://gerrit.openbmc-project.xyz/#/c/5006
>
> If there's interest, I can stage it against skeleton for review and comment.
>
> We have a patch to the kernel character device for the aspeed-lpc-snoop
> that is required and enables reading the post codes.
>
> Patrick
- --
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJa0U+sAAoJEK+E3vEXDOFbOM4H/3WJK9SbA6ly4Q/CioC9Yz9L
dzwsKSClKkK1pHru86wPYHadAmatn/ksA5dl4pEzQlfh5RKGBAaoFdVdVG/BdbVA
upKn9WBudQyLCHFWtD3xg4vzX3cCsi3hFgvgGIKkdrxj4uMv+56Fp5Fwh2eWuun8
ITadBt1LVdZlZT7z56zi2gt0eC4QSaAIBjBXq4KYIhXdc/xX9suw7pLKHAfxpb3v
ygSlE+SGeD1jZQfA5y2CxhOYyl+ac3AmCHXlDe70WQgbyPHU6aohuJaoh1+AtJeo
ys2mULcL9Sz2y8YTBXbEQ2QVMCJHw2BpKBmy6gxuDKChUNndqNJBselSVu7jrXU=
=OWnM
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2018-04-14 0:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 18:56 Exposing POST codes Patrick Venture
2018-03-01 17:31 ` Patrick Venture
2018-03-05 5:19 ` Brad Bishop
2018-03-05 21:34 ` Tanous, Ed
2018-03-05 21:35 ` Patrick Venture
2018-03-06 1:05 ` Stewart Smith
2018-03-07 1:05 ` Rob Lippert
2018-03-13 6:48 ` Stewart Smith
2018-03-26 22:57 ` Rob Lippert
2018-04-03 6:08 ` Stewart Smith
2018-03-06 1:06 ` Brad Bishop
2018-04-14 0:47 ` Timothy Pearson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5AD14FAF.90109@raptorengineering.com \
--to=tpearson@raptorengineering.com \
--cc=openbmc@lists.ozlabs.org \
--cc=venture@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.