Re: 'fastboot boot' TPL

[Michael Zimmermann <sigmaepsilon92@gmail.com>]

> I agree. Did you run into any issues due to this?
Surprisingly no. I was just trying to understand the fastboot
implementation before I use it on my platform
and was surprised that this works at all. I can imagine that's because this
is supposed to load linux's efistub which probably doesn't do anything but
calling SetVirtualMemoryMap and ExitBootServices.
I can imagine that more complex loaders like the one used for Windows
wouldn't work this way.

On Wed, Feb 28, 2018 at 9:10 AM, Ard Biesheuvel <ard.biesheuvel@linaro.org>
wrote:

> On 28 February 2018 at 07:56, Michael Zimmermann
> <sigmaepsilon92@gmail.com> wrote:
> > I feel like both of you misunderstood my intention.
> > As I said in my initial mail, I'm not arguing the spec - I know that
> > StartImage must be called from TPL_APPLICATION.
> >
> > I'm just discussing a bug inside EmbeddedPkg/Application/AndroidFastboot
> -
> > because they actually do call StartImage from TPL_CALLBACK.
>
> I think the confusion is a result of the fact that you never mentioned
> that particular module/file until now.
>
> > As I proposed in my initial mail, we should not only fix that, but also
> add
> > tpl ASSERTs inside several BootServices to prevent this from happening in
> > future.
> >
>
> I agree. Did you run into any issues due to this?
>