What is EFI_ALREADY_STARTED?
Quick note explaining EFI_ALREADY_STARTED for BIOS/UEFI and embedded firmware readers.
What is EFI_ALREADY_STARTED?
EFI_ALREADY_STARTED is a firmware-debugging concept used to understand return status, logs, commands, or failure points.
Why it matters
- Makes UEFI return values easier to interpret.
- Helps write safer error handling in drivers and applications.
- Useful when following service-call failures in debug logs.
Practical example
Example: do not use output parameters after a UEFI API returns an error. Check EFI_STATUS first, then decide whether to retry, allocate a larger buffer, or fail cleanly.
Quick checklist
- What API returned this status?
- Are input parameters, buffer size, and phase valid?
- Should the caller retry, allocate more memory, or fail cleanly?
Quick takeaway
EFI_ALREADY_STARTED is a small concept, but it often becomes important when reading logs or debugging real firmware.
Related notes
- What is _HID?
- What is _CRS?
- What is _DSM?
- What is Supported() in UEFI Driver Model?
- What is Start() in UEFI Driver Model?
Public references
Found this useful?
Save it or share it with someone learning firmware, BIOS/UEFI, and embedded systems.
Nội dung liên quan
Một số bài viết, ghi chú hoặc project có liên quan đến nội dung bạn vừa đọc.
What is EFI_BUFFER_TOO_SMALL?
Quick note explaining EFI_BUFFER_TOO_SMALL for BIOS/UEFI and embedded firmware readers.
What is EFI_STATUS?
Quick note explaining EFI_STATUS for BIOS/UEFI and embedded firmware readers.
What is Supported() in UEFI Driver Model?
Quick note explaining Supported() in UEFI Driver Model for BIOS/UEFI and embedded firmware readers.
Biến note thành bài viết hoàn chỉnh
Notes là nơi ghi nhanh khái niệm.