public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Rafael Machado <rafaelrodrigues.machado@gmail.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Andrew Fish <afish@apple.com>, "Ni, Ruiyu" <ruiyu.ni@intel.com>,
	 "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: Question about memory map entries
Date: Thu, 2 Aug 2018 16:02:13 -0300	[thread overview]
Message-ID: <CACgnt78Q7RDrcoEbGmsXx+C-X_ThLhAXu61M_TPq-Jn=dG-vjQ@mail.gmail.com> (raw)
In-Reply-To: <d32f4203-0752-86a5-4f2e-4835fd72ec83@redhat.com>

Hi Laszlo

Got your point. Thanks for the comment.

I'll keep working on it.
In case someone has some other information or idea feel free to share.

Thanks
Rafael

Em qui, 2 de ago de 2018 às 14:48, Laszlo Ersek <lersek@redhat.com>
escreveu:

> On 08/02/18 18:42, Rafael Machado wrote:
> > Thanks Andrew and Laszlo for the clarification and guidance.
> >
> > About Laszlo questions
> >
> >> Is the reboot automatic (from the platform firmware), or application /
> >> user initiated?
> > Yes. We just do some clean up, finish the events and "return
> EFI_SUCCESS;"
>
> That's really strange. I don't think that's valid or expected behavior.
> If a boot option exits with success, then, as I understand it, the boot
> manager is expected to return to the setup UI at once. (I don't have a
> reference ready for this, but I remember someone mentioning it.) Boot
> option processing continues only if the current boot option exits with
> failure.
>
> I think the reboot you see is actually a crash. (Not saying that the
> issue is in your application, just that the reboot should not be
> triggered by either the application or the platform firmware.)
>
> Thanks,
> Laszlo
>


  reply	other threads:[~2018-08-02 19:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29 19:05 Question about memory map entries Rafael Machado
2018-06-29 19:27 ` Yao, Jiewen
2018-06-30  1:31   ` Ni, Ruiyu
2018-06-30 12:02     ` Rafael Machado
2018-06-30 19:23       ` Andrew Fish
2018-08-02 12:39         ` Rafael Machado
2018-08-02 14:37           ` Andrew Fish
2018-08-02 14:44           ` Laszlo Ersek
2018-08-02 16:42             ` Rafael Machado
2018-08-02 17:48               ` Laszlo Ersek
2018-08-02 19:02                 ` Rafael Machado [this message]
2018-08-02 19:18                   ` Rafael Machado
2018-08-02 20:38                     ` Laszlo Ersek
2018-08-07 19:12                       ` Rafael Machado
2018-08-07 22:42                         ` Yao, Jiewen
2018-08-08 11:55                           ` Rafael Machado
2018-08-08 17:31                             ` Rafael Machado
2018-08-08 19:13                               ` Andrew Fish
2018-08-08 19:43                                 ` Rafael Machado

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='CACgnt78Q7RDrcoEbGmsXx+C-X_ThLhAXu61M_TPq-Jn=dG-vjQ@mail.gmail.com' \
    --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