public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: edk2-devel@lists.01.org
Cc: Andrew Fish <afish@apple.com>,
	Chenhui Sun <chenhui.sun@linaro.org>,
	Marcin Wojtas <mw@semihalf.com>, Evan Lloyd <Evan.Lloyd@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Future of EBL (is there one?)
Date: Tue, 11 Apr 2017 10:44:30 +0100	[thread overview]
Message-ID: <20170411094430.GT1657@bivouac.eciton.net> (raw)

Hi all,

This email was brought about by Ard's spring cleaning.

EBL (EmbeddedPkg/Ebl/) is (to the best of my understanding) a sort of
lightweight alternative to UEFI Shell, especially for serial console
only embedded devices.

Probably because this was included in some existing ARM platforms in
the past, and its monolithic design made it more familiar to embedded
firmware developers to plug new commands into than the (extremely
modular) Shell, this has now made it into several
definitely-not-embedded platform ports.

In order to reduce the risk of this happening again, I would like to
consider the option of deleting EBL.

Do we still have a need for EBL in EDK2?
If so, can someone give a descriptive mission statement for it? What
is it intended for, and what does it provide over the alternatives?

For those on cc who have included it in platform ports (in
OpenPlatformPkg), can you explain why?

Evan - is EBL of any interest to your team?

Regards,

Leif


             reply	other threads:[~2017-04-11  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  9:44 Leif Lindholm [this message]
2017-04-11 14:57 ` Future of EBL (is there one?) Andrew Fish
2017-04-11 21:13   ` 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=20170411094430.GT1657@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