Lines Matching full:firmware

2   This file provides control over block-oriented firmware devices.
41   @retval EFI_SUCCESS The firmware volume attributes were
53   The SetAttributes() function sets configurable firmware volume
54   attributes and returns the new settings of the firmware volume.
60                       desired firmware volume settings. On
62                       settings of the firmware volume. Type
66   @retval EFI_SUCCESS           The firmware volume attributes were returned.
70                                 as declared in the firmware
83   a memory-mapped firmware volume. This function should be called
84   only for memory-mapped firmware volumes.
91                   base address of the firmware volume.
93   @retval EFI_SUCCESS       The firmware volume base address was returned.
95   @retval EFI_UNSUPPORTED   The firmware volume is not memory mapped.
126   @retval EFI_SUCCESS             The firmware volume base address was returned.
145   Implementations should be mindful that the firmware volume
171   @retval EFI_SUCCESS         The firmware volume was read successfully,
179   @retval EFI_ACCESS_DENIED   The firmware volume is in the
202   firmware volume is sticky write, the caller must ensure that
206   unpredictability arises because, for a sticky-write firmware
214   mindful that the firmware volume might be in the WriteDisabled
217   contents of the firmware volume. The Write() function must
241   @retval EFI_SUCCESS         The firmware volume was written successfully.
248   @retval EFI_ACCESS_DENIED   The firmware volume is in the
272   Erases and initializes a firmware volume block.
277   requested that does not exist within the associated firmware
279   firmware volume), the EraseBlocks() function must return the
281   of the firmware volume. Implementations should be mindful that
282   the firmware volume might be in the WriteDisabled state. If it
285   the firmware volume. All calls to EraseBlocks() must be fully
308   @retval EFI_ACCESS_DENIED   The firmware volume is in the
312                             The firmware device may have been
316                                 not exist in the firmware volume.
327 /// The Firmware Volume Block Protocol is the low-level interface
328 /// to a firmware volume. File-level access to a firmware volume
329 /// should not be done using the Firmware Volume Block Protocol.
330 /// Normal access to a firmware volume must use the Firmware
332 /// produces the Firmware Volume Protocol will bind to the
333 /// Firmware Volume Block Protocol.
344   /// The handle of the parent firmware volume.