Skip to content
RevoGirl edited this page Mar 14, 2011 · 28 revisions

**What is RevoBoot? **

RevoBoot is a GUI less stage 2 bootloader based on Master Chief's "Revolution" - Revolution was a special kind of branch of Chameleon based on Apple's Boot 132.

That being said. RevoBoot is the successor of Revolution and is now being ripped up, dissected and re-thought by RevoGirl. She has continued to fine tune every aspect of what's required to boot OS X in the most direct way, with the aim of keeping the bootloader as small, quick and tidy as possible.

Overview of using Revolution

Revolution is not a one size fits all bootloader, as it needs to be tailored to suit each system it's going to be used on. That happens at the source code level and therefore needs to be compiled specifically by you for your hardware. This allowed us to make RevoBoot what it is today. The smallest and fastest bootloader out on the market. Not the most practical or easiest bootloader.

Source Code Organization

RevoGirl has engineered the code to have a config folder, and in this config folder are the files which need to be changed. This keeps thing simple for us and less daunting for a new user as we only have to concentrate on four files.

Config Files

Looking at Revolutions' source code, drill down to /i386/config and you will find three folders, ACPI, EFI and SMBIOS, each containing a file named data.h. Static data for your system can be added to these data.h files in a structured way to enable you to benefit from a faster boot. For example, your DSDT.aml can be added to /i386/config/ACPI/data.h which will then be compiled inside Revolution. The result being the bootloader no longer needs to search for the file on disk to load at boot time.

Though note: These files don't have to be populated straight away as Revolution can still load your files from the /Extra folder on your boot volume.

Along with the three customisable data.h files, there is also a lose data.h file and settings.h file in /i386/config. The data.h file doesn't need to be touched and should remain where it is as it's part of the source code. Though the settings.h file is your master controller file, containing all the switches that can be turned on or off to direct the compiler code to include for your personal boot file.