public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Sakar Arora <sakar.arora@nxp.com>
Cc: Bhupesh Sharma <bhupesh.sharma@nxp.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [RFC V2] EDK2 Platform Proposal
Date: Mon, 10 Oct 2016 20:22:38 +0100	[thread overview]
Message-ID: <20161010192238.GO3471@bivouac.eciton.net> (raw)
In-Reply-To: <VI1PR04MB21735D468D229769D7FA2268F8C40@VI1PR04MB2173.eurprd04.prod.outlook.com>

Hi Sakar,

Apologies for lag.
What follows are my thoughts, not really discussed with Andrew/Mike.

On Wed, Oct 05, 2016 at 02:16:19PM +0000, Sakar Arora wrote:
> Hi,
> 
> A few questions here.
> 
> What is the proposed directory structure for the edk2-patforms branches? 
> Will it be the same as in
> https://github.com/tianocore/edk2-platforms/tree/minnowboard-max-udk2015,
> which is just the same as edk2?

No, this was one of the original ideas, but we decided on using a
completely separate structure and utilise PACKAGES_PATH to link the
repositories together for building.

On the one hand, I see no reason to change the minnowboard UDK branch,
the one branch that will have a strict layout is
edk2-platforms/master. Others will probably align to a similar layout
for expedience, as time progresses.

> Or, will it be the similar to platform specific part of the
> directory structure proposed in
> https://github.com/mdkinney/edk2/tree/NewDirStruct_V3 ?

That would be my view, yes. Clearly this would simplify migrating new
platforms to edk2/master when desired..

> Or, similar to https://git.linaro.org/uefi/OpenPlatformPkg.git/tree?
> Or, left to platform developers' discretion?

I originally envisioned something more like OpenPlatformPkg (well, I
would, wouldn't I). But one of the things we clarified during
discussions at the recent plugfest was that device drivers, for
devices usable across multiple platforms, belong in edk2/master. So
once NewDirStruct happens, I'm likely to start migrating the
standalone drivers from OpenPlatformPkg into there.

Regards,

Leif

> Thanks,
> Sakar
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Bhupesh Sharma
> Sent: Wednesday, October 05, 2016 11:41 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-devel@lists.01.org
> Subject: Re: [edk2] [RFC V2] EDK2 Platform Proposal
> 
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of 
> > Kinney, Michael D
> > Sent: Friday, September 23, 2016 2:25 AM
> 
> > Hello,
> > 
> > 
> > 
> > Here is the V2 version of the proposal for the edk2-platforms repo.
> > 
> > 
> > 
> > Changes from V1:
> > 
> > ================
> > 
> > * edk2-platform is not a fork of edk2.
> > 
> > * edk2-platforms branches contain CPU, Chipset, SoC, and platform 
> > specific
> > 
> >   packages
> > 
> > * edk2-plaforms/master contains all open platforms that are synced 
> > with
> > 
> >   edk2/master.
> > 
> > * Each edk2-platforms branch may support many platforms (not just one)
> > 
> > * Use PACKAGES_PATH to do builds using packages from multiple 
> > repositories
> > 
> > * Update edk2-platforms branch naming to clearly identify platforms 
> > that
> > 
> >   are considered stable and platforms that are under active 
> > development.
> > 
> > * edk2 developers may be required to verify platforms in 
> > edk2-platforms
> > 
> >   builds as part of test criteria.  Especially platforms that are 
> > intended
> > 
> >   to be used with edk2/master in edk2-platforms/stable-* branches.
> > 
> > 
> > 
> > =================
> > 
> > 
> > 
> > Similar to edk2-staging, we also have a need to manage platforms
> > 
> > that have been ported to edk2.  Jordan has created a repository
> > 
> > called edk2-platforms and has created a branch for the
> > 
> > minnowboard-max that uses a validated release of the UDK 2015 for
> > 
> > the dependent packages:
> > 
> > 
> > 
> > https://github.com/tianocore/edk2-platforms
> > 
> > 
> > 
> > https://github.com/tianocore/edk2-platforms/tree/minnowboard-max-
> > udk2015
> 
> [Bhupesh] This link seems broken. I get a 404 error while trying to acess this branch. Does it require some special privileges.
> 
> Regards,
> Bhupesh
> 
> [snip..]
> _______________________________________________
> 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:[~2016-10-10 19:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 20:54 [RFC V2] EDK2 Platform Proposal Kinney, Michael D
2016-09-28 22:22 ` Leif Lindholm
2016-09-28 22:27   ` Andrew Fish
2016-09-29 22:21     ` Kinney, Michael D
2016-09-29 22:15   ` Kinney, Michael D
2016-10-14  7:14   ` Kinney, Michael D
2016-10-14  7:25     ` Kinney, Michael D
2016-10-14 12:59       ` Leif Lindholm
2016-10-14 15:48         ` Kinney, Michael D
2016-10-05  6:11 ` Bhupesh Sharma
2016-10-05 13:23   ` Richardson, Brian
2016-10-05 14:16   ` Sakar Arora
2016-10-10 19:22     ` Leif Lindholm [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-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=20161010192238.GO3471@bivouac.eciton.net \
    --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