From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/5] subject: efi_loader: add HII database protocol
Date: Wed, 23 Jan 2019 14:11:33 +0900 [thread overview]
Message-ID: <20190123051132.GH20286@linaro.org> (raw)
In-Reply-To: <9e56d840-3a9d-b0ce-6276-1e652eb540c2@gmx.de>
Heinrich,
On Tue, Jan 22, 2019 at 10:13:52PM +0100, Heinrich Schuchardt wrote:
> On 1/22/19 10:48 AM, Alexander Graf wrote:
> >
> >
> > On 21.01.19 04:12, AKASHI Takahiro wrote:
> >> HII database protocol is the last missing (major?) piece of code so that
> >> we can run unmodified EDKII's shell and UEFI SCT on EFI-enabled u-boot.
> >>
> >> The original code was initially written by Leif and Rob a year ago[1],
> >> and now I'm reworking it. The implementation has not been much
> >> enhanced from the original, but I tried to give it clearer implementation
> >> to be able to add more functionality easily later on.
> >> I also addressed the comments by Alex[2] and added a self test on
> >> request of Heinrich.
> >>
> >> HII configuration routing protocol and access protocol have only
> >> a skeleton and should be implemented when we need to have *drivers*
> >> that require configuration mechanism.
> >
> > Reviewed-by: Alexander Graf <agraf@suse.de>
> >
> > But I'll wait for Heinrich's ok as well :)
> >
> >
> > Alex
> >
> I have seen that Takahiro has integrated my recent suggestions.
>
> Currently I am still trying to understand what is wrong with
> GetNextVariableName().
Thank you for finding and investigating this issue.
I almost all of my time test my patches on arm64 primarily :)
-Takahiro Akashi
> So let's go with your review.
>
> Best regards
>
> Heinrich
next prev parent reply other threads:[~2019-01-23 5:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 3:12 [U-Boot] [PATCH v3 0/5] subject: efi_loader: add HII database protocol AKASHI Takahiro
2019-01-21 3:12 ` [U-Boot] [PATCH v3 1/5] efi_loader: Initial HII database protocols AKASHI Takahiro
[not found] ` <154824847481.44817.15540110415651237647@achrid.arch.suse.de>
2019-02-09 16:19 ` [U-Boot] [U-Boot, v3, " Heinrich Schuchardt
2019-02-11 14:28 ` Alexander Graf
2019-02-12 1:41 ` AKASHI Takahiro
2019-01-21 3:12 ` [U-Boot] [PATCH v3 2/5] efi: hii: add guid package support AKASHI Takahiro
2019-01-21 3:12 ` [U-Boot] [PATCH v3 3/5] efi: hii: add keyboard layout " AKASHI Takahiro
2019-01-21 3:13 ` [U-Boot] [PATCH v3 4/5] efi: hii: add HII config routing/access protocols AKASHI Takahiro
2019-01-21 3:13 ` [U-Boot] [PATCH v3 5/5] efi_selftest: add HII database protocols test AKASHI Takahiro
2019-01-22 9:48 ` [U-Boot] [PATCH v3 0/5] subject: efi_loader: add HII database protocol Alexander Graf
2019-01-22 21:13 ` Heinrich Schuchardt
2019-01-23 5:11 ` AKASHI Takahiro [this message]
2019-01-23 6:35 ` Alexander Graf
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=20190123051132.GH20286@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