From: Leif Lindholm <leif.lindholm@linaro.org>
To: edk2-devel@lists.01.org
Cc: Andrew Fish <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Richardson, Brian" <brian.richardson@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Graeme Gregory <graeme.gregory@linaro.org>,
Linaro UEFI <linaro-uefi@lists.linaro.org>,
Ryan Harkin <ryan.harkin@linaro.org>,
"haojian.zhuang@linaro.org" <haojian.zhuang@linaro.org>,
Chenhui Sun <chenhui.sun@linaro.org>,
Heyi Guo <heyi.guo@linaro.org>, "Duran, Leo" <leo.duran@amd.com>,
Marcin Wojtas <mw@semihalf.com>, Evan Lloyd <Evan.Lloyd@arm.com>,
Alan Ott <alan@softiron.co.uk>
Subject: Re: [RFC] migration of OpenPlatformPkg to tianocore
Date: Wed, 21 Jun 2017 18:44:56 +0100 [thread overview]
Message-ID: <20170621174456.GH26676@bivouac.eciton.net> (raw)
In-Reply-To: <20170503225539.GQ1657@bivouac.eciton.net>
Hi all,
I have now pushed updated versions of devel-OpenPlatformPkg branches
to edk2-platforms and edk2-non-osi. I now also have a Readme.md at the
top-level of edk2-platforms describing
All the silly hacks are gone, and all platforms now build.
I would really appreciate if people could have a look (and a play).
Regards,
Leif
On Wed, May 03, 2017 at 11:55:39PM +0100, Leif Lindholm wrote:
> Hi all,
>
> As some of you may be aware, I have been working around the lack of
> a clear upstreaming strategy for platform support by keeping such code
> in a dedicated repository I set up at Linaro for that purpose:
> https://git.linaro.org/uefi/OpenPlatformPkg.git
>
> During discussions at the last Seattle plugfest we finally agreed on
> the (theoretical) details of how to use the edk2-platforms repository.
> After that I promised to migrate OpenPlatformPkg across to the
> edk2-platforms and edk2-non-osi structure, with the explicit end goal
> from my side that this should become the master branch for each.
>
> And now, before the release of HURD 1.0, I have.
>
> Current limitations (that I can remember):
> - A few references to OpenPlatformPkg remain, in ways that do not
> appear to break any of the platform builds. Most likely this affects
> dead code, but in case it's been accidentally orphaned, I thought it
> best to
> - I have simply nuked all references to Ebl (used in _addition_ to the
> UEFI shell, which was never the intent) and the efi-toolkit
> ramdisk driver.
> - The Marvell Yukon driver that I sent out for review last week has
> not migrated anywhere, and so has been temporarily disabled
> Mike suggested I should
> - USB support on the LeMaker Cello board depends on the patch
> "OptionRomPkg: add firmware loader driver for Renesas PD72020x"
> sent out by Ard on 18th of April.
> - I have dropped some of the binary-only modules from OpenPlatformPkg,
> and contacted the platform owners with requests for modifications.
> - The git history is quite messy and will be cleaned up, but I wanted
> to keep the transition quite visible in the RFC.
> - I haven't filled anything into the Maintainers.txt files - I am in
> favour of moving to a fully machine-readable format with wildcards
> as Laszlo has proposed in the past, and think this would be an
> excellent point to have that discussion (which can be had separately
> for edk2-platforms and edk2-non-osi from edk2).
> - Few of the platforms complete the FV generation stage, and I've
> inserted a couple of silly hacks to get them to get as far as they
> do. I think that either I am missing some points of how
> PACKAGES_PATH is intended to work, or I'm simply hitting corner
> cases no one has come across before. I could really use some help
> debugging these issues. (examples below).
>
> The below depends on the 3-part series I sent out today for importing
> DwEmmcDxe and EfiTimeBaseLib from OpenPlatformPkg. But apart from
> that, I have uploaded branches called devel-OpenPlatformPkg to:
>
> https://github.com/tianocore/edk2-platforms/tree/devel-OpenPlatformPkg
> https://github.com/tianocore/edk2-non-osi/tree/devel-OpenPlatformPkg
>
> These branches _will_ be rebased occasionally until they get to a
> point where they can move out of devel- stage (and hopefully onto
> master).
next prev parent reply other threads:[~2017-06-21 17:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 22:55 [RFC] migration of OpenPlatformPkg to tianocore Leif Lindholm
2017-05-05 13:45 ` Yao, Jiewen
2017-05-05 14:03 ` Yao, Jiewen
2017-06-01 15:33 ` Leif Lindholm
2017-06-01 16:49 ` Kinney, Michael D
2017-06-02 14:29 ` Leif Lindholm
2017-06-07 14:58 ` Leif Lindholm
2017-06-13 23:13 ` Kinney, Michael D
2017-06-14 17:05 ` Leif Lindholm
2017-06-21 17:44 ` Leif Lindholm [this message]
2017-06-22 11:39 ` Ard Biesheuvel
2017-06-22 11:46 ` Ard Biesheuvel
2017-06-22 12:49 ` Leif Lindholm
2017-06-22 15:57 ` Ard Biesheuvel
2017-06-22 16:15 ` Leif Lindholm
2017-06-22 12:38 ` 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=20170621174456.GH26676@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