public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] efi_loader: update TODOs in doc/README.uefi
Date: Thu, 28 Mar 2019 17:12:42 +0900	[thread overview]
Message-ID: <20190328081240.GB9937@linaro.org> (raw)
In-Reply-To: <bfea318b-5b0d-575e-5203-0825f0f126f7@gmx.de>

On Thu, Mar 28, 2019 at 07:52:53AM +0100, Heinrich Schuchardt wrote:
> On 3/28/19 1:50 AM, AKASHI Takahiro wrote:
> > Hi Heinrich,
> >
> > As a matter of fact and strictly speaking, there are bunch of
> > missing features;
> > * Boot manager (section 3)
> >   - boot manager policy
> >   - support for some of Boot option variables
> >   - boot recovery
> > * various protocols,
> >   - from section 11 to section 20 and
> >   - from section 24 to section 30
> > * Firmware Update (Spec section 23)
> > * UEFI Byte Code(EBC) machine (Spec section 22)
> > * Secure boot (Spec section 31)
> > * Support for some of HII packages (section 33)
> > * HII configuration protocols (section 34)
> > * security&crypto-related protocols (section 36)
> > * Variables
> >   - support for authentication
> >
> > I don't think that we should list all of them, but we should definitely
> > describe the *criteria* for what features be implemented and what not.
> 
> Alex suggested to base the scope of our implementation on the minimum
> requirements of this document:

Yeah, I heard that but "minimum" is always a moving target and

> Server Base Boot Requirements System Software on ARM Platforms - Version 1.1
> https://developer.arm.com/docs/den0044/latest/server-base-boot-requirements-system-software-on-arm-platforms-version-11

this document yet has a much larger amount of requirements list
than current U-Boot supports.

-Takahiro Akashi

> >
> > # Personally, I'd like to add "integration of DM and UEFI objects" :)
> 
> The deficiencies that I listed in README.uefi are the user view.
> 
> I agree that we should also define our U-Boot internal development
> targets and better DM-UEFI integration should be part of it.
> 
> Best regards
> 
> Heinrich
> 
> >
> > Thanks,
> > -Takahiro Akashi
> >
> > On Wed, Mar 27, 2019 at 10:07:03PM +0100, Heinrich Schuchardt wrote:
> >> The following TODOs are closed:
> >>
> >> - GetNextVariableName is not implemented
> >> - event groups
> >> - manage events in a linked list
> >>
> >> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> >> ---
> >>  doc/README.uefi | 5 +----
> >>  1 file changed, 1 insertion(+), 4 deletions(-)
> >>
> >> diff --git a/doc/README.uefi b/doc/README.uefi
> >> index cda29cdcf7..b38efbc0cc 100644
> >> --- a/doc/README.uefi
> >> +++ b/doc/README.uefi
> >> @@ -299,7 +299,7 @@ This driver is only available if U-Boot is configured with
> >>      CONFIG_BLK=y
> >>      CONFIG_PARTITIONS=y
> >>
> >> -## TODOs as of U-Boot 2018.07
> >> +## TODOs as of U-Boot 2019.04
> >>
> >>  * unimplemented or incompletely implemented boot services
> >>    * Exit - call unload function, unload applications only
> >> @@ -308,16 +308,13 @@ This driver is only available if U-Boot is configured with
> >>
> >>  * unimplemented or incompletely implemented runtime services
> >>    * SetVariable() ignores attribute EFI_VARIABLE_APPEND_WRITE
> >> -  * GetNextVariableName is not implemented
> >>    * QueryVariableInfo is not implemented
> >>
> >>  * unimplemented events
> >>    * EVT_RUNTIME
> >>    * EVT_SIGNAL_VIRTUAL_ADDRESS_CHANGE
> >> -  * event groups
> >>
> >>  * data model
> >> -  * manage events in a linked list
> >>    * manage configuration tables in a linked list
> >>
> >>  * UEFI drivers
> >> --
> >> 2.20.1
> >>
> >
> 

      reply	other threads:[~2019-03-28  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 21:07 [U-Boot] [PATCH 1/1] efi_loader: update TODOs in doc/README.uefi Heinrich Schuchardt
2019-03-28  0:50 ` AKASHI Takahiro
2019-03-28  6:52   ` Heinrich Schuchardt
2019-03-28  8:12     ` AKASHI Takahiro [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-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=20190328081240.GB9937@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox