public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: rebecca@bluestop.org
To: Leif Lindholm <leif.lindholm@linaro.org>, devel@edk2.groups.io
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Marcin Wojtas <mw@semihalf.com>
Subject: Re: [edk2-devel] Adding HTTP and TLS support to Armada80x0McBin (from the MarvellEmbeddedProcessors edk2-open-platforms repo)
Date: Tue, 28 May 2019 19:36:32 -0600	[thread overview]
Message-ID: <ec4f074a-a96a-d9e4-a883-2a0801ee4ed1@bluestop.org> (raw)
In-Reply-To: <20190528083917.pdoshkxrpyjsoz5r@bivouac.eciton.net>

On 2019-05-28 02:39, Leif Lindholm wrote:
>
> This was actually enabled in the upstream edk2-platforms repository as
> part of the "use fragment config files for network config" set:
> 205d5621a35eb6251481526039d24b17374efdf0
>
> Since the PCIe updates just went in, that should now be a valid
> replacement for the MarvellEmbededProcessors repo.
>
> And will let you include HTTP with -D NETWORK_HTTP_BOOT_ENABLE=TRUE.


Thanks. I've also just realized that the devel-OpenPlatformPkg branch
(and probably the others, like devel-MinnowBoardMax-UDK2017) in
edk2-platforms is no longer used. 

Should the Readme.md files be updated to suggest people use master
instead, or perhaps the branches deleted (or closed, if that's something
that can be done in git)? I vaguely remember a discussion here about
switching to using the master branch, but other people coming back to it
might need a bit of a reminder!


-- 
Rebecca Cran


      parent reply	other threads:[~2019-05-29  1:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 23:34 Adding HTTP and TLS support to Armada80x0McBin (from the MarvellEmbeddedProcessors edk2-open-platforms repo) rebecca
2019-05-28  8:39 ` [edk2-devel] " Leif Lindholm
2019-05-28  9:47   ` Marcin Wojtas
2019-05-28 23:19     ` rebecca
2019-05-29  2:18     ` rebecca
2019-05-29  5:04       ` Liming Gao
2019-05-29  1:36   ` rebecca [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=ec4f074a-a96a-d9e4-a883-2a0801ee4ed1@bluestop.org \
    --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