From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] efi_loader: define development target in README.uefi
Date: Tue, 9 Apr 2019 10:49:35 +0900 [thread overview]
Message-ID: <20190409014933.GD21650@linaro.org> (raw)
In-Reply-To: <990db13a-a699-0135-3be5-d2a4e0b3169b@csgraf.de>
On Mon, Apr 01, 2019 at 01:28:24AM +0700, Alexander Graf wrote:
>
> On 28.03.19 14:11, Heinrich Schuchardt wrote:
> > Describe the target scope of the UEFI implementation in U-Boot.
> >
> > Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> > ---
> > doc/README.uefi | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/doc/README.uefi b/doc/README.uefi
> > index b38efbc0cc..66b6abece5 100644
> > --- a/doc/README.uefi
> > +++ b/doc/README.uefi
> > @@ -12,6 +12,15 @@ the interaction of drivers and applications with the firmware. The API comprises
> > access to block storage, network, and console to name a few. The Linux kernel
> > and boot loaders like GRUB or the FreeBSD loader can be executed.
> >
> > +## Development target
> > +
> > +The implementation of UEFI in U-Boot strives to reach the minimum requirements
> > +described in "Server Base Boot Requirements System Software on ARM Platforms -
> > +Version 1.1" [4].
> > +
> > +A full blown UEFI implementation would contradict the U-Boot design principle
> > +"keep it small".
>
>
> I'm not sure we ever want to be fully SBBR compliant. We might be, but
> it's not been a goal so far. We do however want to be *EBBR* compliant.
The current U-Boot still lacks lots of EBBR features.
Our 'minimum' set may be even much smaller than that.
-Takahiro Akashi
> Alex
>
>
> > +
> > ## Building for UEFI
> >
> > The UEFI standard supports only little-endian systems. The UEFI support can be
> > @@ -335,3 +344,5 @@ This driver is only available if U-Boot is configured with
> > http://uefi.org/specifications - UEFI specifications
> > * [2](./driver-model/README.txt) doc/driver-model/README.txt - Driver model
> > * [3](./README.iscsi) doc/README.iscsi - iSCSI booting with U-Boot and iPXE
> > +* [4](https://developer.arm.com/docs/den0044/latest/server-base-boot-requirements-system-software-on-arm-platforms-version-11)
> > + Server Base Boot Requirements System Software on ARM Platforms - Version 1.1
> > --
> > 2.20.1
> >
next prev parent reply other threads:[~2019-04-09 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 7:11 [U-Boot] [PATCH 1/1] efi_loader: define development target in README.uefi Heinrich Schuchardt
2019-03-31 18:28 ` Alexander Graf
2019-04-09 1:49 ` AKASHI Takahiro [this message]
2019-04-09 3:40 ` Heinrich Schuchardt
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-all 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=20190409014933.GD21650@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.