public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Andrew Fish <afish@apple.com>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Scott Telford <stelford@cadence.com>,
	Mike Kinney <michael.d.kinney@intel.com>,
	edk2-devel@ml01.01.org
Subject: Re: [staging/cadence-aarch64] Add readme for cadence-aarch64 branch
Date: Mon, 22 May 2017 11:14:42 -0700	[thread overview]
Message-ID: <6303342E-7E4A-4082-B27D-9A2EC02B0839@apple.com> (raw)
In-Reply-To: <20170522181252.GO1657@bivouac.eciton.net>


> On May 22, 2017, at 11:12 AM, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> 
> Hi Scott, thanks for this. Looking forward to seeing it.
> 
> Andrew, Mike - for what it's worth, I'm happy to do the mechanics here
> unless there are any objections.
> 

Looks good to me.

Thanks,

Andrew Fish

> Oh, and it's usually a good idea to cc maintainers of existing
> packages you intend to work on. For MdeModulePkg, this is
> Feng Tian <feng.tian@intel.com>
> Star Zeng <star.zeng@intel.com> (from Maintainers.txt),
> and if creating any new packages (as you are), probably cc the
> stewards as well (we don't always spot all emails that hit the list)
> Andrew Fish <afish@apple.com>
> Michael D Kinney <michael.d.kinney@intel.com>
> myself.
> 
> Yes, we could do with adding this to the edk2-staging master branch
> README.
> 
> Best Regards,
> 
> Leif
> 
> On Mon, May 15, 2017 at 05:33:43PM +0100, Scott Telford wrote:
>> Announcing the creation of a new edk2-staging branch for Cadence peripheral
>> hardware support in AArch64 platforms.
>> 
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Signed-off-by: Scott Telford <stelford@cadence.com>
>> ---
>> Readme.MD | 27 +++++++++++++++++++++++++++
>> 1 file changed, 27 insertions(+)
>> create mode 100644 Readme.MD
>> 
>> diff --git a/Readme.MD b/Readme.MD
>> new file mode 100644
>> index 0000000..e2ec063
>> --- /dev/null
>> +++ b/Readme.MD
>> @@ -0,0 +1,27 @@
>> +# Cadence IP Support Branch
>> +
>> +This branch will be used to contribute code to support Cadence
>> +hardware IP for AArch64-based platforms.
>> +
>> +## edk2-staging branch owners
>> +* Scott Telford <stelford@cadence.com>
>> +
>> +## Introduction 
>> +
>> +Cadence develops a variety of peripheral IP modules suitable for ARM
>> +SoC architectures. This branch is intended to provide a staging area
>> +for drivers and libraries developed to support Cadence peripherals
>> +that may be incorporated into various SoC architectures from other
>> +vendors, for later integration into the appropriate EDK2
>> +platforms. Initially, the focus will be support for the Cadence PCIe
>> +4.0 Root Port. For internal development and testing purposes, an EDK2
>> +platform has been developed for a minimal AArch64 system
>> +configuration, comprising a single Cortex-A53 processor, GIC-500,
>> +NIC-400, Cadence PCIe Root Port, and Cadence UART. This will be
>> +included in the branch to provide an example of driver/platform
>> +integration.
>> +
>> +## Related Modules
>> +The following modules are related to this branch:
>> +* CadencePkg   - Package containing Cadence-specific drivers and libraries
>> +* MdeModulePkg - Package containing generic drivers relevant to Cadence peripheral IP
>> -- 
>> 2.2.2
>> 
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel



  reply	other threads:[~2017-05-22 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 16:33 [staging/cadence-aarch64] Add readme for cadence-aarch64 branch Scott Telford
2017-05-22 18:12 ` Leif Lindholm
2017-05-22 18:14   ` Andrew Fish [this message]
2017-05-26 14:47 ` 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=6303342E-7E4A-4082-B27D-9A2EC02B0839@apple.com \
    --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