public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Andrew Fish <afish@apple.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
	edk2-devel-01 <edk2-devel@lists.01.org>
Subject: Re: falling back to UiApp?
Date: Wed, 26 Apr 2017 22:50:58 -0700	[thread overview]
Message-ID: <B33E1F23-FA61-4008-993D-91F5C0EBDFBF@apple.com> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5B93AF36@SHSMSX104.ccr.corp.intel.com>

Laszlo,

There is no platform policy in the UEFI spec by design. The spec is policy agnostic, as an ATM policy would be different from a server, etc. It's all implementation choice.
> On Apr 26, 2017, at 10:40 PM, Ni, Ruiyu <ruiyu.ni@intel.com> wrote:
> 
> Laszlo,
> I believe the "Unable to boot" message was added by intention.
> 
> I just checked the UEFI Spec Boot Manager chapter again, still I didn't
> find any wording to say what to do, when boot and recovery failure
> happens.
> 
> Putting "Unable to boot" message there is to tell platform developer
> that system is not in good state (no bootable option), helpful for debugging.
> 
> But rethinking about that, maybe I could also print a user-visible
> string "Unable to boot, press any key to enter Boot Manager Menu." to
> STD console and redirect to Boot Manager Menu when any key is received.
> 
> I still don't like to silently show UI when this failure happens.
> 
> What's your opinion?
> If you agree, could you please help submit a Bugzilla tracker?
> 
> Thanks/Ray
> 
>> -----Original Message-----
>> From: Laszlo Ersek [mailto:lersek@redhat.com]
>> Sent: Wednesday, April 26, 2017 10:23 PM
>> To: Ni, Ruiyu <ruiyu.ni@intel.com>
>> Cc: edk2-devel-01 <edk2-devel@lists.01.org>
>> Subject: falling back to UiApp?
>> 
>> Hi Ray,
>> 
>> the UiApp application is added to the UEFI boot order automatically, but it is not
>> invoked automatically, even if BDS gives up and hangs with
>> 
>>  [Bds] Unable to boot!
>> 
>> For example, consider the following:
>> - no UEFI bootable application available anywhere in the system,
>> - ... not even for the default platform recovery option,
>> - no shell is built into the firmware image,
>> - but UiApp is available in the firmware image.
>> 
>> Is it possible to jump to UiApp in this case, rather than hanging with
>> 
>>  [Bds] Unable to boot!
>> 
>> ?
>> 
>> Can (or should) platform code do something about this?
>> 
>> Or would this conflict with the UEFI spec either way?
>> 
>> Thank you,
>> Laszlo
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2017-04-27  5:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 14:23 falling back to UiApp? Laszlo Ersek
2017-04-27  5:40 ` Ni, Ruiyu
2017-04-27  5:50   ` Andrew Fish [this message]
2017-04-27  9:10   ` Laszlo Ersek

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=B33E1F23-FA61-4008-993D-91F5C0EBDFBF@apple.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