IntelÃ‚Â® Server System Server System "Emerald Ridge ... - CTL

More documents

Recommendations

Info

Intel® Server System "Emerald Ridge” Integrated Baseboard Management Controller EPSIPMI Command InterfaceOffsetNameLengthDescription06hBOT MinorRevisionBYTEThe revision in BCD number. For this version of thespecification the revision is 95h.07h Length WORD Length of the Boot order table structure09h Reserved BYTE ReservedData 0Ah Update flag BYTE Flag to indicate Boot order has been updated.0BhBoot OrderinformationVariesBit 0 = 1 if BIOS has updatedBit 1 = 1 if Chassis manager have updated and requestednew boot order.Other bits are reserved.At all other times the BIOS retains the existing boot order.Boot order information has two parts – the Boot order datafollowed by the Boot device name and path data.Boot order data specifies the system boot order and thedevice order within a particular device type. Each boot orderdata starts with Order type and Order length and is followedby an ordered list of device numbers. Boot order data endswith End boot order type 0FFh and is followed by 00h orderlength.BootOrderData0Bh forfirstentry.VariesforfurtherentriesDevice name/data contains description names of devices anddevice specific hardware path to uniquely identify the bootdevices in a compute server.Order type BYTE This field specifies the type of order,00h = System Boot order. This type will specify the order inwhich each boot device type should attempt to boot. This is amandatory order when BOT is implemented.The order of devices within each device type is specified byfollowing the Order types. The order type definition includeslegacy and EFI boot devices. Legacy boot device orderswithin a particular device class are optional. When absent theBIOS will follow the default enumeration for that device class.Compute servers that support UEFI/EFI, must implement EFIboot order.01h = Floppy disk drive (FDD) order03h = CD/DVD drive order05h = USB removable media order06h = Network device order08h = Local Hard disk drive (HDD) order09h = External HDD order80h = BEV device order10h = EFI boot order that specify order of EFI boot targets0C0h to 0DFh = OEM device types that can be used for OEMspecific devices0FFh = End of boot order type, which marks the end of theboot order lists and must be followed by 00h to indicate zerolength orderOther boot order types are reserved.Revision 1.1Intel ® Confidential 95
IPMI Command InterfaceIntel® Server System "Emerald Ridge” Integrated Baseboard Management Controller EPSOffsetNameLengthDescriptionVaries Order length BYTE The number of boot devices in a particular order list.VariesDevice orderlistOrderlengthThe ordered list of boot device types or boot devices.For System Boot order type, The Device list should containthe ordered list of device types. Each device type is a bytevalue and should be one of following device types: 01h =FDD; 08h = Local HDD; 03h = CD/DVD; 05h = USBremovable media; 06h = Network Device (PXE); 09h =external HDD; 80h = BEV; 10h = EFI Boot device.For legacy or OEM device order type, the Device list shallcontain ordered list of device numbers within particular devicetype. Each device number is a byte value and may have aname associated in Device name/path field.For EFI Boot order type, the Device list shall contain anordered list of EFI boot targets. Each boot target is a two bytenumber, as in an EFI BootOrder variable. The boot targetnumber associates the EFI boot device to Boot#### EFIvariable, where ‘####’ represent the boot target number. Eachboot target must have a device path in Device name/pathfield.Devicenameand Pathdata0Bh +SizeDeviceName/PathVariesThis field contains a device name (user readable description)and hardware path data for all devices in boot order data. Thename is optional for legacy and EFI boot devices, butmandatory for OEM devices. The device name/path datashould be used when boot devices are reported to the user.Each device name/path entry starts with a 3 byte device code.The first byte represents the order type that the device is partof, and the next 2 bytes represent the device number.For legacy devices and OEM devices, this field must use thefollowing format:Size in BytesType 1 Order typeNumber 2 Device numberName Varies Null terminated ASCIIstringFor EFI devices, this field also contains an EFI device path tothe boot target, which is mandatory. The device path mustcomply with the UEFI 2.0 specification. This field should havethe following format for EFI devices:Size in BytesType 1 Order type = 10hNumber 2 Device numberPath length 2 Size of the Devicepath in bytes.Name Varies Null terminatedUnicode string. Thestring is UTF-16encoding format asspecified in Unicode1.2 standard.96Intel ConfidentialRevision 1.1
Page 1:
Intel ® Server System "Emerald Rid
Page 4 and 5:
錯誤 ! 尚未定義樣式
Page 6 and 7:
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63: 錯誤 ! 尚未定義樣式
Page 70 and 71: Intel® Server System "Emerald Ridg
Page 156 and 157: Intel® Server System "Emerald "Rid
Page 162 and 163:
Intel® Server System "Emerald "Rid
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Intel® Server System "Emerald Ridg
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
show all

IntelÃ‚Â® Server System Server System "Emerald Ridge ... - CTL

Create successful ePaper yourself

Delete template?

Save as template?