]>
Commit | Line | Data |
---|---|---|
959ccb23 | 1 | \r |
2 | /** @file\r | |
3 | PI PEI master include file. This file should match the PI spec.\r | |
4 | \r | |
5 | Copyright (c) 2006 - 2007, Intel Corporation \r | |
6 | All rights reserved. This program and the accompanying materials \r | |
7 | are licensed and made available under the terms and conditions of the BSD License \r | |
8 | which accompanies this distribution. The full text of the license may be found at \r | |
9 | http://opensource.org/licenses/bsd-license.php \r | |
10 | \r | |
11 | THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS, \r | |
12 | WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED. \r | |
13 | \r | |
14 | Module Name: PiPeiCis.h\r | |
15 | \r | |
16 | @par Revision Reference:\r | |
17 | Version 1.0.\r | |
18 | \r | |
19 | **/\r | |
20 | \r | |
21 | #ifndef __PI_PEICIS_H__\r | |
22 | #define __PI_PEICIS_H__\r | |
23 | \r | |
24 | #include <Pi/PiMultiPhase.h>\r | |
25 | \r | |
26 | #define EFI_NOT_AVAILABLE_YET EFIERR (28)\r | |
27 | \r | |
28 | //\r | |
29 | // Handles of EFI FV/FFS.\r | |
30 | // \r | |
31 | typedef VOID *EFI_PEI_FV_HANDLE;\r | |
32 | typedef VOID *EFI_PEI_FILE_HANDLE;\r | |
33 | \r | |
34 | //\r | |
35 | // Declare forward referenced data structures\r | |
36 | //\r | |
37 | typedef struct _EFI_PEI_SERVICES EFI_PEI_SERVICES;\r | |
38 | typedef struct _EFI_PEI_NOTIFY_DESCRIPTOR EFI_PEI_NOTIFY_DESCRIPTOR;\r | |
39 | \r | |
40 | \r | |
41 | #include <Ppi/CpuIo.h>\r | |
42 | #include <Ppi/PciCfg2.h>\r | |
43 | \r | |
44 | /**\r | |
45 | The PEI Dispatcher will invoke each PEIM one time. During this pass, the PEI \r | |
46 | Dispatcher will pass control to the PEIM at the AddressOfEntryPoint in the PE Header. \r | |
47 | \r | |
48 | @param FfsHeader Pointer to the FFS file header.\r | |
49 | @param PeiServices Describes the list of possible PEI Services.\r | |
50 | \r | |
51 | @return Status code\r | |
52 | \r | |
53 | **/\r | |
54 | typedef\r | |
55 | EFI_STATUS\r | |
56 | (EFIAPI *EFI_PEIM_ENTRY_POINT)(\r | |
57 | IN EFI_FFS_FILE_HEADER *FfsHeader,\r | |
58 | IN EFI_PEI_SERVICES **PeiServices\r | |
59 | );\r | |
60 | \r | |
61 | /**\r | |
62 | Entry point of the notification callback function itself within the PEIM.\r | |
63 | \r | |
64 | @param PeiServices Indirect reference to the PEI Services Table.\r | |
65 | @param NotifyDescriptor Address of the notification descriptor data structure.\r | |
66 | @param Ppi Address of the PPI that was installed.\r | |
67 | \r | |
68 | @return Status code\r | |
69 | \r | |
70 | **/\r | |
71 | typedef\r | |
72 | EFI_STATUS\r | |
73 | (EFIAPI *EFI_PEIM_NOTIFY_ENTRY_POINT) (\r | |
74 | IN EFI_PEI_SERVICES **PeiServices,\r | |
75 | IN EFI_PEI_NOTIFY_DESCRIPTOR *NotifyDescriptor,\r | |
76 | IN VOID *Ppi\r | |
77 | );\r | |
78 | \r | |
79 | //\r | |
80 | // PEI Ppi Services List Descriptors\r | |
81 | //\r | |
82 | #define EFI_PEI_PPI_DESCRIPTOR_PIC 0x00000001\r | |
83 | #define EFI_PEI_PPI_DESCRIPTOR_PPI 0x00000010\r | |
84 | #define EFI_PEI_PPI_DESCRIPTOR_NOTIFY_CALLBACK 0x00000020\r | |
85 | #define EFI_PEI_PPI_DESCRIPTOR_NOTIFY_DISPATCH 0x00000040\r | |
86 | #define EFI_PEI_PPI_DESCRIPTOR_NOTIFY_TYPES 0x00000060\r | |
87 | #define EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST 0x80000000\r | |
88 | \r | |
89 | typedef struct {\r | |
90 | UINTN Flags;\r | |
91 | EFI_GUID *Guid;\r | |
92 | VOID *Ppi;\r | |
93 | } EFI_PEI_PPI_DESCRIPTOR;\r | |
94 | \r | |
95 | struct _EFI_PEI_NOTIFY_DESCRIPTOR {\r | |
96 | UINTN Flags;\r | |
97 | EFI_GUID *Guid;\r | |
98 | EFI_PEIM_NOTIFY_ENTRY_POINT Notify;\r | |
99 | };\r | |
100 | \r | |
101 | //\r | |
102 | // Describes request of the module to be loaded to \r | |
103 | // the permanent memory once it is available. Unlike most of the other HOBs, \r | |
104 | // this HOB is produced and consumed during the HOB producer phase.\r | |
105 | // \r | |
106 | typedef struct _EFI_HOB_LOAD_PEIM {\r | |
107 | EFI_HOB_GENERIC_HEADER Header;\r | |
108 | EFI_PEI_FILE_HANDLE FileHandle;\r | |
109 | EFI_PEIM_ENTRY_POINT EntryPoint;\r | |
110 | EFI_PEIM_ENTRY_POINT InMemEntryPoint;\r | |
111 | } EFI_HOB_LOAD_PEIM;\r | |
112 | \r | |
113 | \r | |
114 | /**\r | |
115 | This service is the first one provided by the PEI Foundation. This function \r | |
116 | installs an interface in the PEI PPI database by GUID. The purpose of the \r | |
117 | service is to publish an interface that other parties can use to call \r | |
118 | additional PEIMs.\r | |
119 | \r | |
120 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table\r | |
121 | published by the PEI Foundation.\r | |
122 | @param PpiList A pointer to the list of interfaces that the caller shall install.\r | |
123 | \r | |
124 | @retval EFI_SUCCESS The interface was successfully installed.\r | |
125 | @retval EFI_INVALID_PARAMETER The PpiList pointer is NULL or Any of the PEI PPI descriptors in the list do not have the EFI_PEI_PPI_DESCRIPTOR_PPI bit set in the Flags field.\r | |
126 | @retval EFI_OUT_OF_RESOURCES There is no additional space in the PPI database.\r | |
127 | \r | |
128 | **/\r | |
129 | typedef\r | |
130 | EFI_STATUS\r | |
131 | (EFIAPI *EFI_PEI_INSTALL_PPI) (\r | |
132 | IN EFI_PEI_SERVICES **PeiServices,\r | |
133 | IN EFI_PEI_PPI_DESCRIPTOR *PpiList\r | |
134 | );\r | |
135 | \r | |
136 | /**\r | |
137 | This function reinstalls an interface in the PEI PPI database by GUID. \r | |
138 | The purpose of the service is to publish an interface that other parties \r | |
139 | can use to replace a same-named interface in the protocol database \r | |
140 | with a different interface. \r | |
141 | \r | |
142 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table\r | |
143 | published by the PEI Foundation.\r | |
144 | @param OldPpi A pointer to the former PPI in the database.\r | |
145 | @param NewPpi A pointer to the new interfaces that the caller shall install.\r | |
146 | \r | |
147 | @retval EFI_SUCCESS The interface was successfully installed.\r | |
148 | @retval EFI_INVALID_PARAMETER The PpiList pointer is NULL or Any of the PEI PPI descriptors in the \r | |
149 | list do not have the EFI_PEI_PPI_DESCRIPTOR_PPI bit set in the Flags field.\r | |
150 | @retval EFI_OUT_OF_RESOURCES There is no additional space in the PPI database.\r | |
151 | @retval EFI_NOT_FOUND The PPI for which the reinstallation was requested has not been installed.\r | |
152 | \r | |
153 | **/\r | |
154 | typedef\r | |
155 | EFI_STATUS\r | |
156 | (EFIAPI *EFI_PEI_REINSTALL_PPI) (\r | |
157 | IN EFI_PEI_SERVICES **PeiServices,\r | |
158 | IN EFI_PEI_PPI_DESCRIPTOR *OldPpi,\r | |
159 | IN EFI_PEI_PPI_DESCRIPTOR *NewPpi\r | |
160 | );\r | |
161 | \r | |
162 | /**\r | |
163 | This function locates an interface in the PEI PPI database by GUID. \r | |
164 | \r | |
165 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES published by the PEI Foundation.\r | |
166 | @param Guid A pointer to the GUID whose corresponding interface needs to be found.\r | |
167 | @param Instance The N-th instance of the interface that is required.\r | |
168 | @param PpiDescriptor A pointer to instance of the EFI_PEI_PPI_DESCRIPTOR.\r | |
169 | @param Ppi A pointer to the instance of the interface.\r | |
170 | \r | |
171 | @retval EFI_SUCCESS The interface was successfully returned.\r | |
172 | @retval EFI_NOT_FOUND The PPI descriptor is not found in the database.\r | |
173 | \r | |
174 | **/\r | |
175 | typedef\r | |
176 | EFI_STATUS\r | |
177 | (EFIAPI *EFI_PEI_LOCATE_PPI) (\r | |
178 | IN EFI_PEI_SERVICES **PeiServices,\r | |
179 | IN EFI_GUID *Guid,\r | |
180 | IN UINTN Instance,\r | |
181 | IN OUT EFI_PEI_PPI_DESCRIPTOR **PpiDescriptor,\r | |
182 | IN OUT VOID **Ppi\r | |
183 | );\r | |
184 | \r | |
185 | /**\r | |
186 | This function installs a notification service to be called back when a \r | |
187 | given interface is installed or reinstalled. The purpose of the service \r | |
188 | is to publish an interface that other parties can use to call additional PPIs \r | |
189 | that may materialize later.\r | |
190 | \r | |
191 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation\r | |
192 | @param NotifyList A pointer to the list of notification interfaces that the caller shall install.\r | |
193 | \r | |
194 | @retval EFI_SUCCESS The interface was successfully installed.\r | |
195 | @retval EFI_INVALID_PARAMETER The PpiList pointer is NULL or Any of the PEI PPI descriptors in the \r | |
196 | list do not have the EFI_PEI_PPI_DESCRIPTOR_PPI bit set in the Flags field.\r | |
197 | @retval EFI_OUT_OF_RESOURCES There is no additional space in the PPI database.\r | |
198 | \r | |
199 | **/\r | |
200 | typedef\r | |
201 | EFI_STATUS\r | |
202 | (EFIAPI *EFI_PEI_NOTIFY_PPI) (\r | |
203 | IN EFI_PEI_SERVICES **PeiServices,\r | |
204 | IN EFI_PEI_NOTIFY_DESCRIPTOR *NotifyList\r | |
205 | );\r | |
206 | \r | |
207 | /**\r | |
208 | This function returns the present value of the boot mode.\r | |
209 | \r | |
210 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r | |
211 | @param BootMode A pointer to contain the value of the boot mode.\r | |
212 | \r | |
213 | @retval EFI_SUCCESS The boot mode was returned successfully.\r | |
214 | \r | |
215 | **/\r | |
216 | typedef\r | |
217 | EFI_STATUS\r | |
218 | (EFIAPI *EFI_PEI_GET_BOOT_MODE) (\r | |
219 | IN EFI_PEI_SERVICES **PeiServices,\r | |
220 | OUT EFI_BOOT_MODE *BootMode\r | |
221 | );\r | |
222 | \r | |
223 | /**\r | |
224 | This function sets the value of the boot mode.\r | |
225 | \r | |
226 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation\r | |
227 | @param BootMode The value of the boot mode to set.\r | |
228 | \r | |
229 | @retval EFI_SUCCESS The boot mode was returned successfully.\r | |
230 | \r | |
231 | **/\r | |
232 | typedef\r | |
233 | EFI_STATUS\r | |
234 | (EFIAPI *EFI_PEI_SET_BOOT_MODE) (\r | |
235 | IN EFI_PEI_SERVICES **PeiServices,\r | |
236 | IN EFI_BOOT_MODE BootMode\r | |
237 | );\r | |
238 | \r | |
239 | /**\r | |
240 | This function returns the pointer to the list of Hand-Off Blocks (HOBs) in memory. \r | |
241 | \r | |
242 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation\r | |
243 | @param HobList A pointer to the list of HOBs that the PEI Foundation will initialize\r | |
244 | \r | |
245 | @retval EFI_SUCCESS The list was successfully returned.\r | |
246 | @retval EFI_NOT_AVAILABLE_YET The HOB list is not yet published.\r | |
247 | \r | |
248 | **/\r | |
249 | typedef\r | |
250 | EFI_STATUS\r | |
251 | (EFIAPI *EFI_PEI_GET_HOB_LIST) (\r | |
252 | IN EFI_PEI_SERVICES **PeiServices,\r | |
253 | IN OUT VOID **HobList\r | |
254 | );\r | |
255 | \r | |
256 | /**\r | |
257 | This service published by the PEI Foundation abstracts the creation of a Hand-Off Block's (HOB's) headers.\r | |
258 | \r | |
259 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r | |
260 | @param Type The type of HOB to be installed.\r | |
261 | @param Length The length of the HOB to be added.\r | |
262 | @param Hob The address of a pointer that will contain the HOB header.\r | |
263 | \r | |
264 | @retval EFI_SUCCESS The HOB was successfully created.\r | |
265 | @retval EFI_OUT_OF_RESOURCES There is no additional space for HOB creation.\r | |
266 | \r | |
267 | **/\r | |
268 | typedef\r | |
269 | EFI_STATUS\r | |
270 | (EFIAPI *EFI_PEI_CREATE_HOB) (\r | |
271 | IN EFI_PEI_SERVICES **PeiServices,\r | |
272 | IN UINT16 Type,\r | |
273 | IN UINT16 Length,\r | |
274 | IN OUT VOID **Hob\r | |
275 | );\r | |
276 | \r | |
277 | /**\r | |
278 | The purpose of the service is to abstract the capability of the PEI \r | |
279 | Foundation to discover instances of firmware volumes in the system. \r | |
280 | Given the input file pointer, this service searches for the next \r | |
281 | matching file in the Firmware File System (FFS) volume.\r | |
282 | \r | |
283 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r | |
284 | @param Instance This instance of the firmware volume to find. The value 0 is the Boot Firmware Volume (BFV).\r | |
285 | @param FwVolHeader Pointer to the firmware volume header of the volume to return.\r | |
286 | \r | |
287 | @retval EFI_SUCCESS The volume was found.\r | |
288 | @retval EFI_NOT_FOUND The volume was not found.\r | |
289 | @retval EFI_INVALID_PARAMETER FwVolHeader is NULL\r | |
290 | \r | |
291 | **/\r | |
292 | typedef\r | |
293 | EFI_STATUS\r | |
294 | (EFIAPI *EFI_PEI_FFS_FIND_NEXT_VOLUME2) (\r | |
295 | IN EFI_PEI_SERVICES **PeiServices,\r | |
296 | IN UINTN Instance,\r | |
297 | IN OUT EFI_FIRMWARE_VOLUME_HEADER **FwVolHeader\r | |
298 | );\r | |
299 | \r | |
300 | /**\r | |
301 | The purpose of the service is to abstract the capability of the PEI \r | |
302 | Foundation to discover instances of firmware files in the system. \r | |
303 | Given the input file pointer, this service searches for the next matching \r | |
304 | file in the Firmware File System (FFS) volume.\r | |
305 | \r | |
306 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r | |
307 | @param SearchType A filter to find files only of this type.\r | |
308 | @param FwVolHeader Pointer to the firmware volume header of the volume to search.This parameter \r | |
309 | must point to a valid FFS volume.\r | |
310 | @param FileHeader Pointer to the current file from which to begin searching.This pointer will be \r | |
311 | updated upon return to reflect the file found.\r | |
312 | \r | |
313 | @retval EFI_SUCCESS The file was found.\r | |
314 | @retval EFI_NOT_FOUND The file was not found.\r | |
315 | @retval EFI_NOT_FOUND The header checksum was not zero.\r | |
316 | \r | |
317 | **/\r | |
318 | typedef\r | |
319 | EFI_STATUS\r | |
320 | (EFIAPI *EFI_PEI_FFS_FIND_NEXT_FILE2) (\r | |
321 | IN EFI_PEI_SERVICES **PeiServices,\r | |
322 | IN EFI_FV_FILETYPE SearchType,\r | |
323 | IN EFI_FIRMWARE_VOLUME_HEADER *FwVolHeader,\r | |
324 | IN OUT EFI_FFS_FILE_HEADER **FileHeader\r | |
325 | );\r | |
326 | \r | |
327 | /**\r | |
328 | Given the input file pointer, this service searches for the next \r | |
329 | matching file in the Firmware File System (FFS) volume. \r | |
330 | \r | |
331 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r | |
332 | @param SectionType The value of the section type to find.\r | |
333 | @param FfsFileHeader A pointer to the file header that contains the set of sections to be searched.\r | |
334 | @param SectionData A pointer to the discovered section, if successful.\r | |
335 | \r | |
336 | @retval EFI_SUCCESS The section was found.\r | |
337 | @retval EFI_NOT_FOUND The section was not found.\r | |
338 | \r | |
339 | **/\r | |
340 | typedef\r | |
341 | EFI_STATUS\r | |
342 | (EFIAPI *EFI_PEI_FFS_FIND_SECTION_DATA2) (\r | |
343 | IN EFI_PEI_SERVICES **PeiServices,\r | |
344 | IN EFI_SECTION_TYPE SectionType,\r | |
345 | IN EFI_FFS_FILE_HEADER *FfsFileHeader,\r | |
346 | IN OUT VOID **SectionData\r | |
347 | );\r | |
348 | \r | |
349 | /**\r | |
350 | This function registers the found memory configuration with the PEI Foundation.\r | |
351 | \r | |
352 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r | |
353 | @param MemoryBegin The value of a region of installed memory\r | |
354 | @param MemoryLength The corresponding length of a region of installed memory.\r | |
355 | \r | |
356 | @retval EFI_SUCCESS The region was successfully installed in a HOB.\r | |
357 | @retval EFI_INVALID_PARAMETER MemoryBegin and MemoryLength are illegal for this system.\r | |
358 | @retval EFI_OUT_OF_RESOURCES There is no additional space for HOB creation.\r | |
359 | \r | |
360 | **/\r | |
361 | typedef\r | |
362 | EFI_STATUS\r | |
363 | (EFIAPI *EFI_PEI_INSTALL_PEI_MEMORY) (\r | |
364 | IN EFI_PEI_SERVICES **PeiServices,\r | |
365 | IN EFI_PHYSICAL_ADDRESS MemoryBegin,\r | |
366 | IN UINT64 MemoryLength\r | |
367 | );\r | |
368 | \r | |
369 | /**\r | |
370 | The purpose of the service is to publish an interface that allows \r | |
371 | PEIMs to allocate memory ranges that are managed by the PEI Foundation.\r | |
372 | \r | |
373 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r | |
374 | @param MemoryType The type of memory to allocate.\r | |
375 | @param Pages The number of contiguous 4 KB pages to allocate.\r | |
376 | @param Memory Pointer to a physical address. On output, the address is set to the base \r | |
377 | of the page range that was allocated.\r | |
378 | \r | |
379 | @retval EFI_SUCCESS The memory range was successfully allocated.\r | |
380 | @retval EFI_OUT_OF_RESOURCES The pages could not be allocated.\r | |
381 | @retval EFI_INVALID_PARAMETER Type is not equal to AllocateAnyPages.\r | |
382 | \r | |
383 | **/\r | |
384 | typedef\r | |
385 | EFI_STATUS\r | |
386 | (EFIAPI *EFI_PEI_ALLOCATE_PAGES) (\r | |
387 | IN EFI_PEI_SERVICES **PeiServices,\r | |
388 | IN EFI_MEMORY_TYPE MemoryType,\r | |
389 | IN UINTN Pages,\r | |
390 | IN OUT EFI_PHYSICAL_ADDRESS *Memory\r | |
391 | );\r | |
392 | \r | |
393 | /**\r | |
394 | The purpose of this service is to publish an interface that \r | |
395 | allows PEIMs to allocate memory ranges that are managed by the PEI Foundation.\r | |
396 | \r | |
397 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r | |
398 | @param Size The number of bytes to allocate from the pool.\r | |
399 | @param Buffer If the call succeeds, a pointer to a pointer to the allocated buffer; undefined otherwise.\r | |
400 | \r | |
401 | @retval EFI_SUCCESS The allocation was successful.\r | |
402 | @retval EFI_OUT_OF_RESOURCES There is not enough heap to allocate the requested size.\r | |
403 | \r | |
404 | **/\r | |
405 | typedef\r | |
406 | EFI_STATUS\r | |
407 | (EFIAPI *EFI_PEI_ALLOCATE_POOL) (\r | |
408 | IN EFI_PEI_SERVICES **PeiServices,\r | |
409 | IN UINTN Size,\r | |
410 | OUT VOID **Buffer\r | |
411 | );\r | |
412 | \r | |
413 | /**\r | |
414 | This service copies the contents of one buffer to another buffer.\r | |
415 | \r | |
416 | @param Destination Pointer to the destination buffer of the memory copy.\r | |
417 | @param Source Pointer to the source buffer of the memory copy\r | |
418 | @param Length Number of bytes to copy from Source to Destination.\r | |
419 | \r | |
420 | @return None\r | |
421 | \r | |
422 | **/\r | |
423 | typedef\r | |
424 | VOID\r | |
425 | (EFIAPI *EFI_PEI_COPY_MEM) (\r | |
426 | IN VOID *Destination,\r | |
427 | IN VOID *Source,\r | |
428 | IN UINTN Length\r | |
429 | );\r | |
430 | \r | |
431 | /**\r | |
432 | The service fills a buffer with a specified value.\r | |
433 | \r | |
434 | @param Buffer Pointer to the buffer to fill.\r | |
435 | @param Size Number of bytes in Buffer to fill.\r | |
436 | @param Value Value to fill Buffer with\r | |
437 | \r | |
438 | @return None\r | |
439 | \r | |
440 | **/\r | |
441 | typedef\r | |
442 | VOID\r | |
443 | (EFIAPI *EFI_PEI_SET_MEM) (\r | |
444 | IN VOID *Buffer,\r | |
445 | IN UINTN Size,\r | |
446 | IN UINT8 Value\r | |
447 | );\r | |
448 | \r | |
449 | /**\r | |
450 | This service publishes an interface that allows PEIMs to report status codes.\r | |
451 | \r | |
452 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r | |
453 | @param Type Indicates the type of status code being reported.\r | |
454 | @param Value Describes the current status of a hardware or\r | |
455 | software entity. This includes information about the class and\r | |
456 | subclass that is used to classify the entity as well as an operation.\r | |
457 | For progress codes, the operation is the current activity.\r | |
458 | For error codes, it is the exception.For debug codes,it is not defined at this time.\r | |
459 | @param Instance The enumeration of a hardware or software entity within\r | |
460 | the system. A system may contain multiple entities that match a class/subclass\r | |
461 | pairing. The instance differentiates between them. An instance of 0 indicates\r | |
462 | that instance information is unavailable, not meaningful, or not relevant.\r | |
463 | Valid instance numbers start with 1.\r | |
464 | @param CallerId This optional parameter may be used to identify the caller.\r | |
465 | This parameter allows the status code driver to apply different rules to\r | |
466 | different callers.\r | |
467 | @param Data This optional parameter may be used to pass additional data.\r | |
468 | \r | |
469 | @retval EFI_SUCCESS The function completed successfully.\r | |
470 | @retval EFI_NOT_AVAILABLE_YET No progress code provider has installed an interface in the system.\r | |
471 | \r | |
472 | **/\r | |
473 | typedef\r | |
474 | EFI_STATUS\r | |
475 | (EFIAPI *EFI_PEI_REPORT_STATUS_CODE) (\r | |
476 | IN EFI_PEI_SERVICES **PeiServices,\r | |
477 | IN EFI_STATUS_CODE_TYPE Type,\r | |
478 | IN EFI_STATUS_CODE_VALUE Value,\r | |
479 | IN UINT32 Instance,\r | |
480 | IN EFI_GUID *CallerId OPTIONAL,\r | |
481 | IN EFI_STATUS_CODE_DATA *Data OPTIONAL\r | |
482 | );\r | |
483 | \r | |
484 | /**\r | |
485 | Resets the entire platform.\r | |
486 | \r | |
487 | @param PeiServices An indirect pointer to the EFI_PEI_SERVICES\r | |
488 | table published by the PEI Foundation.\r | |
489 | \r | |
490 | @retval EFI_SUCCESS The function completed successfully.\r | |
491 | @retval EFI_NOT_AVAILABLE_YET The service has not been installed yet.\r | |
492 | \r | |
493 | **/\r | |
494 | typedef\r | |
495 | EFI_STATUS\r | |
496 | (EFIAPI *EFI_PEI_RESET_SYSTEM) (\r | |
497 | IN EFI_PEI_SERVICES **PeiServices\r | |
498 | );\r | |
499 | \r | |
500 | /**\r | |
501 | \r | |
502 | This service searches for files with a specific name, within\r | |
503 | either the specified firmware volume or all firmware volumes.\r | |
504 | The service returns a file handle of type EFI_PEI_FILE_HANDLE,\r | |
505 | which must be unique within the system.\r | |
506 | \r | |
507 | @param FileName A pointer to the name of the file to\r | |
508 | find within the firmware volume.\r | |
509 | \r | |
510 | @param VolumeHandle The firmware volume to search FileHandle\r | |
511 | Upon exit, points to the found file's\r | |
512 | handle or NULL if it could not be found.\r | |
513 | \r | |
514 | @retval EFI_SUCCESS File was found.\r | |
515 | \r | |
516 | @retval EFI_NOT_FOUND File was not found.\r | |
517 | \r | |
518 | @retval EFI_INVALID_PARAMETER VolumeHandle or FileHandle or\r | |
519 | FileName was NULL.\r | |
520 | \r | |
521 | \r | |
522 | **/\r | |
523 | typedef\r | |
524 | EFI_STATUS\r | |
525 | (EFIAPI *EFI_PEI_FFS_FIND_BY_NAME) (\r | |
526 | IN CONST EFI_GUID *FileName,\r | |
527 | IN CONST EFI_PEI_FV_HANDLE VolumeHandle,\r | |
528 | OUT EFI_PEI_FILE_HANDLE *FileHandle\r | |
529 | );\r | |
530 | \r | |
531 | \r | |
532 | /**\r | |
533 | \r | |
534 | @param FileName Name of the file.\r | |
535 | \r | |
536 | @param FileType File type. See EFI_FV_FILETYPE, which is\r | |
537 | defined in the Platform Initialization\r | |
538 | Firmware Storage Specification.\r | |
539 | \r | |
540 | @param FileAttributes Attributes of the file. Type\r | |
541 | EFI_FV_FILE_ATTRIBUTES is defined in\r | |
542 | the Platform Initialization Firmware\r | |
543 | Storage Specification.\r | |
544 | \r | |
545 | @param Buffer Points to the file's data (not the header).\r | |
546 | Not valid if EFI_FV_FILE_ATTRIB_MEMORY_MAPPED\r | |
547 | is zero.\r | |
548 | \r | |
549 | @param BufferSize Size of the file's data.\r | |
550 | \r | |
551 | **/\r | |
552 | typedef struct {\r | |
553 | EFI_GUID FileName;\r | |
554 | EFI_FV_FILETYPE FileType;\r | |
555 | EFI_FV_FILE_ATTRIBUTES FileAttributes;\r | |
556 | VOID *Buffer;\r | |
557 | UINT32 BufferSize;\r | |
558 | } EFI_FV_FILE_INFO;\r | |
559 | \r | |
560 | /**\r | |
561 | \r | |
562 | This function returns information about a specific file,\r | |
563 | including its file name, type, attributes, starting address and\r | |
564 | size. If the firmware volume is not memory mapped then the\r | |
565 | Buffer member will be NULL.\r | |
566 | \r | |
567 | @param FileHandle Handle of the file.\r | |
568 | \r | |
569 |