SetupDesignGuide.pdf - Firmware Encoding Index

More documents

Recommendations

Info

Setup Design Guide DRAFT The driver will do the hardware interaction and return a packet of data to the database and it will fill in the appropriate string data. If the packet is returned successfully, the DYNAMIC flag is turned off. This string data would likely correlate to the initial list of file systems available on the system. This completes the first phase of interaction to acquire all the information the system needs to display data to the user. Additionally, when the user manually selects the file system they want to start searching, a callback to the exporting driver would occur and a packet would return the data requested. This would continue until the desired file was chosen. In the case where the driver which is exporting data bypasses the HII database and sends the data directly to the EFI configuration driver, the driver becomes responsible for the saving of the NVRAM data if any. Additionally, bypassing the HII database along with the multiple iteration callbacks are not compatible with runtime propagation. This use case would likely be used by pre-boot only utilities like the EFI Boot Maintenance Manager. Human Interface Infrastructure Database Consists of IFR/String/Font Which has been submitted by varying EFI drivers EFI Driver/Utility Requiring Dynamic Hardware Interaction EFI Configuration Driver Provides User Interface Support Callable by a Protocol Interface EFI Driver/Utility Requiring Dynamic Hardware Interaction Pre-boot Only and Responsible for storing NVRAM changes Additionally, a driver which required multiple iteration support could use the HII database so that the data might have a presence in the O/S runtime. The practical situation for this might be a driver which has a large amount of questions and possibly only a very small set which require multiple iteration support. In this case, the developer needs to be conscious when designing the page contents of the VFR script so that if the O/S runtime version of the data is stripped of op-codes with the INTERACTIVE flag turned on the user experience will not be odd. For instance, if a driver contains a page dedicated to modem initialization and the op-codes associated with that page are all set to INTERACTIVE, it might look very odd if the O/S runtime user is presented with a blank page which inferred there should be more data. 2.7 Setup Infrastructure Overview Graphic 22
Setup Design Guide DRAFT BDS Policy Engine for EFI Responsible for launching drivers and boot options. typedef struct { EFI_HII_PACKET EFI_HII_PACKET EFI_HII_PACKET } EFI_IFR_PACKET; *IFRData; *FontData; *StringData; Human Interface Infrastructure Database Consists of IFR/String/Font Data Which has been submitted by varying EFI drivers EFI Driver EFI Driver EFI Driver EFI Driver Requiring Dynamic Hardware Interaction If UseDatabase == TRUE, Retrieve all DBHandles, Ignore Packet/DriverPointer If UseDatabase == FALSE, process the Packet and DriverPointer. EFI Configuration Driver Provides User Interface Support Callable by a Protocol Interface typedef struct _EFI_CONFIGURATION_PROTOCOL { BOOLEAN UseDatabase; EFI_IFR_PACKET *Packet; OPTIONAL VOID *DriverPointer; OPTIONAL } EFI_CONFIGURATION_PROTOCOL 23
Page 1 and 2: Tiano Setup Design Guide Draft for
Page 3 and 4: Setup Design Guide DRAFT Revision H
Page 5 and 6: DRAFT 4.3 5 User Interface Design..
Page 7 and 8: DRAFT 1 Introduction 1.1 Scope This
Page 9 and 10: DRAFT RTC: Real Time Clock. The pie
Page 11: DRAFT Description: Status Codes Ret
Page 14 and 15: Setup Design Guide DRAFT VFR source
Page 16 and 17: Setup Design Guide DRAFT 2.1.5 HII
Page 18 and 19: Setup Design Guide DRAFT Human Inte
Page 20 and 21: Setup Design Guide DRAFT Human Inte
Page 24 and 25: Setup Design Guide DRAFT 3 Setup Bu
Page 26 and 27: Setup Design Guide DRAFT #define IF
Page 28 and 29: Setup Design Guide DRAFT ::= oneof
Page 30 and 31: Setup Design Guide DRAFT #strdef SP
Page 32 and 33: Setup Design Guide DRAFT should onl
Page 34 and 35: Setup Design Guide DRAFT 4.2.15 tim
Page 36 and 37: Setup Design Guide DRAFT 4.2.18 got
Page 38 and 39: Setup Design Guide DRAFT This keywo
Page 40 and 41: Setup Design Guide DRAFT 5 User Int
Page 42 and 43: Setup Design Guide DRAFT The area b
Page 44 and 45: Setup Design Guide DRAFT 6 Setup Dr
Page 46 and 47: Setup Design Guide DRAFT 7 HII Data
Page 48 and 49: Setup Design Guide DRAFT Related De
Page 50 and 51: Setup Design Guide DRAFT // // A fo
Page 52 and 53: Setup Design Guide DRAFT 7.1.1 EFI_
Page 62 and 63: Setup Design Guide DRAFT 7.1.10 EFI
Page 72 and 73:
Setup Design Guide DRAFT 7.3 EFI Fo
Page 74 and 75:
Setup Design Guide DRAFT EFI_SUCCES
Page 76 and 77:
Setup Design Guide DRAFT 7.3.3 EFI_
Page 78 and 79:
Setup Design Guide DRAFT 8 Simple I
Page 80 and 81:
Setup Design Guide DRAFT 9 HII Keyb
Page 82 and 83:
Setup Design Guide DRAFT // #define
Page 84 and 85:
Setup Design Guide DRAFT accent key
Page 86:
Setup Design Guide DRAFT proceeded
show all

SetupDesignGuide.pdf - Firmware Encoding Index

Create successful ePaper yourself

Delete template?

Save as template?