All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Thang Nguyen <thang@os.amperecomputing.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>, bradleyb@fuzziesquirrel.com
Subject: Re: Request to create ampere-platform-mgmt and ampere-ipmi-oem repos
Date: Fri, 30 Apr 2021 09:25:44 -0500	[thread overview]
Message-ID: <YIwTaJ11MRUXY2H5@heinlein> (raw)
In-Reply-To: <7bec9fb2-35d5-8e44-463f-3eb5c0955f0d@os.amperecomputing.com>

[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]

On Sat, Apr 24, 2021 at 07:48:14PM +0700, Thang Nguyen wrote:
> I intend to push Ampere specific features, you can find current codes at 
> https://github.com/ampere-openbmc/ampere-platform-mgmt.

It seems to me like all of the functional areas you mentioned we already
have some sort of implementation.  It would be better if you could work
with the maintainers on these repositories to see how it can be enhanced
to support your use case.  As I mentioned in another email thread today,
I really don't want to see catch-all repositories being created.

If you have specific features that aren't covered by an existing
repository or you feel like you've ran into a roadblock coming to
consensus with the developers already working in those areas, we should
revisit making repositories for those specific functional areas.

> 
> It is good to have any of below can be implemented with current existing 
> repositories:
> 
> - utilities to flash Ampere Host firmware and NVPARM: Boot EEPROM, 
> UEFI/ATF firmware, ...

Are these extra utilities or the firmware update procedures themselves?
Have you already implemented support in phosphor-bmc-code-mgmt?  There
are other systems that have BIOS update for x86 done in that repository.

> - Control boot EEPROM based on current input GPIO and log the 
> information into Redfish 
> (https://github.com/ampere-openbmc/ampere-platform-mgmt/tree/ampere/altra/host-control/scp-failover)

This looks like something that could be implemented with
phosphor-gpio-monitor.  Have you looked at that?

> - Handle boot progress from Ampere's Altra SMpro, log the progress into 
> Redfish and update dbus. Note that the boot progress is based on 
> information from EDK2 and other firmware like ATF and SMpro.

You can probably fit this into the existing post-code repositories:
    - phosphor-host-postd
    - phosphor-post-code-manager

We recently did similar for a system where we get the post codes over
IPMB rather than GPIOs.

> - Handle events from Ampere Altra's SMpro (like Sideband controller) and 
> log to IPMI SEL and Redfish.

This sounds like it should go into ampere-ipmi-oem?  I'm making an
assumption that the SMpro is an IPMB path, which might be wrong.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-04-30 14:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  2:05 Request to create ampere-platform-mgmt and ampere-ipmi-oem repos Thang Nguyen
2021-04-23 13:31 ` Patrick Williams
2021-04-24 12:48   ` Thang Nguyen
2021-04-30 14:25     ` Patrick Williams [this message]
2021-05-04  1:47       ` Thang Nguyen
2021-05-11  9:00         ` Thang Nguyen
2021-05-03 14:33 ` Brad Bishop
2021-05-04  1:45   ` Thang Nguyen
2021-06-07  8:45   ` Thang Nguyen
2021-06-07 12:59     ` Andrew Geissler

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=YIwTaJ11MRUXY2H5@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=thang@os.amperecomputing.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.