HP Moonshot 1500 Chassis User Manual Page 109

  • Download
  • Add to my manuals
  • Print
  • Page
    / 189
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 108
Table 70 Boot option parameters (continued)
Parameter data (non-volatile unless otherwise noted)#Parameter
parameter data. It is a notification flag only, it is
not a resource lock. The MC does not provide any
interlock mechanism that would prevent other
software from writing parameter data.
Reserved11b =
Data 1 — MC boot flag valid bit clearing. Default = 00000b.3MC boot flag valid bit
clearing (semi-volatile)
1
Reserved[7:5]
Do not clear valid bit on reset/power cycle caused
by PEF. Not supported in Moonshot.
1b =[4]
Do not automatically clear boot flag valid bit if
chassis control command is not received
1b =[3]
within 60-second timeout (countdown restarts when
a chassis control command is received).
Do not clear valid bit on reset/power cycle caused
by watchdog timeout.
1b =[2]
Do not clear valid bit on push button reset/soft-reset
(such as “Ctrl-Alt-Del”). Not supported in Moonshot.
1b =[1]
Do not clear valid bit on power up via power push
button or wake event. Not supported in Moonshot.
1b =[0]
These flags are used to allow individual parties to track whether they have
already seen and handled the boot information. Applications that deal with
4Boot info acknowledge
(semi-volatile)
1
boot information should check the boot information and clear their
corresponding bit after consuming the boot options data.
Data 1: Write mask (write-only). This field is returned as 00h when read. This
is to eliminate the need for the MC to provide storage for the write mask field.
Enable write to bit 7 of data field1b =[7]
Enable write to bit 6 of data field1b =[6]
Enable write to bit 5 of data field1b =[5]
Enable write to bit 4 of data field1b =[4]
Enable write to bit 3 of data field1b =[3]
Enable write to bit 2 of data field1b =[2]
Enable write to bit 1 of data field1b =[1]
Enable write to bit 0 of data field1b =[0]
Data 2: Boot initiator acknowledge data. The boot initiator should typically
write FFh to this parameter before initiating the boot. The boot initiator may
write 0’s if it wants to intentionally direct a given party to ignore the boot info.
This field is automatically initialized to 00h when the management controller
is first powered up or reset.
Reserved. Write as 1b. Ignore on read.[7]
Reserved. Write as 1b. Ignore on read.[6]
Reserved. Write as 1b. Ignore on read.[5]
OEM has handled boot information.0b =[4]
SMS has handled boot information.0b =[3]
OS/service partition has handled boot information.0b =[2]
Standard command specification 109
Page view 108
1 2 ... 104 105 106 107 108 109 110 111 112 113 114 ... 188 189

Comments to this Manuals

No comments