public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Andrew Fish <afish@apple.com>
Cc: edk2-devel@lists.01.org, Chenhui Sun <chenhui.sun@linaro.org>,
	Marcin Wojtas <mw@semihalf.com>, Evan Lloyd <Evan.Lloyd@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: Future of EBL (is there one?)
Date: Tue, 11 Apr 2017 22:13:13 +0100	[thread overview]
Message-ID: <20170411211313.GX1657@bivouac.eciton.net> (raw)
In-Reply-To: <847AC2FB-E4AC-4722-8B01-0FA88E59C248@apple.com>

Hi Andrew,

On Tue, Apr 11, 2017 at 07:57:13AM -0700, Andrew Fish wrote:
> > On Apr 11, 2017, at 2:44 AM, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> > 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.
> > 
> 
> Leif,
> 
> I wrote the original code something like 10 years ago. The intent
> was a proof of concept that EFI could scale down to embedded systems
> and be a BSD licensed alternative to U-Boot. I was trying to show
> that implementation != architecture and a lot of edk2 projects were
> large but they did not have to be.
> 
> I was kind of surprised how popular it was and how many products
> actually shipped with it. I'm fine with deprecating the EBL if it
> makes sense.

Thanks.

For what it's worth - I think it's worth revisiting that in the
future, combined for lightweight ARM and x86 platforms (and maybe
RISC-V), and through the magic of git it will be easy to resurrect at
that point.

For now, I mainly want to stop new platform ports being posted with both
EBL and UEFI Shell. (And I've not seen any using EBL for a good reason
in a long time.)

Regards,

Leif.

> 
> Thanks,
> 
> Andrew Fish
> 
> > 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 21:13 UTC|newest]

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