tjhancocks/vboot

A bootloader for the Veracyon Project.

vboot's Issues

Create a rudimentary stub kernel for testing multiboot compliance.

There needs to be a very basic multiboot compliant kernel created for testing the generated multiboot info structure produced. This stub kernel should be installed into all test disk images so that it can be used by vboot in testing.

Ensure reading and parsing of ELF files is done correctly.

Currently the bootloader only does the bare minimum parsing on the ELF kernel to get it to run, and makes assumptions of best case scenario. It currently neglects to handle section headers and thus is ignoring sections such as the __mbHeader and bss. These are both required to get the kernel correctly laid out in memory (so that it knows what the kernel requires, and where the end of the kernel actually is.

Generate a basic multiboot information structure that will be passed to the kernel.

The bootloader needs to produce an information structure to pass to the kernel describing information that has been determined about the hardware and environment. The following information is provided via the Multiboot Information structure:

• Flags & Version Number
• Amount of Memory (mem_lower and mem_upper)
• Boot Device and partition information
• Command line information
• Boot module list
• Aout/ELF symbol list
• Memory map information
• Drive information
• ROM configuration tables
• Bootloader Name
• APM information
• VBE information

All of this information is provided to the kernel via a struct multiboot_info structure.

A tool for installing the vboot bootloader into a disk image/disk.

There needs to be a way to easily install the bootloader onto a disk image or physical disk without having to use dd and manually calculate offsets. This tool should be able to consider any of the file systems that vboot supports, which is currently only RawFS (however future file systems should be considered).