public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Achin Gupta <achin.gupta@arm.com>
To: <edk2-devel@lists.01.org>
Cc: Leif Lindholm <Leif.Lindholm@arm.com>, <afish@apple.com>,
	<michael.d.kinney@intel.com>, James Morse <James.Morse@arm.com>,
	<nd@arm.com>
Subject: [staging/apei]: New branch request for APEI work
Date: Thu, 25 May 2017 13:29:06 +0100	[thread overview]
Message-ID: <20170525122905.GC20909@e104320-lin> (raw)

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

Hi All,

I would like to create a branch for implementing support for APEI in EDK2. The
intent is to upstream modules that are capable of creating the HEST, BERT, ERST
and EINJ after gathering error and error source information from the platform
and other sources. The work is still very nascent and the branch will be first
populated with some workarounds. These will be used as the basis for further
development.

Could you please do the needful. The attached readme has been populated with
some basic information.

cheers,
Achin

[-- Attachment #2: Readme-apei.MD --]
[-- Type: text/plain, Size: 540 bytes --]

This branch will be used to develop support for ACPI Platform Error Interfaces
(APEI) on ARMv8-A standard platforms.

The branch owners: Achin Gupta <achin.gupta@arm.com>, James Morse <james.morse@arm.com>

# Feature Introduction
The ACPI specification describes APEI which provide a mechanism for the firmware
to convey error information to OSPM. This branch will be used to implement
support for these interfaces in EDK2 and test them on ARM platforms.

# Aims
Upstream support for APEI to EDK2

# Related Modules
* MdeModulePkg
* ArmPkg

             reply	other threads:[~2017-05-25 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 12:29 Achin Gupta [this message]
2017-05-25 16:52 ` [staging/apei]: New branch request for APEI work Laszlo Ersek
2017-06-01 13:18 ` Leif Lindholm

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-list 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=20170525122905.GC20909@e104320-lin \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox