First commit, Vystem v0.1

docs/blastproof/bootprocess.md

@@ -0,0 +1,35 @@
+# Blastproof boot process
+
+Blastproof boot process follow a very rigid sequences of steps that are detailled below:
+
+- Printing informations:
+  - Bootloader version
+  - Firmware informations
+  - CPU informations
+- Reading boot password from EFI console
+- Verifying integrity of integrated keys (see SBFIE)
+- Acquiring access to ESP partition
+  - Acquiring loaded image handle
+  - Acquiring BlockIO protocol for ESP partition
+  - Acquiring filesystem protocol (Blastproof doesn't have an integrated FAT32 driver)
+  - Opening root folder
+- Performing cryptographic checks with internal keys on his own files (see SBFIE)
+- Readind, parsing and applying boot configuration
+- Locating Simple Graphic Protocol (GOP) handle
+- Identify a suitable graphic output format, based on configuration, or highest resolution available in case of fallback
+- Loading and rendering bitmap font according to selected graphic output format
+- Loading, rendering and playing boot animation if configuration allow it
+- Loading InitFS and SignSyst
+  - Listing all availables BlockIO protocol
+  - Locating handles for InitFS and SignSyst
+  - Allocating memory for them
+  - Loading them into RAM
+  - Parsing their headers
+  - Performing cryptographic checks to validate their headers and contents
+- Loading the kernel
+  - Loading Shelter and Keycard binary 
+  - Generating Shelter boot configuration
+  - Allocating pages for kernel sections
+  - Creating page table
+  - Parsing EFI Memory Map and transforming it into a understandable format for Vystem
+  - Jumping to kernel