Lines Matching +full:firmware +full:- +full:name

2   The Firmware Volume Protocol provides file-level access to the firmware volume.
3   Each firmware volume driver must produce an instance of the
4   Firmware Volume Protocol if the firmware volume is to be visible to
5   the system during the DXE phase. The Firmware Volume Protocol also provides
6   mechanisms for determining and modifying some attributes of the firmware volume.
8   Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
9   SPDX-License-Identifier: BSD-2-Clause-Patent
81   Returns the attributes and current settings of the firmware volume.
83   Because of constraints imposed by the underlying firmware
84   storage, an instance of the Firmware Volume Protocol may not
87   firmware volume are exposed to the caller using the
100   @retval EFI_SUCCESS   The firmware volume attributes were
112   Modifies the current settings of the firmware volume according to the input parameter.
115   firmware volume attributes. Only EFI_FV_READ_STATUS,
123   does not affect the ability to read or write the firmware
134                         desired firmware volume settings. On
136                         settings of the firmware volume. On
138                         modified and the firmware volume
141   @retval EFI_SUCCESS           The requested firmware volume attributes
206   Retrieves a file and/or file information from the firmware volume.
208   ReadFile() is used to retrieve any file from a firmware volume
210   the firmware volume media may be in any arbitrary format as long
211   as it does the following: It is accessed using the Firmware
213   format defined in Code Definitions: PI Firmware File Format.
218   - BufferSize is returned with the size that is required to
220   - The output parameters FoundType and *FileAttributes are
222   - The returned value of *AuthenticationStatus is undefined.
231   caller-allocated output buffer. If the output buffer is not
250                                 name. All firmware file names are EFI_GUIDs.
251                                 A single firmware volume must not have two
252                                 valid files with the same file name
259   @param  BufferSize            Pointer to a caller-allocated UINTN. It
263   @param  FoundType             Pointer to a caller-allocated EFI_FV_FILETYPE.
265   @param  FileAttributes        Pointer to a  caller-allocated
268   @param  AuthenticationStatus  Pointer to a caller-allocated
283   @retval EFI_NOT_FOUND               Name was not found in the firmware volume.
286                                       attempting to access the firmware volume.
288   @retval EFI_ACCESS_DENIED           The firmware volume is configured to
308   within a firmware volume. The section returned is determined
309   using a depth-first, left-to-right search algorithm through all
316   indicates the size of the caller-allocated output buffer. If
336                               file name from which the requested section
355   @param BufferSize           Pointer to a caller-allocated UINTN. It
359   @param AuthenticationStatus Pointer to a caller-allocated
366   @retval EFI_WARN_BUFFER_TOO_SMALL   The caller-allocated
376                           the firmware volume. EFI_NOT_FOUND The
381                             attempting to access the firmware
384   @retval EFI_ACCESS_DENIED The firmware volume is configured to
422   /// Pointer to a GUID, which is the file name to be written.
446   WriteFile() is used to write one or more files to a firmware
450   array is compatible with the firmware volume. Firmware volume
453   EFI_FV_RELIABLE_WRITE, the caller must check the firmware volume
455   firmware volume. EFI_FV_UNRELIABLE_WRITE must always be
457   (FileData[n].BufferSize == 0) deletes the file from the firmware
482   @retval EFI_OUT_OF_RESOURCES    The firmware volume does not
487                                   attempting to access the firmware volume.
489   @retval EFI_WRITE_PROTECTED     The firmware volume is
494                                   firmware volume.
519   Retrieves information about the next file in the firmware volume store
522   GetNextFile() is the interface that is used to search a firmware
532   re-initialized and starts at the beginning. Subsequent calls to
542 …@param Key        Pointer to a caller-allocated buffer that contains implementation-specific data …
544 …                  at least This->KeySize bytes long. To re-initialize the search and begin from the
545 …                 beginning of the firmware volume, the entire buffer must be cleared to zero. Other
549   @param FileType   Pointer to a caller-allocated
559   @param NameGuid   Pointer to a caller-allocated EFI_GUID. If a
560                     matching file is found, the file's name is
564   @param Attributes Pointer to a caller-allocated
572   @param Size       Pointer to a caller-allocated UINTN. If a
585                             attempting to access the firmware
588   @retval EFI_ACCESS_DENIED The firmware volume is configured to
605   Return information about a firmware volume.
608   InformationType for the requested firmware volume. If the volume
661   Sets information about a firmware volume.
664   on the requested firmware volume.
710 /// The Firmware Volume Protocol contains the file-level
711 /// abstraction to the firmware volume as well as some firmware
713 /// Firmware Volume Protocol is the interface used by all parts of
714 /// DXE that are not directly involved with managing the firmware
716 /// firmware volume implementations. A firmware volume may be a
718 /// for example. This level of firmware volume implementation
719 /// detail is not visible to the consumers of the Firmware Volume
738   /// Handle of the parent firmware volume.