UEFI Specification - Revision history

GHXX: /* Display setup */

2026-08-18T15:03:43Z

Display setup

← Older revision		Revision as of 15:03, 18 August 2026
Line 82:		Line 82:

	== Display setup ==		== Display setup ==
	Currently the built-in bootloader does set up display interaction and provide functions such as <code>print</code>. This however shall not be relied upon by operating systems. Instead every OS should set up its own display handling and clear the [[Gpu]]'s [[~~TextBuffer~~\|TextBuffers]] via <code>gpuUD:freeAllBuffers()</code>.		Currently the built-in bootloader does set up display interaction and provide functions such as <code>print</code>. This however shall not be relied upon by operating systems. Instead every OS should set up its own display handling and clear the Gpu's [[Gpu#TextBufferUD\|TextBuffers]] via <code>gpuUD:freeAllBuffers()</code>.


	{{Navbox content}}		{{Navbox content}}

GHXX at 17:26, 17 August 2026

2026-08-17T17:26:05Z

← Older revision		Revision as of 17:26, 17 August 2026
Line 15:		Line 15:
	!Description		!Description
	\|-		\|-
	\|bootDrive		\|<code>bootDrive</code>
	\|Yes		\|Yes
	\|<code>ManagedMassStorageUD</code> or <code>UnmanagedMassStorageUD</code> or <code>table</code>		\|<code>ManagedMassStorageUD</code> or <code>UnmanagedMassStorageUD</code> or <code>table</code>

GHXX at 17:23, 17 August 2026

2026-08-17T17:23:47Z

← Older revision		Revision as of 17:23, 17 August 2026
Line 27:		Line 27:
	\|}		\|}

	=== Beep codes ===		== Beep codes ==
	If you decide to use <code>computer:beep()</code> codes during the boot process, follow the tables below. Symbols with indicated range shall always use the maximum duration, if the beep code indicates an error. Between two non-pause symbols there shall be a pause of 0.25 seconds. It is not necessary to make use of all beep codes. For ease of readability it is best to not mix symbols of different durations.		If you decide to use <code>computer:beep()</code> codes during the boot process, follow the tables below. Symbols with indicated range shall always use the maximum duration, if the beep code indicates an error. Between two non-pause symbols there shall be a pause of 0.25 seconds. It is not necessary to make use of all beep codes. For ease of readability it is best to not mix symbols of different durations.
	{\| class="wikitable"		{\| class="wikitable"
Line 81:		Line 81:
	\|}		\|}

			== Display setup ==
			Currently the built-in bootloader does set up display interaction and provide functions such as <code>print</code>. This however shall not be relied upon by operating systems. Instead every OS should set up its own display handling and clear the [[Gpu]]'s [[TextBuffer\|TextBuffers]] via <code>gpuUD:freeAllBuffers()</code>.


	{{Navbox content}}		{{Navbox content}}

GHXX at 13:23, 17 August 2026

2026-08-17T13:23:14Z

← Older revision		Revision as of 13:23, 17 August 2026
Line 17:		Line 17:
	\|bootDrive		\|bootDrive
	\|Yes		\|Yes
	\|<code>ManagedMassStorageUD</code>		\|<code>ManagedMassStorageUD</code> or <code>UnmanagedMassStorageUD</code> or <code>table</code>
	or <code>UnmanagedMassStorageUD</code>
	or <code>table</code>
	\|The instance of [[ManagedMassStorage]] (or [[UnmanagedMassStorage]]) that <code>boot.lua</code> was loaded from. Without this, an OS has no way of knowing which disk was selected in a dual-boot environment. In case such an component is not available, for example during a network-boot, bootloader must provide a table that provides the same fields of either Managed- or UnmanagedMassStorage.		\|The instance of [[ManagedMassStorage]] (or [[UnmanagedMassStorage]]) that <code>boot.lua</code> was loaded from. Without this, an OS has no way of knowing which disk was selected in a dual-boot environment. In case such an component is not available, for example during a network-boot, bootloader must provide a table that provides the same fields of either Managed- or UnmanagedMassStorage.
	Note: Neither bootloaders nor OSes are required to support booting from UnmanagedMassStorages nor network.		Note: Neither bootloaders nor OSes are required to support booting from UnmanagedMassStorages nor network.
