15.03.2015 Views

SetupDesignGuide.pdf - Firmware Encoding Index

SetupDesignGuide.pdf - Firmware Encoding Index

SetupDesignGuide.pdf - Firmware Encoding Index

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Setup Design Guide<br />

DRAFT<br />

7.3 EFI Form Callback Protocol<br />

Summary<br />

The EFI_FORM_CALLBACK_PROTOCOL is the defined interface for access to custom NV storage<br />

devices as well as communication of user selections in a more interactive environment. This protocol<br />

should be published by hardware specific drivers which want to export access to custom hardware<br />

storage or publish IFR which has a requirement to call back the original driver.<br />

GUID<br />

#define EFI_FORM_CALLBACK_PROTOCOL_GUID \<br />

{ 0xf3e4543d, 0xcf35, 0x6cef, 0x35, 0xc4, 0x4f, 0xe6, \<br />

0x34, 0x4d, 0xfc, 0x54 }<br />

Protocol Interface Structure<br />

typedef struct _EFI_FORM_CALLBACK_PROTOCOL {<br />

EFI_NV_READ<br />

NvRead;<br />

EFI_NV_WRITE<br />

NvWrite;<br />

EFI_FORM_CALLBACK<br />

Callback;<br />

} EFI_FORM_CALLBACK_PROTOCOL;<br />

Parameters<br />

Read<br />

Write<br />

Callback<br />

This is the read operation to access the NV data serviced by a<br />

hardware specific driver.<br />

This is the write operation to access the NV data serviced by a<br />

hardware specific driver.<br />

This is the function that is called from the configuration browser to<br />

communicate key value pairs.<br />

Description<br />

This is the interface that is provided by hardware specific drivers that control access to non-system NV<br />

storage and support callbacks from the browser or HII.<br />

72

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!