System Initialization (SGI Mips): Difference between revisions

From OSDev.wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
Content added Content deleted
mNo edit summary
No edit summary
Line 1: Line 1:
{{Stub}}
{{Stub}}


At boottime, a SGI system will load the ARCS firmware which then initializes basic hardware (such as the framebuffer, serial ports, keyboard, and disks), test system functionality and optionally loads a primary bootloader or kernel in some way. Otherwise, it gives the user a graphical menu if a keyboard has been attached.
At boottime, a SGI system will load the ARCS firmware which then initializes basic hardware (such as the framebuffer, serial ports, keyboard, and disks), test system functionality and optionally loads a primary bootloader or kernel. Otherwise, it gives the user a graphical menu if a keyboard has been attached.

The ARCS firmware was made in both 32 bit and 64 bit versions. The 32 bit versions are loosely based on the [[ARC]] firmware specification, but as with all ARC systems there were several deviations. The differences between the 32 bit and 64 bit version are not well documented. A system with a 64 bit processor does not necessarily have a 64 bit firmware - the Power Indigo 2, Indigo 2 R10000, Origin, Onyx 2, and Octane are 64 bit ARCS, for example, but the Indy, which has a 64 bit processor, runs a 32 bit version of ARCS.

The ARCS firmware expects a boot payload in ECOFF format, an extended variant of [[COFF]]. The 64 bit version of ARCS *may* support ELF, but more research is needed.


[[Category:MIPS]]
[[Category:MIPS]]

Revision as of 18:31, 3 May 2019

This page is a stub.
You can help the wiki by accurately adding more contents to it.

At boottime, a SGI system will load the ARCS firmware which then initializes basic hardware (such as the framebuffer, serial ports, keyboard, and disks), test system functionality and optionally loads a primary bootloader or kernel. Otherwise, it gives the user a graphical menu if a keyboard has been attached.

The ARCS firmware was made in both 32 bit and 64 bit versions. The 32 bit versions are loosely based on the ARC firmware specification, but as with all ARC systems there were several deviations. The differences between the 32 bit and 64 bit version are not well documented. A system with a 64 bit processor does not necessarily have a 64 bit firmware - the Power Indigo 2, Indigo 2 R10000, Origin, Onyx 2, and Octane are 64 bit ARCS, for example, but the Indy, which has a 64 bit processor, runs a 32 bit version of ARCS.

The ARCS firmware expects a boot payload in ECOFF format, an extended variant of COFF. The 64 bit version of ARCS *may* support ELF, but more research is needed.