SetupDesignGuide.pdf - Firmware Encoding Index

More documents

Recommendations

Info

Setup Design Guide DRAFT This keyword is used primarily when defining flags settings for certain operations. This keyword will primarily be used if a particular operation requires additional information from a hardware specific interface. The intention is that once the data is retrieved successfully, the bit will internally be turned off and a callback will not be done again. When doing a callback, a key will be passed to the driver who exported this data. The driver interprets the key and returns the appropriate data in an appropriate form. The compiler will ensure the key value specified is unique across the entire formset. A common scenario where this might be used is when a text op-code which prints CPU information is used and needs to print information like the CPU frequency. This obviously could not have been determined during the building of the VFR file. Example: text text = STR_CPU_FREQUENCY_TEXT, text = STR_CPU_DERIVED_TEXT, flags = DYNAMIC, key = CPU_FREQUENCY_KEY; More information about interacting with hardware is contained in section 2.6. 4.3.4 INTERACTIVE **Limit to one-of, text, and string, and numeric – any reason for other op-codes to be of this class?** This keyword is used primarily when defining flags settings for certain operations. This keyword will primarily be used if a particular operation requires additional information from a hardware specific interface. The intention is that once the initial data is retrieved successfully, the DYNAMIC bit will internally be disabled. This assumes that the infrastructure now has sufficient data to display initial data to the screen. The INTERACTIVE flag is not compatible with exporting data to runtime since it assumes callbacks to a driver which may not exist in the O/S runtime space. The use of this flag should be relegated to preboot only utilities. Once a user makes a selection on a tag that is interactive, a callback will be made to retrieve the data from a driver. A common use for this flag might be the entering of a modem configuration string, and returning data based on the resulting status from the modem. Example: string endstring; varid = NULL.ModemString, prompt = STR_MODEM_STRING_PROMPT, help = STR_MODEM_STRING_HELP, minsize = 1, maxsize = 60, flags = INTERACTIVE, key = MODEM_STRING_KEY, In the above example, a user would select the modem string prompt. After typing in the modem string to send to the modem (i.e. ATE1M0), a callback to the driver would send this packet of data to the modem. The modem will give some return code to the called driver. The driver will return back to the 38
Setup Design Guide DRAFT setup infrastructure with a particular return code and return packet. This packet (based on the keyword it is responding to) will contain some string data to print out. In the case of the above example, one might get returned a string stating “Modem Configured Without Errors”. The infrastructure will print that message, and return the user to the menu which contained the modem string prompt. More information about interacting with hardware is contained in section 2.6. 39
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 22 and 23: Setup Design Guide DRAFT The driver
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 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 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

SetupDesignGuide.pdf - Firmware Encoding Index

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?