ResetSystem() was over-specified in the document. UEFI already documents
the behaviour of ResetSystem() sufficiently. Add notes on expected
behaviour when platform specific or standard interface methods are
available.
Resolves: #29
Signed-off-by: Grant Likely <grant.likely(a)arm.com>
---
source/chapter2-uefi.rst | 27 ++++++++++-----------------
1 file changed, 10 insertions(+), 17 deletions(-)
diff --git a/source/chapter2-uefi.rst b/source/chapter2-uefi.rst
index 0cbddff..8a3ff1a 100644
--- a/source/chapter2-uefi.rst
+++ b/source/chapter2-uefi.rst
@@ -175,23 +175,16 @@ and the OS must use a device driver to control the RTC.
UEFI Reset and Shutdown
-----------------------
-The UEFI Runtime service ResetSystem() must implement the following commands,
-for purposes of power management and system control.
-
-- EfiResetCold()
-- EfiResetShutdown()
- * EfiResetShutdown must not reboot the system.
-
-If firmware updates are supported through the Runtime Service of
-UpdateCapsule(), then ResetSystem() might need to support the following
-command:
-
-- EfiWarmReset()
-
-.. note:: On platforms implementing the Power State Coordination Interface
- specification [PSCI]_, it is still required that EBBR compliant
- Operating Systems calls to reset the system will go via Runtime Services
- and not directly to PSCI.
+ResetSystem() is required to be implemented in boot services, but it is
+optional for runtime services.
+During runtime services, the operating system should first attempt to
+use ResetSystem() to reset the system.
+If ResetSystem() returns EFI_UNSUPPORTED, then the OS may fall back to
+an architecture or platform specific mechanism.
+
+On AArch64 platforms implementing [PSCI]_,
+if ResetSystem() is not implemented then the Operating System should fall
+back to making a PSCI call to reset or shutdown the system.
Runtime Variable Access
-----------------------
--
2.13.0
For those of you dialing into the weekly EBBR call, the dial in details
have changed (see below). We'll use WebEx instead of Skype for Business
from here on.
Agenda 27/09/2018:
• YVR18 Recap
• Review meeting time
• Release schedule
• Get/SetVariable – once more with feeling
• reference platforms/qemu
Anyone is welcome to join. Feel free to pass this invitation along. Let
me know if anyone has trouble dialling/connecting to the SfB bridge.
Time: Every Thursday at 16:30-17:30 BST (8:30 PDT, 23:30 CST)
[1]
https://lists.linaro.org/pipermail/boot-architecture/2018-April/000419.html
g.
---
Grant Likely's Personal Room
https://arm-onsite.webex.com/meet/gralik01
Access code: 809 053 990
Join by phone
1-408-792-6300 Call-in toll number (US/Canada)
1-877-668-4490 Call-in toll-free number (US/Canada)
44-203-478-5285 Call-in toll number (UK)
08-002061177 Call-in toll-free (UK)
Access code: 809 053 990
More access numbers:
https://arm-onsite.webex.com/cmp3300/webcomponents/widget/globalcallin/glob…https://www.webex.com/pdf/tollfree_restrictions.pdf
Hello,
Can we add a discussion in upcoming meetings about the participation
of SMMU in the booting procedure?
In the past there's been a number of proposals on how to mitigate
attacks, were a rogue PCI card is inserted into the system.
Some of them include shutting down external DMA ports until the OS
explicitly powers them up or blocking DMA using BME bit etc
Keeping in mind this will enhance the security of devices would it
make sense to include it as a 'MUST' if the hardware is present or a
recommendation would be enough?
If we enable if a number of questions will rise as well such as, What
happens if the SMMU is already configured? Should the OS reconfigure
it ?
/Ilias
On 27/09/2018 22:19, Mark Brown wrote:
> On Thu, Sep 27, 2018 at 04:25:29PM +0100, Grant Likely wrote:
>
>> Anyone is welcome to join. Feel free to pass this invitation along. Let me
>> know if anyone has trouble dialling/connecting to the SfB bridge.
>
> Highlighting in case anyone else makes the same mistake I did today: the
> dial in details have changed, if you've copied them into your personal
> calendar or similar you'll need to update!
Oops! The current calendar invite is about to expire, and I'm going to
try and rearrange the meeting to be at the top of the hour (need to
coordinate with Linaro LEDGE SC meeting). There will be a new invite in
the near future.
Mark, I also maintain a regular calendar invite. Would you like me to
add you to that?
g.
>
>> Time: Every Thursday at 16:30-17:30 BST (8:30 PDT, 23:30 CST)
>>
>> [1]
>> https://lists.linaro.org/pipermail/boot-architecture/2018-April/000419.html
>>
>> g.
>>
>> ---
>> Grant Likely's Personal Room
>> https://arm-onsite.webex.com/meet/gralik01
>> Access code: 809 053 990
>>
>> Join by phone
>> 1-408-792-6300 Call-in toll number (US/Canada)
>> 1-877-668-4490 Call-in toll-free number (US/Canada)
>> 44-203-478-5285 Call-in toll number (UK)
>> 08-002061177 Call-in toll-free (UK)
>> Access code: 809 053 990
>>
>> More access numbers:
>> https://arm-onsite.webex.com/cmp3300/webcomponents/widget/globalcallin/glob…
>> https://www.webex.com/pdf/tollfree_restrictions.pdf
Hi all, There is a face to face EBBR meeting scheduled at Linaro Connect
YVR18. I’m setting up this Skype dial-in for those who won’t be on-site.
Time: Tuesday 18 Sept 2018 at 10:00-11:00 PDT
.........................................................................................................................................
Join online meeting
https://meet.lync.com/armh/grant.likely/97ATLDZ1
Join by Phone
+442033215213 (Dial-in Number) English (United Kingdom)
Find a local number
https://dialin.lync.com/7bdb65cd-97d0-44fe-bc03-bf8072eadc33
Conference ID:
14562158
Forgot your dial-in PIN?
https://dialin.lync.com/7bdb65cd-97d0-44fe-bc03-bf8072eadc33
.........................................................................................................................................
Hi all,
I'd like to use today's EBBR meeting to discuss the demo for Linaro
connect. It would be great if we can have several distro images and show
them booting on multiple boards without fuss. Let's coordinate on which
boards are feasable candidates to use and which OS images should be used.
Talk to you at 16:30BST.
Cheers,
g.
---
Every Thursday at 16:30 UTC/BST, 8:30 PST/PDT, 00:30 CST
(following UTC/BST daylight savings time shifts)
Online meeting: https://meet.lync.com/armh/grant.likely/YBY93TIK
Skype Web App: https://meet.lync.com/armh/grant.likely/YBY93TIK?sl=1
Phone +44 2033215213,, 4664465#
Find a local number:
https://dialin.lync.com/7bdb65cd-97d0-44fe-bc03-bf8072eadc33
Conference ID: 4664465
On 30/08/2018 15:19, Mark Brown wrote:
> On Thu, Aug 30, 2018 at 03:14:47PM +0100, Grant Likely wrote:
>
>> Online meeting: https://meet.lync.com/armh/grant.likely/YBY93TIK
>> Skype Web App: https://meet.lync.com/armh/grant.likely/YBY93TIK?sl=1
>
> I keep meaning to mention - these links never seem to work for me, I
> always have to join via phone. Not sure if it's just me or not.
>
Yeah, skype4business is a pain on Linux. Sadly it's the tool Arm pays
for. I've been meaning to see if Arm will supply a Bluejeans account for
these meetings.
Dial-in always works. You could also try the Skype4Business Android or
iOS apps.
g.
Hi all,
Today's EBBR meeting is cancelled due to conflicts with other meetings. We'll meet again next week.
g.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 03/08/2018 17:40, Mark Brown wrote:
> On Fri, Aug 03, 2018 at 05:34:05PM +0100, Grant Likely wrote:
>
>> Anyone familiar with Open Source Firmware Conference coming up in
>> September? Is this just a PC firmware thing, or do we have some U-Boot
>> involvement?
>>
>> https://osfc.io/
>
> Their CFP lists LinuxBoot, coreboot, U-Boot, TianoCore and ARM Trusted
> Firmware.
Their CFP lists that, but it seems to be mostly Coreboot and LinuxBoot
folks. I was on the Linuxboot call today, and they don't seem to have
much contact with people from U-Boot or other projects.
g.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