Line 25:		Line 23:
	\|<code>_*</code>		\|<code>_*</code>
	\|No		\|No
	\|		\|any
	\|Any custom, non-standard values starting with an underscore may be added to this table, for any kind of purpose. OSes may make use of them but cannot expect them to always be present. Always precede custom values with an underscore as to not run into a conflict with future versions of this spec.		\|Any custom, non-standard values starting with an underscore may be added to this table, for any kind of purpose. OSes may make use of them but cannot expect them to always be present. Always precede custom values with an underscore as to not run into a conflict with future versions of this spec.
	\|}		\|}

GHXX at 13:22, 17 August 2026

2026-08-17T13:22:37Z

@@ Line 1: / Line 1: @@
 {{Warning|Currently this spec is still under construction and thus neither followed by the built-in [[UEFI]], nor by [[Advanced OS]]. This however will change in the future.}}
-This page intends to describe an interface between the [[UEFI]] bootloaders and operating systems such as [[Advanced OS]]. As the name "bootloader" implies, the purpose is to find and boot an operating system, either from a local disk or over the network. Additionally, the bootloader may want to set up printing
+This page intends to describe an interface between the [[UEFI]] bootloaders and operating systems such as [[Advanced OS]]. As the name "bootloader" implies, the purpose is to find and boot an operating system, either from a local disk or over the network. Additionally, the bootloader may want to set up printing for easily facilitating user interaction and displaying errors. For solely indicating boot-errors, one can also resort to beep-codes via `computer:beep()` as indicated below.
 {{Navbox content}}

GHXX at 11:56, 17 August 2026

2026-08-17T11:56:56Z

← Older revision		Revision as of 11:56, 17 August 2026
Line 1:		Line 1:
	{{Warning\|Currently this spec is neither followed by the built-in [[UEFI]], nor by [[Advanced OS]]~~, though this~~ will change in the future.}}		{{Warning\|Currently this spec is still under construction and thus neither followed by the built-in [[UEFI]], nor by [[Advanced OS]]. This however will change in the future.}}

	This page intends to describe an interface between the [[UEFI]] bootloaders and operating systems such as [[Advanced OS]]. As the name "bootloader" implies, the purpose is to find and boot an operating system, either from a local disk or over the network. Additionally, the bootloader may want to set up printing		This page intends to describe an interface between the [[UEFI]] bootloaders and operating systems such as [[Advanced OS]]. As the name "bootloader" implies, the purpose is to find and boot an operating system, either from a local disk or over the network. Additionally, the bootloader may want to set up printing

GHXX at 11:56, 17 August 2026

2026-08-17T11:56:20Z

← Older revision		Revision as of 11:56, 17 August 2026
Line 1:		Line 1:
	{{~~Note~~\|Currently this spec is neither followed by the built-in [[UEFI]], nor by [[Advanced OS]], though this will change in the future.}}		{{Warning\|Currently this spec is neither followed by the built-in [[UEFI]], nor by [[Advanced OS]], though this will change in the future.}}

	This page intends to describe an interface between the [[UEFI]] bootloaders and operating systems such as [[Advanced OS]]. As the name "bootloader" implies, the purpose is to find and boot an operating system, either from a local disk or over the network. Additionally, the bootloader may want to set up printing		This page intends to describe an interface between the [[UEFI]] bootloaders and operating systems such as [[Advanced OS]]. As the name "bootloader" implies, the purpose is to find and boot an operating system, either from a local disk or over the network. Additionally, the bootloader may want to set up printing

GHXX: Created page with "{{Note|Currently this spec is neither followed by the built-in UEFI, nor by Advanced OS, though this will change in the future.}} This page intends to describe an interface between the UEFI bootloaders and operating systems such as Advanced OS. As the name "bootloader" implies, the purpose is to find and boot an operating system, either from a local disk or over the network. Additionally, the bootloader may want to set up printing {{Navbox content}}"

2026-08-17T11:56:01Z

Created page with "{{Note|Currently this spec is neither followed by the built-in UEFI, nor by Advanced OS, though this will change in the future.}} This page intends to describe an interface between the UEFI bootloaders and operating systems such as Advanced OS. As the name "bootloader" implies, the purpose is to find and boot an operating system, either from a local disk or over the network. Additionally, the bootloader may want to set up printing {{Navbox content}}"

New page

{{Note|Currently this spec is neither followed by the built-in [[UEFI]], nor by [[Advanced OS]], though this will change in the future.}}

This page intends to describe an interface between the [[UEFI]] bootloaders and operating systems such as [[Advanced OS]]. As the name "bootloader" implies, the purpose is to find and boot an operating system, either from a local disk or over the network. Additionally, the bootloader may want to set up printing

{{Navbox content}}