.gitattributes

@@ -1,14 +1 @@
 config_templates/hbl_html/accessible-urls/accessible-urls.txt text eol=lf
-
-# Mark C++ "include" files as C++
-*.inc linguist-language=C++
-
-# Mark RapidJSON include as vendored
-libraries/include/stratosphere/rapidjson/** linguist-vendored
-
-# Mark emummc as vendored
-emummc/** linguist-vendored
-
-# Mark fatfs as vendored
-exosphere/mariko_fatal/source/fatfs/** linguist-vendored
-fusee/program/source/fatfs/** linguist-vendored

.github/ISSUE_TEMPLATE/bug_report.md

@@ -49,8 +49,6 @@ X.X.X</br>
      - [ Ex: Kosmos' distribution of Atmosphère ]
 - Do you have additional kips or sysmodules you're loading:
 - Homebrew software installed: [ * ]
-- EmuMMC or SysNAND:
-  - [ If using an EmuMMC, include whether it's partition-based or file-based. ]
 
 ### Additional context?
 

.gitignore

@@ -31,16 +31,12 @@
 
 # Executables
 *.exe
-*.lz4
 *.out
 *.app
 *.i*86
 *.x86_64
 *.hex
 
-# Deko3d shaders
-*.dksh
-
 # Switch Executables
 *.nso
 *.nro
@@ -79,32 +75,15 @@ dkms.conf
 *.nam
 *.til
 
-# Compiled python files.
+# KEYS file for sept-secondary.
 *.pyc
+sept/sept-secondary/KEYS.py
 
 .**/
 
-# macOS horseshittery
-.DS_Store
-
 # NOTE: make sure to make exceptions to this pattern when needed!
 *.bin
 *.enc
 
 **/out
 **/build
-**/lib
-**/build_nintendo_nx_arm64
-**/build_nintendo_nx_arm64_armv8a
-**/build_nintendo_nx_arm
-**/build_nintendo_nx_arm_armv8a
-**/build_nintendo_nx_arm_armv7a
-**/build_nintendo_nx_arm_armv4t
-**/build_nintendo_nx_x64
-**/build_nintendo_nx_x86
-
-tools/*/
-
-package3
-
-stratosphere/test/

Makefile

@@ -1,42 +1,144 @@
-ATMOSPHERE_BUILD_CONFIGS :=
-all: nx_release
-clean: clean-nx_release
+TOPTARGETS := all clean dist-no-debug dist
+AMSBRANCH := $(shell git symbolic-ref --short HEAD)
+AMSHASH := $(shell git rev-parse --short HEAD)
+AMSREV := $(AMSBRANCH)-$(AMSHASH)
 
-THIS_MAKEFILE     := $(abspath $(lastword $(MAKEFILE_LIST)))
-CURRENT_DIRECTORY := $(abspath $(dir $(THIS_MAKEFILE)))
+ifneq (, $(strip $(shell git status --porcelain 2>/dev/null)))
+    AMSREV := $(AMSREV)-dirty
+endif
 
-define ATMOSPHERE_ADD_TARGET
+COMPONENTS := fusee stratosphere mesosphere exosphere thermosphere troposphere libraries
 
-ATMOSPHERE_BUILD_CONFIGS += $(strip $1)
+all: $(COMPONENTS)
 
-$(strip $1):
-	@echo "Building $(strip $1)"
-	@$$(MAKE) -f $(CURRENT_DIRECTORY)/atmosphere.mk ATMOSPHERE_MAKEFILE_TARGET="$(strip $1)" ATMOSPHERE_BUILD_NAME="$(strip $2)" ATMOSPHERE_BOARD="$(strip $3)" ATMOSPHERE_CPU="$(strip $4)" $(strip $5)
+thermosphere:
+	$(MAKE) -C thermosphere all
 
-clean-$(strip $1):
-	@echo "Cleaning $(strip $1)"
-	@$$(MAKE) -f $(CURRENT_DIRECTORY)/atmosphere.mk clean ATMOSPHERE_MAKEFILE_TARGET="$(strip $1)" ATMOSPHERE_BUILD_NAME="$(strip $2)" ATMOSPHERE_BOARD="$(strip $3)" ATMOSPHERE_CPU="$(strip $4)" $(strip $5)
+exosphere: thermosphere
+	$(MAKE) -C exosphere all
 
-endef
+stratosphere: exosphere libraries
+	$(MAKE) -C stratosphere all
 
-define ATMOSPHERE_ADD_TARGETS
+mesosphere: exosphere libraries
+	$(MAKE) -C mesosphere all
 
-$(eval $(call ATMOSPHERE_ADD_TARGET, $(strip $1)_release, release, $(strip $2), $(strip $3), \
-    ATMOSPHERE_BUILD_SETTINGS="$(strip $4)" \
-))
+troposphere: stratosphere
+	$(MAKE) -C troposphere all
 
-$(eval $(call ATMOSPHERE_ADD_TARGET, $(strip $1)_debug, debug, $(strip $2), $(strip $3), \
-    ATMOSPHERE_BUILD_SETTINGS="$(strip $4) -DAMS_BUILD_FOR_DEBUGGING" ATMOSPHERE_BUILD_FOR_DEBUGGING=1 \
-))
+sept: exosphere
+	$(MAKE) -C sept all
 
-$(eval $(call ATMOSPHERE_ADD_TARGET, $(strip $1)_audit, audit, $(strip $2), $(strip $3), \
-    ATMOSPHERE_BUILD_SETTINGS="$(strip $4) -DAMS_BUILD_FOR_AUDITING" ATMOSPHERE_BUILD_FOR_DEBUGGING=1 ATMOSPHERE_BUILD_FOR_AUDITING=1 \
-))
+fusee: exosphere mesosphere stratosphere sept
+	$(MAKE) -C $@ all
 
-endef
+libraries:
+	$(MAKE) -C libraries all
 
-$(eval $(call ATMOSPHERE_ADD_TARGETS, nx, nx-hac-001, arm-cortex-a57,))
+clean:
+	$(MAKE) -C fusee clean
+	rm -rf out
 
-clean-all: $(foreach config,$(ATMOSPHERE_BUILD_CONFIGS),clean-$(config))
+dist-no-debug: all
+	$(eval MAJORVER = $(shell grep 'define ATMOSPHERE_RELEASE_VERSION_MAJOR\b' libraries/libvapours/include/vapours/ams/ams_api_version.h \
+		| tr -s [:blank:] \
+		| cut -d' ' -f3))
+	$(eval MINORVER = $(shell grep 'define ATMOSPHERE_RELEASE_VERSION_MINOR\b' libraries/libvapours/include/vapours/ams/ams_api_version.h \
+		| tr -s [:blank:] \
+		| cut -d' ' -f3))
+	$(eval MICROVER = $(shell grep 'define ATMOSPHERE_RELEASE_VERSION_MICRO\b' libraries/libvapours/include/vapours/ams/ams_api_version.h \
+		| tr -s [:blank:] \
+		| cut -d' ' -f3))
+	$(eval AMSVER = $(MAJORVER).$(MINORVER).$(MICROVER)-$(AMSREV))
+	rm -rf atmosphere-$(AMSVER)
+	rm -rf out
+	mkdir atmosphere-$(AMSVER)
+	mkdir atmosphere-$(AMSVER)/atmosphere
+	mkdir atmosphere-$(AMSVER)/sept
+	mkdir atmosphere-$(AMSVER)/switch
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/contents/0100000000000008
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/contents/010000000000000D
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/contents/010000000000002B
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/contents/0100000000000032
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/contents/0100000000000034
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/contents/0100000000000036
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/contents/0100000000000037
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/fatal_errors
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/config_templates
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/config
+	cp fusee/fusee-primary/fusee-primary.bin atmosphere-$(AMSVER)/atmosphere/reboot_payload.bin
+	cp fusee/fusee-mtc/fusee-mtc.bin atmosphere-$(AMSVER)/atmosphere/fusee-mtc.bin
+	cp fusee/fusee-secondary/fusee-secondary.bin atmosphere-$(AMSVER)/atmosphere/fusee-secondary.bin
+	cp fusee/fusee-secondary/fusee-secondary.bin atmosphere-$(AMSVER)/sept/payload.bin
+	cp sept/sept-primary/sept-primary.bin atmosphere-$(AMSVER)/sept/sept-primary.bin
+	cp sept/sept-secondary/sept-secondary.bin atmosphere-$(AMSVER)/sept/sept-secondary.bin
+	cp sept/sept-secondary/sept-secondary_00.enc atmosphere-$(AMSVER)/sept/sept-secondary_00.enc
+	cp sept/sept-secondary/sept-secondary_01.enc atmosphere-$(AMSVER)/sept/sept-secondary_01.enc
+	cp sept/sept-secondary/sept-secondary_dev_00.enc atmosphere-$(AMSVER)/sept/sept-secondary_dev_00.enc
+	cp sept/sept-secondary/sept-secondary_dev_01.enc atmosphere-$(AMSVER)/sept/sept-secondary_dev_01.enc
+	cp config_templates/BCT.ini atmosphere-$(AMSVER)/atmosphere/config/BCT.ini
+	cp config_templates/override_config.ini atmosphere-$(AMSVER)/atmosphere/config_templates/override_config.ini
+	cp config_templates/system_settings.ini atmosphere-$(AMSVER)/atmosphere/config_templates/system_settings.ini
+	cp -r config_templates/kip_patches atmosphere-$(AMSVER)/atmosphere/kip_patches
+	cp -r config_templates/hbl_html atmosphere-$(AMSVER)/atmosphere/hbl_html
+	cp stratosphere/boot2/boot2.nsp atmosphere-$(AMSVER)/atmosphere/contents/0100000000000008/exefs.nsp
+	cp stratosphere/dmnt/dmnt.nsp atmosphere-$(AMSVER)/atmosphere/contents/010000000000000D/exefs.nsp
+	cp stratosphere/erpt/erpt.nsp atmosphere-$(AMSVER)/atmosphere/contents/010000000000002B/exefs.nsp
+	cp stratosphere/eclct.stub/eclct.stub.nsp atmosphere-$(AMSVER)/atmosphere/contents/0100000000000032/exefs.nsp
+	cp stratosphere/fatal/fatal.nsp atmosphere-$(AMSVER)/atmosphere/contents/0100000000000034/exefs.nsp
+	cp stratosphere/creport/creport.nsp atmosphere-$(AMSVER)/atmosphere/contents/0100000000000036/exefs.nsp
+	cp stratosphere/ro/ro.nsp atmosphere-$(AMSVER)/atmosphere/contents/0100000000000037/exefs.nsp
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/contents/0100000000000032/flags
+	touch atmosphere-$(AMSVER)/atmosphere/contents/0100000000000032/flags/boot2.flag
+	mkdir -p atmosphere-$(AMSVER)/atmosphere/contents/0100000000000037/flags
+	touch atmosphere-$(AMSVER)/atmosphere/contents/0100000000000037/flags/boot2.flag
+	cp troposphere/reboot_to_payload/reboot_to_payload.nro atmosphere-$(AMSVER)/switch/reboot_to_payload.nro
+	cd atmosphere-$(AMSVER); zip -r ../atmosphere-$(AMSVER).zip ./*; cd ../;
+	rm -r atmosphere-$(AMSVER)
+	mkdir out
+	mv atmosphere-$(AMSVER).zip out/atmosphere-$(AMSVER).zip
+	cp fusee/fusee-primary/fusee-primary.bin out/fusee-primary.bin
 
-.PHONY: all clean clean-all $(foreach config,$(ATMOSPHERE_BUILD_CONFIGS), $(config) clean-$(config))
+dist: dist-no-debug
+	$(eval MAJORVER = $(shell grep 'define ATMOSPHERE_RELEASE_VERSION_MAJOR\b' libraries/libvapours/include/vapours/ams/ams_api_version.h \
+		| tr -s [:blank:] \
+		| cut -d' ' -f3))
+	$(eval MINORVER = $(shell grep 'define ATMOSPHERE_RELEASE_VERSION_MINOR\b' libraries/libvapours/include/vapours/ams/ams_api_version.h \
+		| tr -s [:blank:] \
+		| cut -d' ' -f3))
+	$(eval MICROVER = $(shell grep 'define ATMOSPHERE_RELEASE_VERSION_MICRO\b' libraries/libvapours/include/vapours/ams/ams_api_version.h \
+		| tr -s [:blank:] \
+		| cut -d' ' -f3))
+	$(eval AMSVER = $(MAJORVER).$(MINORVER).$(MICROVER)-$(AMSREV))
+	rm -rf atmosphere-$(AMSVER)-debug
+	mkdir atmosphere-$(AMSVER)-debug
+	cp fusee/fusee-primary/fusee-primary.elf atmosphere-$(AMSVER)-debug/fusee-primary.elf
+	cp fusee/fusee-mtc/fusee-mtc.elf atmosphere-$(AMSVER)-debug/fusee-mtc.elf
+	cp fusee/fusee-secondary/fusee-secondary.elf atmosphere-$(AMSVER)-debug/fusee-secondary.elf
+	cp sept/sept-primary/sept-primary.elf atmosphere-$(AMSVER)-debug/sept-primary.elf
+	cp sept/sept-secondary/sept-secondary.elf atmosphere-$(AMSVER)-debug/sept-secondary.elf
+	cp sept/sept-secondary/key_derivation/key_derivation.elf atmosphere-$(AMSVER)-debug/sept-secondary-key-derivation.elf
+	cp exosphere/exosphere.elf atmosphere-$(AMSVER)-debug/exosphere.elf
+	cp exosphere/lp0fw/lp0fw.elf atmosphere-$(AMSVER)-debug/lp0fw.elf
+	cp exosphere/sc7fw/sc7fw.elf atmosphere-$(AMSVER)-debug/sc7fw.elf
+	cp exosphere/rebootstub/rebootstub.elf atmosphere-$(AMSVER)-debug/rebootstub.elf
+	cp mesosphere/kernel_ldr/kernel_ldr.elf atmosphere-$(AMSVER)-debug/kernel_ldr.elf
+	cp stratosphere/ams_mitm/ams_mitm.elf atmosphere-$(AMSVER)-debug/ams_mitm.elf
+	cp stratosphere/boot/boot.elf atmosphere-$(AMSVER)-debug/boot.elf
+	cp stratosphere/boot2/boot2.elf atmosphere-$(AMSVER)-debug/boot2.elf
+	cp stratosphere/creport/creport.elf atmosphere-$(AMSVER)-debug/creport.elf
+	cp stratosphere/dmnt/dmnt.elf atmosphere-$(AMSVER)-debug/dmnt.elf
+	cp stratosphere/eclct.stub/eclct.stub.elf atmosphere-$(AMSVER)-debug/eclct.stub.elf
+	cp stratosphere/fatal/fatal.elf atmosphere-$(AMSVER)-debug/fatal.elf
+	cp stratosphere/loader/loader.elf atmosphere-$(AMSVER)-debug/loader.elf
+	cp stratosphere/pm/pm.elf atmosphere-$(AMSVER)-debug/pm.elf
+	cp stratosphere/ro/ro.elf atmosphere-$(AMSVER)-debug/ro.elf
+	cp stratosphere/sm/sm.elf atmosphere-$(AMSVER)-debug/sm.elf
+	cp stratosphere/spl/spl.elf atmosphere-$(AMSVER)-debug/spl.elf
+	cp stratosphere/erpt/erpt.elf atmosphere-$(AMSVER)-debug/erpt.elf
+	cd atmosphere-$(AMSVER)-debug; zip -r ../atmosphere-$(AMSVER)-debug.zip ./*; cd ../;
+	rm -r atmosphere-$(AMSVER)-debug
+	mv atmosphere-$(AMSVER)-debug.zip out/atmosphere-$(AMSVER)-debug.zip
+
+
+.PHONY: $(TOPTARGETS) $(COMPONENTS)

README.md

@@ -3,8 +3,7 @@
 =====
 
 ![License](https://img.shields.io/badge/License-GPLv2-blue.svg)
-[![Chat on Discord](https://img.shields.io/badge/Discord-5865f2?logo=discord&logoColor=white)](https://discordapp.com/invite/ZdqEhed)
-![Made with Notepad++](img/np++.png?raw=true)
+[![Chat on Discord](https://camo.githubusercontent.com/b4175720ede4f2621aa066ffbabb70ae30044679/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f636861742d446973636f72642d627269676874677265656e2e737667)](https://discordapp.com/invite/ZdqEhed)
 
 Atmosphère is a work-in-progress customized firmware for the Nintendo Switch.
 
@@ -14,6 +13,7 @@ Components
 Atmosphère consists of multiple components, each of which replaces/modifies a different component of the system:
 
 * Fusée: First-stage Loader, responsible for loading and validating stage 2 (custom TrustZone) plus package2 (Kernel/FIRM sysmodules), and patching them as needed. This replaces all functionality normally in Package1loader/NX Bootloader.
+    * Sept: Payload used to enable support for runtime key derivation on 7.0.0.
 * Exosphère: Customized TrustZone, to run a customized Secure Monitor
 * Thermosphère: EL2 EmuNAND support, i.e. backing up and using virtualized/redirected NAND images
 * Stratosphère: Custom Sysmodule(s), both Rosalina style to extend the kernel/provide new features, and of the loader reimplementation style to hook important system actions
@@ -27,6 +27,7 @@ This software is licensed under the terms of the GPLv2, with exemptions for spec
 You can find a copy of the license in the [LICENSE file](LICENSE).
 
 Exemptions:
+* The [yuzu emulator project](https://github.com/yuzu-emu/yuzu) is exempt from GPLv2 licensing and may (at its option) instead license any source code authored for the Atmosphère project as GPLv2 or later.
 * [Nintendo](https://github.com/Nintendo) is exempt from GPLv2 licensing and may (at its option) instead license any source code authored for the Atmosphère project under the Zero-Clause BSD license.
 
 Credits
@@ -37,7 +38,7 @@ In no particular order, we credit the following for their invaluable contributio
 
 * __switchbrew__ for the [libnx](https://github.com/switchbrew/libnx) project and the extensive [documentation, research and tool development](http://switchbrew.org) pertaining to the Nintendo Switch.
 * __devkitPro__ for the [devkitA64](https://devkitpro.org/) toolchain and libnx support.
-* __ReSwitched Team__ for additional [documentation, research and tool development](https://reswitched.github.io/) pertaining to the Nintendo Switch.
+* __ReSwitched Team__ for additional [documentation, research and tool development](https://reswitched.team/) pertaining to the Nintendo Switch.
 * __ChaN__ for the [FatFs](http://elm-chan.org/fsw/ff/00index_e.html) module.
 * __Marcus Geelnard__ for the [bcl-1.2.0](https://sourceforge.net/projects/bcl/files/bcl/bcl-1.2.0) library.
 * __naehrwert__ and __st4rk__ for the original [hekate](https://github.com/nwert/hekate) project and its hwinit code base.

atmosphere.mk

@@ -1,173 +0,0 @@
-#---------------------------------------------------------------------------------
-# pull in common atmosphere configuration
-#---------------------------------------------------------------------------------
-THIS_MAKEFILE     := $(abspath $(lastword $(MAKEFILE_LIST)))
-CURRENT_DIRECTORY := $(abspath $(dir $(THIS_MAKEFILE)))
-include $(CURRENT_DIRECTORY)/libraries/config/common.mk
-
-# Get Atmosphere version fields
-ATMOSPHERE_MAJOR_VERSION               := $(shell grep 'define ATMOSPHERE_RELEASE_VERSION_MAJOR\b' $(ATMOSPHERE_LIBRARIES_DIR)/libvapours/include/vapours/ams/ams_api_version.h | tr -s [:blank:] | cut -d' ' -f3)
-ATMOSPHERE_MINOR_VERSION               := $(shell grep 'define ATMOSPHERE_RELEASE_VERSION_MINOR\b' $(ATMOSPHERE_LIBRARIES_DIR)/libvapours/include/vapours/ams/ams_api_version.h | tr -s [:blank:] | cut -d' ' -f3)
-ATMOSPHERE_MICRO_VERSION               := $(shell grep 'define ATMOSPHERE_RELEASE_VERSION_MICRO\b' $(ATMOSPHERE_LIBRARIES_DIR)/libvapours/include/vapours/ams/ams_api_version.h | tr -s [:blank:] | cut -d' ' -f3)
-ATMOSPHERE_SUPPORTED_HOS_MAJOR_VERSION := $(shell grep 'define ATMOSPHERE_SUPPORTED_HOS_VERSION_MAJOR\b' $(ATMOSPHERE_LIBRARIES_DIR)/libvapours/include/vapours/ams/ams_api_version.h | tr -s [:blank:] | cut -d' ' -f3)
-ATMOSPHERE_SUPPORTED_HOS_MINOR_VERSION := $(shell grep 'define ATMOSPHERE_SUPPORTED_HOS_VERSION_MINOR\b' $(ATMOSPHERE_LIBRARIES_DIR)/libvapours/include/vapours/ams/ams_api_version.h | tr -s [:blank:] | cut -d' ' -f3)
-ATMOSPHERE_SUPPORTED_HOS_MICRO_VERSION := $(shell grep 'define ATMOSPHERE_SUPPORTED_HOS_VERSION_MICRO\b' $(ATMOSPHERE_LIBRARIES_DIR)/libvapours/include/vapours/ams/ams_api_version.h | tr -s [:blank:] | cut -d' ' -f3)
-
-ATMOSPHERE_VERSION := $(ATMOSPHERE_MAJOR_VERSION).$(ATMOSPHERE_MINOR_VERSION).$(ATMOSPHERE_MICRO_VERSION)-$(ATMOSPHERE_GIT_REVISION)
-
-dist: dist-no-debug
-	$(eval DIST_DIR = $(CURRENT_DIRECTORY)/$(ATMOSPHERE_OUT_DIR)/atmosphere-$(ATMOSPHERE_VERSION)-debug)
-	rm -rf $(DIST_DIR)
-	mkdir $(DIST_DIR)
-	cp $(CURRENT_DIRECTORY)/fusee/loader_stub/$(ATMOSPHERE_BOOT_OUT_DIR)/loader_stub.elf $(DIST_DIR)/fusee-loader-stub.elf
-	cp $(CURRENT_DIRECTORY)/fusee/program/$(ATMOSPHERE_BOOT_OUT_DIR)/program.elf $(DIST_DIR)/fusee-program.elf
-	cp $(CURRENT_DIRECTORY)/exosphere/loader_stub/$(ATMOSPHERE_OUT_DIR)/loader_stub.elf $(DIST_DIR)/exosphere-loader-stub.elf
-	cp $(CURRENT_DIRECTORY)/exosphere/program/$(ATMOSPHERE_OUT_DIR)/program.elf $(DIST_DIR)/exosphere-program.elf
-	cp $(CURRENT_DIRECTORY)/exosphere/warmboot/$(ATMOSPHERE_BOOT_OUT_DIR)/warmboot.elf $(DIST_DIR)/exosphere-warmboot.elf
-	cp $(CURRENT_DIRECTORY)/exosphere/mariko_fatal/$(ATMOSPHERE_OUT_DIR)/mariko_fatal.elf $(DIST_DIR)/exosphere-mariko-fatal.elf
-	cp $(CURRENT_DIRECTORY)/exosphere/program/sc7fw/$(ATMOSPHERE_BOOT_OUT_DIR)/sc7fw.elf $(DIST_DIR)/exosphere-sc7fw.elf
-	cp $(CURRENT_DIRECTORY)/exosphere/program/rebootstub/$(ATMOSPHERE_BOOT_OUT_DIR)/rebootstub.elf $(DIST_DIR)/exosphere-rebootstub.elf
-	cp $(CURRENT_DIRECTORY)/mesosphere/kernel_ldr/$(ATMOSPHERE_OUT_DIR)/kernel_ldr.elf $(DIST_DIR)/kernel_ldr.elf
-	cp $(CURRENT_DIRECTORY)/mesosphere/kernel/$(ATMOSPHERE_OUT_DIR)/kernel.elf $(DIST_DIR)/kernel.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/ams_mitm/$(ATMOSPHERE_OUT_DIR)/ams_mitm.elf $(DIST_DIR)/ams_mitm.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/boot/$(ATMOSPHERE_OUT_DIR)/boot.elf $(DIST_DIR)/boot.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/boot2/$(ATMOSPHERE_OUT_DIR)/boot2.elf $(DIST_DIR)/boot2.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/creport/$(ATMOSPHERE_OUT_DIR)/creport.elf $(DIST_DIR)/creport.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/cs/$(ATMOSPHERE_OUT_DIR)/cs.elf $(DIST_DIR)/cs.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/dmnt/$(ATMOSPHERE_OUT_DIR)/dmnt.elf $(DIST_DIR)/dmnt.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/dmnt.gen2/$(ATMOSPHERE_OUT_DIR)/dmnt.gen2.elf $(DIST_DIR)/dmnt.gen2.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/eclct.stub/$(ATMOSPHERE_OUT_DIR)/eclct.stub.elf $(DIST_DIR)/eclct.stub.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/erpt/$(ATMOSPHERE_OUT_DIR)/erpt.elf $(DIST_DIR)/erpt.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/fatal/$(ATMOSPHERE_OUT_DIR)/fatal.elf $(DIST_DIR)/fatal.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/htc/$(ATMOSPHERE_OUT_DIR)/htc.elf $(DIST_DIR)/htc.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/jpegdec/$(ATMOSPHERE_OUT_DIR)/jpegdec.elf $(DIST_DIR)/jpegdec.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/loader/$(ATMOSPHERE_OUT_DIR)/loader.elf $(DIST_DIR)/loader.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/LogManager/$(ATMOSPHERE_OUT_DIR)/LogManager.elf $(DIST_DIR)/LogManager.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/ncm/$(ATMOSPHERE_OUT_DIR)/ncm.elf $(DIST_DIR)/ncm.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/pgl/$(ATMOSPHERE_OUT_DIR)/pgl.elf $(DIST_DIR)/pgl.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/pm/$(ATMOSPHERE_OUT_DIR)/pm.elf $(DIST_DIR)/pm.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/ro/$(ATMOSPHERE_OUT_DIR)/ro.elf $(DIST_DIR)/ro.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/sm/$(ATMOSPHERE_OUT_DIR)/sm.elf $(DIST_DIR)/sm.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/spl/$(ATMOSPHERE_OUT_DIR)/spl.elf $(DIST_DIR)/spl.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/TioServer/$(ATMOSPHERE_OUT_DIR)/TioServer.elf $(DIST_DIR)/TioServer.elf
-	cp $(CURRENT_DIRECTORY)/stratosphere/memlet/$(ATMOSPHERE_OUT_DIR)/memlet.elf $(DIST_DIR)/memlet.elf
-	cp $(CURRENT_DIRECTORY)/troposphere/daybreak/daybreak.elf $(DIST_DIR)/daybreak.elf
-	cp $(CURRENT_DIRECTORY)/troposphere/haze/haze.elf $(DIST_DIR)/haze.elf
-	cp $(CURRENT_DIRECTORY)/troposphere/reboot_to_payload/reboot_to_payload.elf $(DIST_DIR)/reboot_to_payload.elf
-	cd $(DIST_DIR); zip -r ../atmosphere-$(ATMOSPHERE_VERSION)-debug.zip ./*; cd ../;
-	rm -rf $(DIST_DIR)
-
-dist-no-debug: package3 $(CURRENT_DIRECTORY)/$(ATMOSPHERE_OUT_DIR)
-	$(eval DIST_DIR = $(CURRENT_DIRECTORY)/$(ATMOSPHERE_OUT_DIR)/atmosphere-$(ATMOSPHERE_VERSION))
-	rm -rf $(CURRENT_DIRECTORY)/$(ATMOSPHERE_OUT_DIR)/*
-	rm -rf $(DIST_DIR)
-	mkdir $(DIST_DIR)
-	mkdir $(DIST_DIR)/atmosphere
-	mkdir $(DIST_DIR)/switch
-	mkdir -p $(DIST_DIR)/atmosphere/fatal_errors
-	mkdir -p $(DIST_DIR)/atmosphere/config_templates
-	mkdir -p $(DIST_DIR)/atmosphere/config
-	mkdir -p $(DIST_DIR)/atmosphere/flags
-	cp fusee/$(ATMOSPHERE_BOOT_OUT_DIR)/fusee.bin $(DIST_DIR)/atmosphere/reboot_payload.bin
-	cp fusee/$(ATMOSPHERE_BOOT_OUT_DIR)/package3 $(DIST_DIR)/atmosphere/package3
-	cp config_templates/stratosphere.ini $(DIST_DIR)/atmosphere/config_templates/stratosphere.ini
-	cp config_templates/override_config.ini $(DIST_DIR)/atmosphere/config_templates/override_config.ini
-	cp config_templates/system_settings.ini $(DIST_DIR)/atmosphere/config_templates/system_settings.ini
-	cp config_templates/exosphere.ini $(DIST_DIR)/atmosphere/config_templates/exosphere.ini
-	mkdir -p config_templates/kip_patches
-	cp -r config_templates/kip_patches $(DIST_DIR)/atmosphere/kip_patches
-	cp -r config_templates/hbl_html $(DIST_DIR)/atmosphere/hbl_html
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000008
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000000d
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000017
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000002b
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000032
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000034
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000036
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000037
-	#mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000003c
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000042
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000420
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000421
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000b240
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000d609
-	mkdir -p $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000d623
-	cp stratosphere/boot2/$(ATMOSPHERE_OUT_DIR)/boot2.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000008/exefs.nsp
-	cp stratosphere/dmnt/$(ATMOSPHERE_OUT_DIR)/dmnt.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000000d/exefs.nsp
-	cp stratosphere/cs/$(ATMOSPHERE_OUT_DIR)/cs.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000017/exefs.nsp
-	cp stratosphere/erpt/$(ATMOSPHERE_OUT_DIR)/erpt.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000002b/exefs.nsp
-	cp stratosphere/eclct.stub/$(ATMOSPHERE_OUT_DIR)/eclct.stub.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000032/exefs.nsp
-	cp stratosphere/fatal/$(ATMOSPHERE_OUT_DIR)/fatal.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000034/exefs.nsp
-	cp stratosphere/creport/$(ATMOSPHERE_OUT_DIR)/creport.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000036/exefs.nsp
-	cp stratosphere/ro/$(ATMOSPHERE_OUT_DIR)/ro.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000037/exefs.nsp
-	#cp stratosphere/jpegdec/$(ATMOSPHERE_OUT_DIR)/jpegdec.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000003c/exefs.nsp
-	cp stratosphere/pgl/$(ATMOSPHERE_OUT_DIR)/pgl.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000042/exefs.nsp
-	cp stratosphere/LogManager/$(ATMOSPHERE_OUT_DIR)/LogManager.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000420/exefs.nsp
-	cp stratosphere/htc/$(ATMOSPHERE_OUT_DIR)/htc.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000b240/exefs.nsp
-	cp stratosphere/dmnt.gen2/$(ATMOSPHERE_OUT_DIR)/dmnt.gen2.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000d609/exefs.nsp
-	cp stratosphere/TioServer/$(ATMOSPHERE_OUT_DIR)/TioServer.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/010000000000d623/exefs.nsp
-	cp stratosphere/memlet/$(ATMOSPHERE_OUT_DIR)/memlet.nsp $(DIST_DIR)/stratosphere_romfs/atmosphere/contents/0100000000000421/exefs.nsp
-	@build_romfs $(DIST_DIR)/stratosphere_romfs $(DIST_DIR)/atmosphere/stratosphere.romfs
-	rm -r $(DIST_DIR)/stratosphere_romfs
-	cp troposphere/reboot_to_payload/reboot_to_payload.nro $(DIST_DIR)/switch/reboot_to_payload.nro
-	cp troposphere/daybreak/daybreak.nro $(DIST_DIR)/switch/daybreak.nro
-	cp troposphere/haze/haze.nro $(DIST_DIR)/switch/haze.nro
-	cd $(DIST_DIR); zip -r ../atmosphere-$(ATMOSPHERE_VERSION).zip ./*; cd ../;
-	rm -rf $(DIST_DIR)
-	cp fusee/$(ATMOSPHERE_BOOT_OUT_DIR)/fusee.bin $(CURRENT_DIRECTORY)/$(ATMOSPHERE_OUT_DIR)/fusee.bin
-
-package3: emummc fusee stratosphere mesosphere exosphere troposphere
-	@python fusee/build_package3.py $(CURRENT_DIRECTORY) $(ATMOSPHERE_OUT_DIR) $(ATMOSPHERE_BOOT_OUT_DIR) $(ATMOSPHERE_GIT_HASH) $(ATMOSPHERE_MAJOR_VERSION) $(ATMOSPHERE_MINOR_VERSION) $(ATMOSPHERE_MICRO_VERSION) 0 $(ATMOSPHERE_SUPPORTED_HOS_MAJOR_VERSION) $(ATMOSPHERE_SUPPORTED_HOS_MINOR_VERSION) $(ATMOSPHERE_SUPPORTED_HOS_MICRO_VERSION) 0
-	@echo "Built package3!"
-
-emummc:
-	$(MAKE) -C $(CURRENT_DIRECTORY)/emummc all
-
-fusee: libexosphere_boot
-	@$(MAKE) --no-print-directory -C $(CURRENT_DIRECTORY)/fusee -f $(CURRENT_DIRECTORY)/fusee/fusee.mk ATMOSPHERE_CPU="$(strip $(ATMOSPHERE_BOOT_CPU))"
-
-exosphere: libexosphere libexosphere_boot
-	@$(MAKE) --no-print-directory -C $(CURRENT_DIRECTORY)/exosphere -f $(CURRENT_DIRECTORY)/exosphere/exosphere.mk ATMOSPHERE_CHECKED_LIBEXOSPHERE=1 ATMOSPHERE_CHECKED_BOOT_LIBEXOSPHERE=1
-
-stratosphere: fusee libstratosphere
-	@$(MAKE) --no-print-directory -C $(CURRENT_DIRECTORY)/stratosphere -f $(CURRENT_DIRECTORY)/stratosphere/stratosphere.mk ATMOSPHERE_CHECKED_LIBSTRATOSPHERE=1 ATMOSPHERE_CHECKED_FUSEE=1
-
-mesosphere: libmesosphere
-	@$(MAKE) --no-print-directory -C $(CURRENT_DIRECTORY)/mesosphere -f $(CURRENT_DIRECTORY)/mesosphere/mesosphere.mk ATMOSPHERE_CHECKED_LIBMESOSPHERE=1
-
-troposphere:
-	$(MAKE) -C $(CURRENT_DIRECTORY)/troposphere all
-
-libexosphere:
-	@$(MAKE) --no-print-directory -C $(ATMOSPHERE_LIBRARIES_DIR)/libexosphere -f $(ATMOSPHERE_LIBRARIES_DIR)/libexosphere/libexosphere.mk
-
-ifneq ($(strip $(ATMOSPHERE_LIBRARY_DIR)),$(strip $(ATMOSPHERE_BOOT_LIBRARY_DIR)))
-libexosphere_boot:
-	@$(MAKE) --no-print-directory -C $(ATMOSPHERE_LIBRARIES_DIR)/libexosphere -f $(ATMOSPHERE_LIBRARIES_DIR)/libexosphere/libexosphere.mk ATMOSPHERE_CPU="$(strip $(ATMOSPHERE_BOOT_CPU))"
-else
-libexosphere_boot: libexosphere
-endif
-
-libmesosphere:
-	@$(MAKE) --no-print-directory -C $(ATMOSPHERE_LIBRARIES_DIR)/libmesosphere -f $(ATMOSPHERE_LIBRARIES_DIR)/libmesosphere/libmesosphere.mk
-
-libstratosphere:
-	@$(MAKE) --no-print-directory -C $(ATMOSPHERE_LIBRARIES_DIR)/libstratosphere -f $(ATMOSPHERE_LIBRARIES_DIR)/libstratosphere/libstratosphere.mk
-
-clean:
-	$(MAKE) -C $(CURRENT_DIRECTORY)/fusee -f $(CURRENT_DIRECTORY)/fusee/fusee.mk clean ATMOSPHERE_CPU="$(strip $(ATMOSPHERE_BOOT_CPU))"
-	$(MAKE) -C $(CURRENT_DIRECTORY)/emummc clean
-	$(MAKE) -C $(CURRENT_DIRECTORY)/exosphere -f $(CURRENT_DIRECTORY)/exosphere/exosphere.mk clean
-	$(MAKE) -C $(CURRENT_DIRECTORY)/mesosphere -f $(CURRENT_DIRECTORY)/mesosphere/mesosphere.mk clean
-	$(MAKE) -C $(CURRENT_DIRECTORY)/stratosphere -f $(CURRENT_DIRECTORY)/stratosphere/stratosphere.mk clean
-	$(MAKE) -C $(CURRENT_DIRECTORY)/troposphere clean
-	$(MAKE) -C $(ATMOSPHERE_LIBRARIES_DIR)/libstratosphere -f $(ATMOSPHERE_LIBRARIES_DIR)/libstratosphere/libstratosphere.mk clean
-	$(MAKE) -C $(ATMOSPHERE_LIBRARIES_DIR)/libmesosphere -f $(ATMOSPHERE_LIBRARIES_DIR)/libmesosphere/libmesosphere.mk clean
-	$(MAKE) -C $(ATMOSPHERE_LIBRARIES_DIR)/libexosphere -f $(ATMOSPHERE_LIBRARIES_DIR)/libexosphere/libexosphere.mk clean
-	$(MAKE) -C $(ATMOSPHERE_LIBRARIES_DIR)/libexosphere -f $(ATMOSPHERE_LIBRARIES_DIR)/libexosphere/libexosphere.mk clean ATMOSPHERE_CPU="$(strip $(ATMOSPHERE_BOOT_CPU))"
-	rm -rf $(CURRENT_DIRECTORY)/$(ATMOSPHERE_OUT_DIR)
-
-$(CURRENT_DIRECTORY)/$(ATMOSPHERE_OUT_DIR) $(CURRENT_DIRECTORY)/$(ATMOSPHERE_BUILD_DIR):
-	@[ -d $@ ] || mkdir -p $@
-
-.PHONY: dist dist-no-debug clean package3 emummc fusee stratosphere mesosphere exosphere troposphere

config_templates/BCT.ini

@@ -0,0 +1,22 @@
+BCT0
+[stage1]
+stage2_path = atmosphere/fusee-secondary.bin
+stage2_mtc_path = atmosphere/fusee-mtc.bin
+stage2_addr = 0xF0000000
+stage2_entrypoint = 0xF0000000
+
+[exosphere]
+; Note: Disabling debugmode will cause parts of ams.tma to not work, in the future.
+debugmode = 1
+debugmode_user = 0
+; Note: Disabling usermode exception handlers will cause atmosphere to not fail gracefully under error conditions.
+; Support will not be provided to users who disable these. If you do not know what you are doing, leave them on.
+disable_user_exception_handlers = 0
+; Note: It's currently unknown what effects enabling the usermode PMU register access may have on official code.
+enable_user_pmu_access = 0
+
+[stratosphere]
+; To force-enable nogc, add nogc = 1
+; To force-disable nogc, add nogc = 0
+
+; To opt in to using Atmosphere's NCM reimplementation, add enable_ncm = 1

config_templates/exosphere.ini

@@ -1,59 +0,0 @@
-# Key: debugmode, default: 1.
-#  Desc: Controls whether kernel is debug mode.
-#   Disabling this will break Atmosphere.
-
-# Key: debugmode_user, default: 0.
-#  Desc: Controls whether userland is debug mode.
-
-# Key: disable_user_exception_handlers, default: 0.
-#  Desc: Controls whether user exception handlers are executed on error.
-#  NOTE: This will cause atmosphere to not fail gracefully.
-#   Support may not be provided to users tho disable these.
-#   If you do not know what you are doing, leave them on.
-
-# Key: enable_user_pmu_access, default: 0.
-#  Desc: Controls whether userland has access to the PMU registers.
-#  NOTE: It is unknown what effects this has on official code.
-
-# Key: blank_prodinfo_sysmmc, default: 0.
-#  Desc: Controls whether PRODINFO should be blanked in sysmmc.
-#   This will cause the system to see dummied out keys and
-#   serial number information.
-#  NOTE: This is not known to be safe, as data may be
-#   cached elsewhere in the system. Usage is not encouraged.
-
-# Key: blank_prodinfo_emummc, default: 0.
-#  Desc: Controls whether PRODINFO should be blanked in emummc.
-#  NOTE: This is not known to be safe, as data may be
-#   cached elsewhere in the system. Usage is not encouraged.
-
-# Key: allow_writing_to_cal_sysmmc, default: 0.
-#  Desc: Controls whether PRODINFO can be written by homebrew in sysmmc.
-#  NOTE: Usage of this setting is strongly discouraged without
-#    a safe backup elsewhere. Turning this on will also cause Atmosphere
-#    to ensure a safe backup of calibration data is stored in unused
-#    mmc space, encrypted to prevent detection. This backup can be used
-#    to prevent unrecoverable edits in emergencies.
-
-# Key: log_port, default: 0.
-#  Desc: Controls what uart port exosphere will set up for logging.
-#  NOTE: 0 = UART-A, 1 = UART-B, 2 = UART-C, 3 = UART-D
-
-# Key: log_baud_rate, default: 115200
-#  Desc: Controls the baud rate exosphere will set up for logging.
-#  NOTE: 0 is treated as equivalent to 115200.
-
-# Key: log_inverted, default: 0.
-#  Desc: Controls whether the logging uart port is inverted.
-
-[exosphere]
-debugmode=1
-debugmode_user=0
-disable_user_exception_handlers=0
-enable_user_pmu_access=0
-blank_prodinfo_sysmmc=0
-blank_prodinfo_emummc=0
-allow_writing_to_cal_sysmmc=0
-log_port=0
-log_baud_rate=115200
-log_inverted=0

config_templates/override_config.ini

@@ -1,10 +1,9 @@
 [hbl_config]
 ; Program Specific Config
 ; Up to 8 program-specific configurations can be set.
-; These use `program_id_#`, `override_address_space_#`, and `override_key_#`
+; These use `program_id_#` and `override_key_#`
 ; where # is in range [0,7].
 ; program_id_0=010000000000100D
-; override_address_space=39_bit
 ; override_key_0=!R
 
 ; Any Application Config
@@ -13,7 +12,6 @@
 ; by a program specific config.
 ; override_any_app=true
 ; override_any_app_key=R
-; override_any_app_address_space=39_bit
 ; path=atmosphere/hbl.nsp
 
 [default_config]

config_templates/stratosphere.ini

@@ -1,4 +0,0 @@
-[stratosphere]
-; To force-enable nogc, add nogc = 1
-; To force-disable nogc, add nogc = 0
-

config_templates/system_settings.ini

@@ -1,25 +1,11 @@
-[eupld]
 ; Disable uploading error reports to Nintendo
+[eupld]
 ; upload_enabled = u8!0x0
-[usb]
-; Enable USB 3.0 superspeed for homebrew
-; 0 = USB 3.0 support is system default (usually disabled), 1 = USB 3.0 support is enabled.
-; usb30_force_enabled = u8!0x0
-[ro]
 ; Control whether RO should ease its validation of NROs.
 ; (note: this is normally not necessary, and ips patches can be used.)
-; ease_nro_restriction = u8!0x1
-[lm]
-; Control whether lm should log to the SD card.
-; Note that this setting does nothing when log manager is not enabled.
-; enable_sd_card_logging = u8!0x1
-; Control the output directory for SD card logs.
-; Note that this setting does nothing when log manager is not enabled/sd card logging is not enabled.
-; sd_card_log_output_directory = str!atmosphere/binlogs
+[ro]
+; ease_nro_restriction = u8!0x0
 ; Atmosphere custom settings
-[erpt]
-; Control whether erpt reports should always be preserved, instead of automatically cleaning periodically.
-; disable_automatic_report_cleanup = u8!0x0
 [atmosphere]
 ; Reboot from fatal automatically after some number of milliseconds.
 ; If field is not present or 0, fatal will wait indefinitely for user input.
@@ -46,31 +32,12 @@
 ; NOTE: EXPERIMENTAL
 ; If you do not know what you are doing, do not touch this yet.
 ; fsmitm_redirect_saves_to_sd = u8!0x0
-; Controls whether am sees system settings "DebugModeFlag" as
-; enabled or disabled.
-; 0 = Disabled (not debug mode), 1 = Enabled (debug mode)
-; enable_am_debug_mode = u8!0x0
-; Controls whether dns.mitm is enabled
-; 0 = Disabled, 1 = Enabled
-; enable_dns_mitm = u8!0x1
-; Controls whether dns.mitm uses the default redirections in addition to
-; whatever is specified in the user's hosts file.
-; 0 = Disabled (use hosts file contents), 1 = Enabled (use defaults and hosts file contents)
-; add_defaults_to_dns_hosts = u8!0x1
-; Controls whether dns.mitm logs to the sd card for debugging
-; 0 = Disabled, 1 = Enabled
-; enable_dns_mitm_debug_log = u8!0x0
-; Controls whether htc is enabled
-; 0 = Disabled, 1 = Enabled
-; enable_htc = u8!0x0
-; Controls whether atmosphere's log manager is enabled
-; Note that this setting is ignored (and treated as 1) when htc is enabled.
-; 0 = Disabled, 1 = Enabled
-; enable_log_manager = u8!0x0
-; Controls whether the bluetooth pairing database is redirected to the SD card (shared across sysmmc/all emummcs)
-; NOTE: On <13.0.0, the database size was 10 instead of 20; booting pre-13.0.0 will truncate the database.
-; 0 = Disabled, 1 = Enabled
-; enable_external_bluetooth_db = u8!0x0
+; Controls whether to enable the deprecated hid mitm
+; to fix compatibility with old homebrew.
+; 0 = Do not enable, 1 = Enable.
+; Please note this setting may be removed in a
+; future release of Atmosphere.
+; enable_deprecated_hid_mitm = u8!0x0
 [hbloader]
 ; Controls the size of the homebrew heap when running as applet.
 ; If set to zero, all available applet memory is used as heap.

docs/building.md

@@ -1,26 +1,8 @@
 # Building Atmosphère
-Building Atmosphère is a very straightforward process that relies almost exclusively on tools provided by the [devkitPro](https://devkitpro.org) organization.
+The process for building Atmosphère is similar to building Fusée Gelée payloads and other Switch apps.
 
-## Dependencies
-+ [devkitA64](https://devkitpro.org)
-+ [devkitARM](https://devkitpro.org)
-+ [Python 2](https://www.python.org) (Python 3 may work as well, but this is not guaranteed)
-+ [LZ4](https://pypi.org/project/lz4)
-+ [PyCryptodome](https://pypi.org/project/pycryptodome) (optional)
-+ [hactool](https://github.com/SciresM/hactool)
+In order to build Atmosphère you must have devkitARM and devkitA64 installed on your computer. You can find instructions on how to install and setup devkitARM and devkitA64 on various OSes [here](https://devkitpro.org/wiki/Getting_Started). You'll need to install the following packages via (dkp-)pacman: switch-dev switch-freetype devkitARM devkitarm-rules
 
-## Instructions
-1. Follow the guide located [here](https://devkitpro.org/wiki/Getting_Started) to install and configure all the tools necessary for the build process.
+sept requires you have python installed with the pycryptodome PyPi packages (`pip install pycryptodome`). You may also want to install the zip package from your package manager of choice to support the `make dist` recipe.
 
-2. Install the following packages via (dkp-)pacman:
-    + `switch-dev`
-    + `switch-glm`
-    + `switch-libjpeg-turbo`
-    + `devkitARM`
-    + `devkitarm-rules`
-    + `hactool`
-
-3. Install the following library via python's package manager `pip`, required by [exosphere](components/exosphere.md):
-    + `lz4`
-
-4. Finally, clone the Atmosphère repository and run `make` under its root directory.
+Once you have finished installing the devkitPro-provided toolchain/libraries, python, and the dependencies, simply clone the Atmosphère repo (clone with the -r flag), change your directory to it and run `make`.

docs/changelog.md

@@ -1,791 +1,4 @@
 # Changelog
-## 1.9.1
-+ Basic support was added for 20.1.0.
-+ General system stability improvements to enhance the user's experience.
-## 1.9.0
-+ Basic support was added for 20.0.0.
-  + The console should boot and atmosphère should be fully functional. However, not all modules have been fully updated to reflect the latest changes.
-    + There shouldn't be anything user visible resulting from this, but it will be addressed in a future atmosphère update.
-    + The same action item from 18.0.0 remains, and I believe in my heart of hearts that it will be addressed eventually. Someone has told me they're working on it.
-    + There aren't (to my knowledge) outstanding 19.0.0 items any more.
-  + **Please note**: As a result of changes made to nintendo's software in 20.0.0, there is roughly 10MB less memory available for custom system modules.
-    + We can only steal a maximum of 14MB from the applet pool, down from 40MB.
-    + To compensate for this, `ams.mitm`'s heap usage has been reduced by 20MB.
-      + To facilitate this, a new helper module (`memlet`) was added, so that memory may be temporarily stolen during the romfs building process.
-      + Hopefully, this results in relatively little breakage, however it is possible that user mods which replace extremely large numbers of files in The Legend of Zelda: Tears of the Kingdom may no longer function.
-        + If you are affected by this, you will see "Data abort (0x101)" when trying to launch the game with mods.
-        + Please reach out to `sciresm` on discord if this occurs to share your error report binary. However, some issues may be impossible to fix.
-        + I apologize sincerely if the issue is impossible to resolve, but I have been forced unavoidably to make compromises here, and I think this is the best balance to be struck.
-  + `exosphère` was updated to reflect the latest official secure monitor behavior.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `loader` was updated to reflect the latest official behavior.
-  + `pm` was updated to reflect the latest official behavior.
-  + `ncm` was partially updated to reflect the latest official behavior.
-  + `erpt` was updated to reflect the latest official behavior.
-+ Atmosphère was updated to use GCC 15/newlib (latest devkitA64/devkitARM releases).
-+ A number of improvements were made to the dmnt cheat engine.
-  + New instructions were added, and instructions were updated for improved/new functionality.
-  + Please see the documents for details -- thanks @tomvita!
-+ General system stability improvements to enhance the user's experience.
-## 1.8.0
-+ Basic support was added for 19.0.0.
-  + The console should boot and atmosphère should be fully functional. However, not all modules have been fully updated to reflect the latest changes.
-    + There shouldn't be anything user visible resulting from this, but it will be addressed in a future atmosphère update. There is still one action item from 18.0.0 to be addressed, as well.
-  + `exosphère` was updated to reflect the latest official secure monitor behavior.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `loader` was updated to reflect the latest official behavior.
-  + `pm` was updated to reflect the latest official behavior.
-  + `ro` was updated to reflect the latest official behavior.
-+ `creport`'s file acces patterns were optimized, greatly improving performance when generating a crash report.
-+ Atmosphère now uses `relr` relocations where possible.
-  + This reduces the filesize of a number of atmosphère's modules.
-+ A number of minor issues were fixed and improvements were made, including:
-  + Support was fixed for running Atmosphère on newer units with specific Hynix/Micron DRAM chips.
-+ General system stability improvements to enhance the user's experience.
-## 1.7.1
-+ Support was added for 18.1.0.
-+ Atmosphère was updated to use GCC 14/newlib (latest devkitA64/devkitARM releases).
-+ Further changes were for 18.0.0:
-  + `loader` was updated to reflect the latest official behavior.
-+ General system stability improvements to enhance the user's experience.
-## 1.7.0
-+ Basic support was added for 18.0.0.
-  + The console should boot and atmosphère should be fully functional. However, not all modules have been fully updated to reflect the latest changes.
-    + There shouldn't be anything user visible resulting from this, but it will be addressed in a future atmosphère update, once I am not traveling so much.
-  + `exosphère` was updated to reflect the latest official secure monitor behavior.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `spl` was updated to reflect the latest official behavior.
-+ `fusee`'s no longer supports applying IPS patches to KIPs.
-  + The only KIPs that are ever present are a) atmosphère modules, b) custom system modules, or c) FS.
-  + The IPS subsystem was originally designed to make nogc patches work for FS, but these are now internal, and it appears the literal only kip patches that exist are for piracy.
-    + I could not find any kip patches posted anywhere made for any other purpose.
-  + It fundamentally does not make sense to slow down boot for every normal user for a feature that has no actual use-case, especially when `fusee` seeks to be a minimal bootloader.
-+ Minor improvements were made to atmosphere's gdbstub, including:
-  + Support was added for QStartNoAckMode.
-  + An issue was fixed that could cause a fatal error when creating too many breakpoints.
-+ A number of minor issues were fixed and improvements were made, including:
-  + `pt-BR` (`PortugueseBr`) is now accepted as a valid language when overriding game locales.
-  + A bug was fixed that could cause atmosphere to incorrectly serialize output object IDs over IPC when using domain objects.
-  + A bug was fixed in `pm`'s resource limit boost logic that could potentially cause legitimate boosts to fail in certain circumstances.
-  + `loader`/`ro` will now throw a fatal error when using invalid IPS patches that go out of bounds, instead of corrupting memory.
-  + Support was fixed for booting using a memory configuration of half of the true available memory (e.g. forcing a 4GB configuration on an 8GB board).
-+ General system stability improvements to enhance the user's experience.
-## 1.6.2
-+ Support was finished for 17.0.0.
-  + `erpt` was updated to support the latest official behavior.
-  + `jpegdec` was updated to support the latest official behavior.
-  + `pm` was updated to support the latest official behavior.
-+ General system stability improvements to enhance the user's experience.
-## 1.6.1
-+ An improved solution to [the problem that would cause consoles which had previously re-built their SYSTEM partition to brick on update-to-17.0.0](https://gist.github.com/SciresM/2ddb708c812ed585c4d99f54e25205ff) was added.
-  + In particular, booting atmosphère will now automatically detect the problem and unbrick any consoles which have fallen into this state.
-+ Some improvements were made to `haze`, including:
-  + Performance was greatly improved:
-    + Support was added for GetObjectPropList, which decreases the amount of requests made by ~8x.
-    + Haze now performs rendering on the GPU, freeing up the CPU to respond to requests in a more timely manner.
-  + An issue was fixed with how `haze` configures `bMaxPacketSize0` which improves support for USB3.
-+ General system stability improvements to enhance the user's experience.
-## 1.6.0
-+ Basic support was added for 17.0.0.
-  + The console should boot and atmosphère should be fully functional. However, not all modules have been fully updated to reflect the latest changes.
-    + There shouldn't be anything user visible resulting from this, but it will be addressed in a soon-to-come atmosphère update.
-  + `exosphère` was updated to reflect the latest official secure monitor behavior.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `ncm` was updated to reflect the latest official behavior.
-  + `erpt` was partially updated to support the latest official behavior.
-+ Atmosphere's gdbstub now supports waiting to attach to a specific program id on launch (as opposed to any application).
-  + The monitor command for this is `monitor wait <hex program id>`, where program id can optionally have an `0x` prefix.
-+ Support was added to `haze` for editing files in-place and performing 64-bit transfers (files larger than 4 GB).
-+ `bpc.mitm` was enabled on Mariko units, and now triggers pmic-based shutdowns/reboots (thanks @CTCaer).
-  + This should cause the console to no longer wake ~15 seconds after shutdown on Mariko.
-+ A number of minor issues were fixed and improvements were made, including:
-  + A workaround was added for a change in 17.0.0 that would cause consoles which had previously re-built their SYSTEM partition to brick on update-to-17.0.0.
-+ General system stability improvements to enhance the user's experience.
-## 1.5.5
-+ Support was added for 16.1.0.
-+ General system stability improvements to enhance the user's experience.
-## 1.5.4
-+ Experimental new functionality was implemented to prevent crashing when building romfs for certain games with obscene file counts.
-  + This includes both Fire Emblem: Engage (~190000 files), and The Legend of Zelda: Tears of the Kingdom (~300000) files.
-  + The solution involved adding functionality to ams.mitm/pm to dynamically steal memory from the application (and system) pool as needed when the games have romfs mods.
-    + No memory is taken, and there is no cost to this functionality when playing without mods (or with overrides disabled).
-  + The Legend of Zelda: Tears of the Kingdom is currently the absolute worst case game, requiring ~48 MB of memory to build a romfs image to play with mods.
-    + Right now, the memory is sourced as follows: 32 MB (base ams.mitm heap), 10 MB (stolen from application pool), 8 MB (dynamically stolen from system pool).
-    + This is 50 MB, which allows a little overhead in the worst case (prevents crashing due to exhausting the heap for other allocations in ams.mitm).
-    + Zelda is remarkably sensitive to memory being stolen from the application pool, tolerating no more than 16 MB on 1.0.0 and 12 MB on 1.1.0. I have chosen to steal 10 MB, to be safe, for now.
-      + This may break on a future game update, but I will fix it if and when that happens. There is no perfect solution; the game simply requires too much memory to support mods flawlessly, and I am forced to compromise.
-  + As usual, if you encounter a game that exhausts ams.mitm's memory (crashing it) when loading layeredfs mods, please contact `SciresM#0524`.
-    "I am jinxing myself by saying this, but it's really hard to imagine any game being worse than The Legend of Zelda: Tears of the Kingdom, but if it happens again I will drop everything to fix it as usual".
-+ General system stability improvements to enhance the user's experience.
-## 1.5.3
-+ Support was added for 16.0.3.
-+ Atmosphère was updated to use GCC 13/newlib (latest devkitA64/devkitARM releases).
-  + **Please note**: This introduces a known issue, which is currently being worked on.
-    + As you may recall from the 1.4.1 changelog, Fire Emblem: Engage requires enormous amounts of memory to support using layeredfs mods with the game.
-    + Latest GCC/newlib slightly increases malloc overhead size, which makes the previous memory increase insufficient.
-    + A general-case solution to this is in the works, which should hopefully fix the problem in a way that doesn't jinx me for the future.
-+ A number of minor issues were fixed and improvements were made, including:
-  + An issue was fixed that caused system font replacement to not work on 16.0.0+.
-  + An minor accuracy issue was addressed in mesosphere's management of certain memory ranges; this issue would have had zero visible impact to the end-user.
-+ General system stability improvements to enhance the user's experience.
-## 1.5.2
-+ A homebrew application (`haze`) was added for performing USB file transfer (with thanks to @liamwhite for both design and implementation).
-  + `haze` is included with atmosphère, and provides access to the SD card via the PTP/MTP protocol.
-    + **Please note**: haze will show inside the homebrew menu under the name "USB File Transfer".
-  + **Please note**: Atmosphère cannot be updated at runtime, and trying to install an atmosphère update via haze will fail as usual.
-+ General system stability improvements to enhance the user's experience.
-## 1.5.1
-+ `fatal` was updated to reduce memory footprint.
-  + Starting in 16.0.0, official `fatal` has no framebuffer or rendering logic, and instead calls other system service commands to draw the screen.
-  + However, these commands aren't usable by atmosphère (too small rendering window, bad color support).
-  + To reduce the relative memory footprint differential between atmosphère and official code, the framebuffer (2 MB) is now dynamically allocated when needed.
-    + This will try to allocate from multiple pools (preferring System > System_NonSecure > Application).
-    + This technically requires that 2 MB be available in at least one of these pools for the fatal screen to render (otherwise, a reboot-to-black-and-white-fatal will occur), but this should be a non-issue in almost all cases.
-+ A feature was added to optionally mirror the bluetooth pairing database to the SD card (thanks @ndeadly).
-  + This allows device pairings to be automatically kept in-sync across sysmmc/all emummcs.
-  + This is opt-in, and can be controlled by setting `atmosphere!enable_external_bluetooth_db = u8!0x1`.
-  + When enabled, the pairing database will be synchronized to `/atmosphere/bluetooth_devices.db`.
-+ General system stability improvements to enhance the user's experience.
-## 1.5.0
-+ Support was added for 16.0.0
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `ncm` was updated to reflect the latest official behavior.
-  + Many FS apis were updated under the hood to reflect the latest official behavior.
-  + **Please Note**: 16.0.0 made breaking changes to a number of system APIs, including in FS/NCM/Shared Font commands that some homebrew programs may use.
-    + These programs may encounter strange errors, and may need to be recompiled with a libnx updated to support 16.0.0's changes to function properly.
-+ A number of minor issues were fixed and improvements were made, including:
-  + An issue was fixed that could cause GPIO outputs to be misconfigured under certain circumstances.
-+ General system stability improvements to enhance the user's experience.
-## 1.4.1
-+ A number of minor issues were fixed and improvements were made, including:
-  + `dmnt` cheat toggle files are no longer ignored when they are missing a trailing newline.
-  + The mechanism for automatically cleaning up `erpt_reports` added in 1.3.0 was fixed.
-    + This was actually just very fundamentally broken and has never worked, but it is verified working now.
-  + Minor fixes were made in `mesosphère` to match official kernel behavior (spin lock assembly was corrected, wrong result on failure in in GetProcessId was corrected).
-  + A missing call to GetSdStatus when initializing SD cards at non uhs-i mode was added in the sdmmc driver.
-+ `ams.mitm`'s memory usage was increased by 16 MB, to prevent crashing when building romfs for games with obscene file counts.
-  + To quote the changelog for 1.2.3: "Animal Crossing's 2.0.0 update contains >99000 files [...] It's really hard to imagine any game being worse than Animal Crossing".
-  + As it turns out, Fire Emblem: Engage has ~186000 files, and is approximately twice as bad as animal crossing.
-  + The additional memory here is taken from the applet pool; no issues are expected to arise from this, but please report anything you may run into.
-  + As usual, if you encounter a game that exhausts ams.mitm's memory (crashing it) when loading layeredfs mods, please contact `SciresM#0524`.
-    + I am jinxing myself by saying this, but it's really hard to imagine any game being worse than Fire Emblem: Engage, but if it happens again I will drop everything to fix it as usual.
-+ General system stability improvements to enhance the user's experience.
-## 1.4.0
-+ Support was added for 15.0.0.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `ncm` was updated to reflect the latest official behavior.
-+ A number of minor issues were fixed and improvements were made, including:
-  + The capacity limit on registered add-on contents was fixed in NCM to reflect the increase that occurred in 12.0.0.
-  + An off-by-one was fixed in mesosphere when computing the new value for an address arbiter signaled with ModifyByWaitingCountIfEqual.
-  + dmnt.gen2's gdbstub now sanitizes thread names to prevent invalid characters from breaking gdb.
-  + dmnt.gen2's gdbstub now reports the architecture tag correctly when attached to 32-bit processes.
-  + Support for program-specific html manual content overrides was added for non-hbl takeover context.
-  + A bug was fixed in how emummc constructed the alternate Nintendo directory path.
-    + Previously, this was using `/*/Nintendo/Nintendo` instead of `/*/Nintendo`.
-    + Code was added to automatically move the old folders to the new ones when booting into emummc.
-  + A bug was fixed in boot that caused an incorrectly low input voltage limit to be set.
-+ General system stability improvements to enhance the user's experience.
-## 1.3.2
-+ Support was improved for 14.0.0+.
-  + `loader` was updated to reflect the latest official behaviors.
-  + `ro` was  updated to reflect the latest official behaviors.
-+ A number of minor issues were fixed and improvements were made, including:
-  + A memory leak was fixed in filesystem path management; this could cause a crash when launching games ~100 times, or when deleting/re-downloading games.
-  + A bug was fixed that could cause threads to not see a newly signaled semaphore.
-  + A number of minor inaccuracies were fixed in the updated FileSystem APIs.
-+ General system stability improvements to enhance the user's experience.
-## 1.3.1
-+ Support was added for 14.1.0.
-+ A number of minor under the hood improvements to accuracy were made to better reflect latest official system module behavior, particularly around FS apis.
-+ General system stability improvements to enhance the user's experience.
-## 1.3.0
-+ Support was added for 14.0.0.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `erpt` was  updated to reflect the latest official behaviors.
-  + `pm` was  updated to reflect the latest official behaviors.
-  + `fatal` was  updated to reflect the latest official behaviors.
-+ A mechanism for automatically cleaning up `erpt_reports` was added.
-  + When booting, if the console has more than 1000 reports inside `/atmosphere/erpt_reports`, the folder will be cleaned to empty.
-  + This behavior can be disabled by setting `erpt!disable_automatic_report_cleanup` = u8!0x1 in system_settings.ini.
-+ Atmosphère's build system was re-written, and now allows globally building for various builds/configs.
-  + All boards now automatically support release/debugging/auditing targets; it is now possible to build a full debugging/auditing build of atmosphère for the first time.
-+ Support was added for compiling libstratosphère to run on PC.
-  + The currently implemented/tested targets are Windows (x64), Linux (x64, arm64), macOS (x64, arm64).
-    + If you are a developer interested in adding support for another target, please reach out to `SciresM#0524` on discord.
-  + This is intended to finally allow sanely testing Atmosphère's code, by allowing most of it to run on a PC (with access to a debugger) instead of on game console hardware.
-  + In addition, this will allow making PC tools which reuse code written for Atmosphère directly..
-  + **Please Note**: This has no relation to interacting with official software on PC whatsoever. This really allows for making tests and self-contained atmosphère-based command-line tools; the Atmosphère project continues to have zero interest in attempting to run official software of any kind.
-  + In the course of adding this support (and working on tooling using it), a number of fairly major revisions were made to stratosphere (particularly surrounding filesystem code).
-    + **Please Note**: A number of changes made for this (and ones necessary in the process of adding support for 14.0.0) are api-breaking.
-      + If you're a developer and any of this caused your code to break, please feel free to contact `SciresM#0524` for help updating your program.
-+ General system stability improvements to enhance the user's experience.
-## 1.2.6
-+ Support was added for 13.2.1.
-+ A number of minor issues were fixed and improvements were made, including:
-  + A minor performance improvement was implemented in service table dispatch by sorting and binary-searching the service command table instead of using linear search.
-  + Static initialization logic in Atmosphere was made much more regular.
-+ General system stability improvements to enhance the user's experience.
-## 1.2.5
-+ Support was added for 13.2.0.
-+ A number of minor issues were fixed and improvements were made, including:
-  + A bug was fixed that caused `mesosphère` to underreport the total memory size by 8MB for certain games which use newer system-resource-size memory management.
-    + This caused FIFA 19 to crash, and possibly other issues.
-  + Memory management changes were made to `sm` that save 0x5000 of memory.
-  + A microoptimization was made to the way `mesosphère` manages updating the debug register for hardware single-step support.
-  + Support was fixed for enabling `usb!usb30_force_enabled` on 13.0.0+.
-  + The work-in-progress unit testing framework was updated to use doctest instead of catch2.
-+ General system stability improvements to enhance the user's experience.
-## 1.2.4
-+ Changes were made to the way fs.mitm builds images when providing a layeredfs romfs.
-  + Cache management (to avoid unnecessary rebuild) was revised, to add a grace period of ~500ms-1s between process closing romfs image and ams.mitm needing to rebuild if romfs is re-opened.
-    + This makes our cache much more effective, previously we were re-building romfs several times.
-  + RomFS image ownership was overhauled, with a new reference-counting implementation added (used to implement the above grace period).
-    + Certain games (e.g. Puyo Puyo Tetris 2, probably others) were sensitive to this timing, and could use access patterns which would trigger creation of romfs image while previous romfs image was in the middle of destructor.
-    + This could cause a fatal error, because the destructor for the old image could run simultaneously with building the new image.
-  + This also provides a speedup versus the 1.2.3 code, with Animal Crossing now taking ~8 fewer seconds to get past the Nintendo Switch logo.
-+ General system stability improvements to enhance the user's experience.
-## 1.2.3
-+ Because ams.TMA is taking longer to develop than expected, experimental support for Atmosphère's gdbstub as a standalone is now available.
-  + To enable it, set `atmosphere!enable_standalone_gdbstub` = u8!0x1 in system_settings.ini.
-    + The standalone also requires `atmosphere!enable_htc` = u8!0x0, but this should be the case for everyone since ams.TMA isn't actually usable yet.
-  + Once enabled, open the devkitPro provided-gdb (`aarch64-none-elf-gdb` for 64-bit or `arm-none-eabi-gdb` for 32-bit).
-    + The standalone stub exposes itself on port 22225 -- so the command to connect is `target extended-remote <ip address>:22225`.
-    + Type `info os processes` to get a list of process IDs that can be attached to.
-      + The stub should work on both system programs, games, and homebrew -- but please note that debugging certain processes (like sockets) can cause hang due to the stub using them itself.
-  + Software break-points, hardware break-points, hardware watch-points, and hardware single-step are all supported/implemented.
-  + The following monitor commands are currently supported:
-    + `monitor get info`: Get process info, address space layout, and information on modules.
-    + `monitor get mappings`: Get all memory mappings.
-    + `monitor get mapping <addr>`: Get the memory mapping for a specific address.
-    + `monitor wait application`: Causes the stub to wait for an application to be launched. The next application will be started suspended.
-      + User is expected to send `attach <pid>` after launching, which will cause attach-on-first-instruction. Failure to attach may cause system instability, this probably needs work.
-  + **Please Note**: The GDBstub is new and may have bugs/need work. If you find issues, please report them to SciresM#0524 -- all help finding/fixing bugs is appreciated, here.
-  + Generally speaking, if you would like to report information about fixes needed/discuss development of the gdbstub, join ReSwitched's #dev-support channel.
-+ Changes were made to the way fs.mitm builds images when providing a layeredfs romfs.
-  + Animal Crossing's 2.0.0 update contains >99000 files, and has tables so big that we ran out of memory even after the optimizations made in 0.10.5.
-    + Previously, we used fixed-sized 0x40000 work buffers for file/directory tables and simultaneously built hash/content tables in one loop over files/directories.
-    + We now iterate over the file/directory tables multiple times, first once to determine the hash table indices, then repeatedly to build hash tables, then once to build content tables.
-    + We also now allow smaller-than-0x40000 work buffers, trying half-as-big buffers until allocation succeeds (or work buffer would be <0x4000, which is a safeguard against truly horrible performance).
-  + There is a slight speed penalty to these changes, but it's on the order of seconds for the worst case (Animal Crossing) and trivial for most games with reasonable tables.
-  + If you encounter a game that exhausts ams.mitm's memory (crashing it) when loading layeredfs mods, please contact `SciresM#0524`.
-    + It's really hard to imagine any game being worse than Animal Crossing, but if it happens again I will drop everything to fix it as usual.
-+ `creport` now attempts to parse symbol tables if present.
-  + If a game executable has a symbol for a given address, the function-relative-offset will now be printed after the module-relative-offset.
-+ General system stability improvements to enhance the user's experience.
-## 1.2.2
-+ A number of fixes were made to Atmosphère's implementation of the new "sprofile" service added in 13.0.0.
-  + Nintendo is finally transmitting data over the internet to certain consoles, which has allowed for validating our service implementation.
-    + Unfortunately, there were several problems, and if your console began trying to use the new services atmosphere would show a fatal error with code 0xCAF6 (sprofile::ResultInvalidState()).
-  + With actual test data in hand, a test program was written and it was verified that our implementation can successfully import/access profile data now.
-    + Hopefully there are no more issues, and I sincerely apologize for anyone who got an 0xCAF6 fatal due to this.
-+ A number of minor improvements were made to `mesosphère`, including:
-  + KThread::GetContextForSchedulerLoop was implemented in assembly (using static assertions to verify offset-of-context-in-struct is correct).
-    + This saves an unnecessary function call in the middle of the scheduler hot loop, replacing it with an addition instruction, which should improve microperformance.
-  + Mesosphere's hardware maintenance instructions were audited via a script and now directly match Nintendo's kernels.
-    + Notably, this inserts a missing instruction synchronization barrier when validating that slab heaps may be constructed.
-    + This missing ISB could cause an abort on certain (see: particularly sensitive) hardware on boot if the relevant codepath was speculatively executed (it normally only executes on game launch...)
-  + The SVC handlers for performing light IPC (normally unused) from 32-bit process were fixed in Mesosphere.
-  + A bug was fixed that would cause the register x27 to be overwritten with the contents of x26 when returning from a user exception handler.
-  + A bug was fixed that would cause the kernel to use the userland stack pointer instead of the kernel stack pointer while generating an error report for a kernel abort.
-+ General system stability improvements to enhance the user's experience.
-## 1.2.1
-+ Support was implemented for 13.1.0.
-  + `mesosphère` was updated to reflect the kernel behavioral changes made in 13.1.0.
-    + KScheduler now issues a data memory barrier when unlocking the scheduler lock and when early-returning due to top-thread-is-current during scheduling.
-  + `erpt` was  updated to reflect the latest official behaviors.
-    + The new service added in 13.0.0 ("sprofile") was revised, and the data formats it expects was changed.
-      + This still appears to be (possibly(?)) untestable due to data not being transmitted yet, but I have greater confidence things will go smoothly than I did when 1.1.0 released.
-+ A number of improvements were made to `mesosphère`, including:
-  + A build target was created to build targeting the qemu `virt` board.
-    + This facilitates writing unit tests for the kernel (and other atmosphere components) and running them under PC.
-      + **Please Note**: Official system software will not work at all under this, and the Atmosphère project has zero interest in attempting to run official software of any kind. This is unit testing machinery, and explicitly not more than that.
-    + This should hopefully allow us to have greater confidence that all of atmosphere's components work the way they're theoretically supposed to in the future.
-    + **Please Note**: If you are a developer who is familiar with the Horizon operating system (or capable of becoming familiar), I would greatly appreciate help writing tests and improving the testing framework.
-      + Please contact `SciresM#0524` if you are capable and interested.
-        + Really, if you are actually a developer who would like to help me get this off the ground, I would deeply appreciate it.
-        + That said, if you are not a developer but want to be one, this probably isn't the best opportunity; I expect it to be highly technical.
-          + Consider the ReSwitched discord's #hack-n-all channel for your educational purposes.
-      + We are (at least for now) using [catch2](https://github.com/catchorg/Catch2) for unit tests.
-  + Almost all virtual calls in the kernel are now resolved statically.
-    + This eliminates substantial virtual call overhead, and should lead to improved kernel microperformance in pretty much every function.
-  + The remaining red black tree find operations which weren't using the optimized "find key" variant are now using the optimized version.
-  + Custom assembly was written to improve tick-to-timespan conversion.
-    + This works around gcc emitting suboptimal assembly at -Os (it emits good assembly at -O3, clang is fine at both -O3 and -Os).
-  + KThread and KSession structures were updated to optimize member layout, saving 0x10 bytes per KThread/KSession object.
-  + Rather than unnecessarily zero-ing all data in kernel objects only to overwrite members later, we now only initialize the members we need to in kernel object constructors.
-    + This is what Nintendo was doing already.
-  + A set of custom optimized atomic primitives were implemented and are used in place of std::atomic<>
-    + This works around a gcc bug which downgrades specified memory order to seq_cst, and introduces clrex in places where it is appropriate.
-    + This should strictly improve microperformance of many system calls.
-  + An compile-time toggleable extension was added to support 40-bit physical addresses in MapRange capabilities (using currently reserved bits).
-  + A number of minor bugs were fixed, including:
-    + Initial cache management now better reflects official behavior.
-      + This fixes an issue that caused certain hardware with cache sensitivity to produce cryptic kernel panics during boot.
-    + Incorrect logic when checking thread priority capabilities was fixed to reflect official behavior.
-    + The scheduler was updated to reflect latest official behavior, and a number of minor bugs involving clz/ctz were fixed.
-    + Accesses to the processes local region were fixed to properly use kernel linear region, not userland pointers.
-    + The cache SVCs exposed for 32-bit processes now better reflect official core mask request semantics.
-    + A bug was fixed that could cause a kernel panic if SvcArbitrateLock was called on a thread with exactly one reference in the middle of handling a user-mode exception.
-+ General system stability improvements to enhance the user's experience.
-## 1.2.0
-+ `boot` was updated to reflect the latest official behavior for display/battery management.
-  + This should fix any issues that might result from running older releases on the OLED model, if you're somehow in a position to do so.
-+ The "target firmware" system was changed to allow the bootloader to specify an approximation, rather than the true target firmware.
-  + Previously we expected compliant bootloaders to inspect SYSTEM:/ to determine the specific target firmware.
-  + Now, we only require an approximate version, with major version == true major version and approximate version <= true version.
-  + This greatly simplifies bootloader requirements, and correspondingly all code for accessing SYSTEM has been removed from fusee.
-    + This should result in a substantial speedup when booting emummc with fusee, as SYSTEM accesses were the most expensive thing done previously.
-  + This should resolve any inconsistency in firmware detection when booting via fusee vs hekate.
-  + This should also improve our compatibility with micro firmware releases, making it more likely that atmosphere "just works" if nothing important has changed.
-+ Dynamic resource limit determination logic was implemented in `pm` to match latest official behavior.
-  + This greatly simplifies/makes consistent the resource limits on older firmwares, as well.
-+ An enormous amount of refactoring was performed under the hood, including:
-  + **Please Note**: If you are a developer who uses Atmosphere-libs, a number of changes here are breaking.
-    + Feel free to contact SciresM#0524 for help updating your program.
-  + The OS namespace had many primitives implemented/made more accurate.
-  + Since mesosphere is now always-on, os::LightEvent (which required newer SVCs) is now globally usable (and used by stratosphere where relevant).
-  + Assertions are now true no-ops when building for release.
-  + Stratosphere is now built with -Wextra/-Werror.
-  + Most "common" logic in system module main.cpp files was moved into libstratosphere.
-    + **Please Note**: main.cpp files for prior atmosphere-libs will no longer work, for a really large number of reasons.
-  + A number of longstanding code style issues were corrected.
-  + Mesosphere now uses util::BitFlagSet for SVC permissions.
-  + Mesosphere now puts its relocation table inside .bss, which allows that memory to be reclaimed after relocations are performed.
-    + These changes save ~16KB of memory in the kernel, all said and done.
-  + A number of locations in stratosphere where memory could be saved were spotted and taken advantage of, leading to ~150-200KB of saved memory.
-  + The `spl` and `loader` system module was refactored to better reflect official logic.
-  + `sf` ipc server code was updated to only emit mitm/defer logic when that logic is actually required somewhere in process.
-  + `tipc` ipc server code was updated to reflect changes to official logic made in 13.0.0.
-  + Many, many other minor changes, please talk to SciresM#0524 or read the relevant commits if you want to know more.
-+ A number of minor issues were fixed, including:
-  + Mesosphere's handling of SVC permissions on thread pin/unpin was updated to reflect official kernel behavior.
-  + util::CountTrailingZeros() was fixed to calculate the correct value when used at compile-time.
-+ General system stability improvements to enhance the user's experience.
-## 1.1.1
-+ A bug was fixed which caused some memory to leak when launching a game with mods enabled, eventually causing a crash after enough game launches without rebooting.
-+ General system stability improvements to enhance the user's experience.
-## 1.1.0
-+ Support was implemented for 13.0.0.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `ncm` was updated to reflect the latest official behaviors.
-  + `erpt` was  updated to reflect the latest official behaviors.
-    + Two new services ("sprofile") were added to `erpt`, and have been fully reimplemented.
-    + **Please Note**: These services provide a way for settings to be pushed to consoles over the internet without system update.
-      + Because there appear to be no settings pushed out yet, this implementation fundamentally cannot be fully tested right now, but hopefully there are no issues once settings begin being distributed.
-+ The `LogManager` system module was reimplemented.
-  + This system module provides services that some games use for logging.
-  + Atmosphere's reimplementation supports logging to the SD card (if `lm!enable_sd_card_logging` is true) and to ams.TMA.
-    + To control the directory where logs are saved, modify the `lm!sd_card_log_output_directory` setting.
-  + Atmosphere's reimplementation is disabled by default (in order to save memory), but can be enabled by setting `lm!enable_log_manager` to true.
-    + This will allow reading over logs from games which use the services (or potentially logging from homebrew in the future), which can be useful to developers.
-    + Please note that when TMA is fully implemented in the future, enabling TMA will forcibly enable `LogManager`.
-+ General system stability improvements to enhance the user's experience.
-## 1.0.0
-+ `fusee` was completely re-written in C++ to use the same atmosphere-libs APIs as the rest of atmosphere's code.
-  + The rewrite was performed with a big emphasis on ensuring a good boot speed, and generally boot should be much faster than it was previously.
-    + Depending on SD card/environment, boot speed may now be slightly faster than, roughly the same as, or slightly slower than when booting with hekate.
-    + The obvious low-hanging fruit for performance improvements has been picked, so hopefully the improved performance is to everybody's liking.
-  + SD card compatibility was improved: fusee should now have SD card compatibility identical to the official OS driver.
-  + **Please Note**: various components were renamed (fusee-primary.bin -> fusee.bin, fusee-secondary.bin -> package3).
-    + If you use another bootloader (like hekate), you may need to update your configuration to use the new layout.
-  + **Please Note**: BCT.ini no longer exists, nogc configuration has been moved to `/atmosphere/stratosphere.ini`.
-    + If you rely on custom nogc configuration, please be sure to update accordingly.
-  + Custom splash screen BMP parsing is no longer supported (as it slows down boot for 99% of users).
-    + To compensate for this, a script to insert a custom splash screen into a `package3` binary has been added to the `utilities` folder of the atmosphere repository.
-    + The release build should be equivalent to running the following command from the root of the atmosphere repository: `python utilities/insert_splash_screen.py img/splash.png fusee/package3`
-+ A number of pending changes were made, following the end of the relevant testing periods:
-  + `mesosphere` is no longer opt-out, and stratosphere code will begin depending on its being present/in use.
-  + `NCM` is no longer opt-out.
-  + The cleanup to ease the transition from < 0.19.0 to 0.19.0 has been removed.
-+ General system stability improvements to enhance the user's experience.
-## 0.20.1
-+ An issue was fixed that caused severely degraded performance after wake-from-sleep on Mariko hardware.
-  + This was due to Mariko MTC resulting in a frequency of 1599.999MHz instead of 1600MHz.
-  + Due to this off-by-one, Nintendo's EMC management code failed to initialize/take over, and after wake from sleep RAM would be in a strange state.
-+ General system stability improvements to enhance the user's experience.
-## 0.20.0
-+ DRAM training (MTC) was implemented for Mariko hardware, increasing RAM speed from 204MHz to 1600MHz.
-  + This significantly optimizes Mariko boot speed, cutting boot time roughly in half.
-  + Typical boot time reductions (measured as "select fusee" to "home menu visible"):
-    + Normal (Iowa): ~35 seconds -> ~18 seconds.
-    + Lite (Hoag): ~65 seconds -> ~30 seconds.
-  + NOTE: Work is being started on a re-written `fusee` component, with an eye specifically towards ensuring a good boot speed.
-    + With any luck, boot will be much much faster on all units (Mariko and Erista) in an upcoming release.
-+ Sept was replaced, and deleted from the repository.
-  + Erista units now use a custom TSEC firmware to manage key derivation.
-    + For more details, contact SciresM#0524 on discord.
-  + This has a number of benefits, including:
-    + This greatly simplifies key derivation logic by making it consistent on all firmwares.
-      + Fusee no longer accesses/uses keyblobs at all, so units which have accidentally destroyed/lost keyblobs can boot without them.
-    + This greatly increases stability (sept was the biggest source of boot failures).
-    + This improves boot speed (sept rebooted multiple times, performed hardware init multiple times, and was generally very slow).
-    + Atmosphère build process is now much saner.
-+ A number of improvements were made to the dmnt cheat engine.
-  + Cheats which take in a memory region operand may now use types "2" or "3" to perform accesses relative to the alias/aslr regions, respectively.
-  + Support was added for an "else" opcode in the cheat engine, to make writing certain conditional logic more natural.
-  + Support was added for a cheat orchestrator homebrew (like edizon) to detach from a cheat process/set the master cheat programmatically.
-+ Daybreak now provides a warning when attempting to install a firmware newer than the highest version atmosphère knows it supports.
-  + To facilitate this, exosphere now exposes the supported HOS version via an extension ConfigItem.
-+ A number of minor issues were fixed, including:
-  + Several mesosphere debug SVC implementations were updated to reflect the semantics of the latest kernel.
-  + Support was fixed for deriving BIS encryption keys on certain prototype hardware.
-+ General system stability improvements to enhance the user's experience.
-## 0.19.5
-+ Support was added for 12.1.0.
-+ LayeredFS support was added for OpenDataStorageWithProgramIndex commands.
-  + Certain games using newer (7.0.0+ APIs) which include multiple programs under a single title previously could not be modified.
-  + These are now supported as normal, and LayeredFS should have 100% compatibility again.
-+ A number of minor issues were fixed, including:
-  + The Reboot to Payload NRO was updated to allow the OS to save state prior to rebooting (thanks @AuroraWright)!
-  + An issue was fixed that could cause dns.mitm to fail when games requested resolution of an empty string.
-  + An issue was fixed that caused a memory leak in the erpt system module.
-    + This would eventually cause a system crash after ~540 reports were generated without rebooting.
-+ A number of minor improvements were made to improve mesosphere's accuracy.
-+ General system stability improvements to enhance the user's experience.
-## 0.19.4
-+ Support was added for 12.0.3.
-+ A number of minor issues were fixed, including:
-  + An issue was fixed that could cause heap memory corruption when allocation was highly contended.
-  + An issue was fixed that could cause sleep to fail under certain conditions.
-  + An issue was fixed that could cause a scheduler slow path to be taken more often than necessary.
-+ General system stability improvements to enhance the user's experience.
-## 0.19.3
-+ Support was added for 12.0.2.
-+ A number of minor issues were fixed, including:
-  + An issue was fixed in dns.mitm that caused a crash when games attempted to resolve the IP address of nullptr.
-  + An issue was fixed in erpt that would cause an abort when booting without having ever booted stock previously.
-  + An issue was fixed in (file-based) emummc that caused an error on system format/downloading certain games.
-+ General system stability improvements to enhance the user's experience.
-## 0.19.2
-+ Atmosphère's components were further updated to reflect latest official behaviors as of 12.0.0.
-  + Notably, `erpt` was updated to implement the new forced shutdown detection feature.
-    + When a forced-shutdown occurs, an erpt_report will be generated and saved to the SD card on the next boot.
-+ Atmosphere-libs was updated to use GCC 11 (latest devkitA64/devkitARM releases).
-  + Initial inspections show mild-to-moderate optimizer improvements in several important places (kernel is 0x3000 smaller).
-  + General system stability improvements to enhance the user's experience.
-+ A number of minor issues were fixed, including:
-  + A bug was fixed that caused a black screen when attempting to boot firmware versions 2.0.0-4.1.0.
-  + A bug was fixed that caused sm to abort when at the session limit, rather than returning error codes.
-  + A bug was fixed that allowed for resource exhaustion on 12.0.0, under certain circumstances.
-+ Several issues were fixed, and usability and stability were improved.
-## 0.19.1
-+ An issue was fixed that caused a fatal error when using official `migration` services to transfer data between consoles.
-+ An issue was fixed in `ncm` that caused an error when the OS tried to enumerate installed SD card content.
-+ Several issues were fixed, and usability and stability were improved.
-## 0.19.0
-+ Support was added for 12.0.0.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `sm`, `boot2`, `pgl` were updated to reflect the latest official behaviors.
-    + **Please Note**: 12.0.0 added a new protocol for IPC ("tipc"), which has been freshly reimplemented in its entirety.
-      + It is possible there may be as of yet unfound issues; if there are, please send the appropriate crash reports to SciresM (SciresM#0524 on discord).
-      + Homebrew which uses atmosphere extensions (including the mitm API) will need to be re-compiled in order to function on 0.19.0.
-        + I apologize for this, but it's unavoidable for technical reasons. If you're affected by this and mad about it, please contact SciresM to complain.
-  + `erpt` was partially updated to reflect the latest official behaviors.
-    + New features were added to erpt to track the activity of running applets, and to detect when a forced shutdown occurs.
-    + These behaviors have been temporarily stubbed, as they are not necessary for 12.0.0 to run (and their outputs won't be saved anywhere).
-    + A future atmosphère update will implement these behaviors, in the interest of reflecting official logic as faithfully as we can.
-+ Atmosphère no longer uses the /contents/ folder for its own programs.
-  + Atmosphère's system modules are now bundled together in the single file "stratosphere.romfs".
-    + For those working on developing for atmosphère, executables inside the /contents/ directory will be preferred to those in "stratosphere.romfs".
-  + **Please Note**: In order to facilitate this change (and the desired behavior), the first time you boot after extracting a release zip, atmosphère system modules inside /contents/ will be deleted.
-    + This will have no impact on user programs (it only removes programs with specific program ids).
-+ Improvements were made to mesosphere, including:
-  + An extension InfoType was added for getting the current process handle, without having to spawn a thread and do IPC with oneself.
-  + An issue was fixed in SvcSetDebugThreadContext.
-  + An issue was fixed when doing IPC with user buffers.
-+ Support was fixed for toggling the custom setting `usb!usb30_force_enabled` on 9.0.0+.
-  + This was broken by Nintendo's introducing a dependency that made USB a requirement to launch before custom settings are parsed.
-  + Since the fix, you can now toggle the setting (as you could prior to atmosphère 0.9.4), and it will work as expected.
-  + **Please Note**: Enabling USB 3.0 often severely impacts wireless communications.
-    + Because of this, the setting will default to off. If you experience issues with it enabled, consider disabling it.
-+ A warning was added to daybreak when resetting the console to factory settings.
-+ Substantial work was completed towards atmosphere's upcoming implementation of the host target connection protocol.
-  + Once completed, users will be able to interact with a Switch running atmosphère via a PC application ("Starlink") currently under development.
-    + Planned eventual features for connected consoles include a gdbstub, interacting with memory (for cheat development), streaming gameplay audio and video, and accessing the Switch's SD card filesystem.
-    + Switch homebrew will also have access to a (configurable and sandboxed) filesystem on the host PC, while connected.
-  + Towards this end, the following was accomplished:
-    + The "htc" system module was reimplemented completely.
-    + The system module which provides remote access to the SD card was reimplemented completely.
-  + This is currently the active focus of atmosphère's development.
-  + **Please Note**: Support is not yet completed, and users are disadvised from interacting with the related settings for the time being, unless they particularly know what they're doing.
-+ A number of minor issues were fixed, including:
-  + A bug was fixed in `dmnt` that could cause a fatal when launching certain games with cheats active.
-  + An issue was fixed that could cause an abort in `sm` when using a large number of custom system modules.
-  + An issue was fixed that prevented launching gamecards on 1.0.0.
-  + Minor issues were fixed in the cheat virtual machine's behavior.
-+ Several issues were fixed, and usability and stability were improved.
-## 0.18.1
-+ A number of minor issues were fixed, including:
-  + The new `dns.mitm` module added in 0.18.0 no longer fatal errors when receiving port=nullptr.
-    + This fixes youtube ad-blocking, and possibly other usecases.
-  + A bug was fixed that caused ams.mitm to incorrectly cache data storages.
-    + This potentially broke DLC when using romfs mods, and could have caused other issues (e.g. with custom themes, and maybe other cases).
-  + A bug was fixed in power state control module registration.
-    + This might fix a weird edge case with system module dependencies on sleep/wake, but probably nobody should notice any differences.
-  + A bug was fixed where mesosphere sometimes treated virtual core IDs as though they were physical core IDs.
-    + This had zero impact, because for Switch virtual core == physical core, but it could have affected future platforms if it had remained unresolved.
-+ Several issues were fixed, and usability and stability were improved.
-## 0.18.0
-+ A new mitm module was added (`dns.mitm`).
-  + This provides a highly configurable mechanism for redirecting DNS resolution requests.
-  + By default atmosphère redirects resolution requests for official telemetry servers to a loopback address.
-  + Documentation on how to configure `dns.mitm` to meet your more specific needs may be found [here](https://github.com/Atmosphere-NX/Atmosphere/blob/master/docs/features/dns_mitm.md).
-+ The service framework API (`sf`) was refactored to be more accurate to official logic and greatly reduce memory requirements.
-  + The comparison of atmosphère module memory usage versus Nintendo's found [here](https://github.com/Atmosphere-NX/Atmosphere/wiki/Memory-Comparisons) was updated to reflect this.
-  + **Please Note**: If you are a developer using the libstratosphere service APIs, some updating may be required. Contact SciresM#0524 on discord for assistance if required.
-+ A number of deprecations were removed, following a general codebase cleanup:
-  + The `sm` extension to not unregister services on connection close was superseded by official opt-in logic in 11.0.0, and has been removed in favor of official logic.
-    + This should have zero impact on users.
-  + The temporary `hid-mitm` added in 0.9.0 has finally been removed, following over a year of deprecation.
-    + There shouldn't be any homebrew in use still affected by this, but the situation will be monitored.
-    + If this is somehow still a real issue, an unaffiliated hid mitm sysmodule providing the same functionality can be created and released, separate from atmosphère itself.
-+ Several issues were fixed, and usability and stability were improved.
-## 0.17.1
-+ A number of atmosphère's modules were using more memory than their Nintendo equivalent's in 0.17.0; a number of code generatio tweaks have been applied to fix this across the board.
-  + A detailed comparison of atmosphère module memory usage versus Nintendo's was made and can be found [here](https://github.com/Atmosphere-NX/Atmosphere/wiki/Memory-Comparisons).
-+ Several minor bugs were fixed, including:
-  + A bug was fixed in mesosphère that caused games which attempt to map more memory than the Switch has to fail.
-    + This affected "Piczle Lines DX 500 More Puzzles!", and possibly other games.
-  + Enabling configuration to "blank" PRODINFO no longer causes a hang on Mariko devices (or any devices with newer format).
-+ Several issues were fixed, and usability and stability were improved.
-## 0.17.0
-+ fusee was heavily rewritten in order to add support for Mariko hardware.
-  + **Please Note**: Mariko hardware currently has no (and may not ever have any) software exploits; fusee works when loaded from bootloader context with the right keys in the security engine. No means of getting the system into this state is provided.
-+ An issue was fixed in the way shutdown was performed on Erista hardware.
-  + This fixes an issue that caused OFW to black screen on boot after power off from atmosphere without first doing a reboot.
-  + This also substantially improves power drain when the system is shut off; consoles powered off from Atmosphere should now drain battery at the same reduced rate as original firmware.
-+ A number of minor changes were made, including:
-  + A number of inconsistencies in the build system were fixed.
-    + For those building atmosphère at home, the `boot` sysmodule will no longer rebuild every time make is invoked.
-    + This substantially improves build times during development iteration.
-  + `sm` was updated to more accurately reflect how official code manages request deferral.
-  + `mesosphère` was updated to more accurately reflect official kernel management of the trace buffer.
-  + `mesosphère` was updated to improve kernel loader's logic by taking advantage of the assumption that we only boot our kernel, not Nintendo's.
-+ As it has been a few months with zero reported issues, `mesosphère` is now opt-out.
-    + Users who wish to begin using or continue using mesosphere should use the standard/cool kids zip ("atmosphere-").
-    + Users who wish to opt-out of mesosphere should download and extract the opt-out zip ("atmosphere-WITHOUT_MESOSPHERE-").
-+ Several issues were fixed, and usability and stability were improved.
-## 0.16.2
-+ Atmosphère release zips no longer bundle BCT.ini, instead relying on defaults in code.
-  + This means atmosphere updates should no longer overwrite any user configuration at all.
-  + If you wish to modify BCT.ini config, copy the template from /config_templates/ as with other configuration.
-+ `pgl` and `creport` were further updated to reflect differences in official behavior in 11.0.0.
-+ An issue was fixed that caused creport to be launched multiple times on process crash.
-  + This fixes the "duplicate reports" issue that sometimes plagued people.
-+ A new system setting (`atmosphere!enable_am_debug_mode`) configuring am to use debug mode.
-  + If you are not a developer or don't see a clear use for this, leave it configured to the default (off).
-+ Reboot to payload NRO was updated to fix support with certain payloads.
-+ Support was fixed for atmosphere's extension to support homebrew use of new (8.0.0+) kernel mappings.
-  + In particular, when running tracing debug builds of `mesosphère`, hbloader now has access to the kernel trace buffer.
-+ Several issues were fixed, and usability and stability were improved.
-## 0.16.1
-+ Support was added for 11.0.1.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-    + A new svc::InfoType added in 11.0.0 was implemented (it wasn't discovered before 0.16.0 released).
-    + The new Control Flow Integrity (CFI) logic added in 11.0.0 kernel was implemented.
-+ `fs` logic was refactored and cleaned up to reflect some newer sysmodule behavioral and structural changes.
-+ `exosphère` was updated to allow dynamic control of what uart port is used for logging.
-  + This can be controlled by editing the `log_port`, `log_baud_rate`, and `log_inverted` fields in `exosphere.ini`.
-+ `mesosphère` was updated to improve debugging capabilities.
-  + This is still a work in progress, but developers may be interested.
-+ A bug was fixed that caused `fatal` to fatal error if the fatal process was already being debugged.
-+ Several issues were fixed, and usability and stability were improved.
-## 0.16.0
-+ Support was added for 11.0.0.
-  + `exosphère` was updated to reflect the latest official secure monitor behavior.
-  + `mesosphère` was updated to reflect the latest official kernel behavior.
-  + `loader`, `sm`, `boot`, `pgl` were updated to reflect the latest official behaviors.
-    + **Please Note**: 11.0.0 implements an opt-in version of the atmosphère `sm` extension that allows for closing session without unregistering services.
-      + Correspondingly, the extension will be deprecated in favor of the new official opt-in command. In 0.17.0, it will be removed entirely.
-      + If your custom system module relies on this extension (however unlikely that seems to me), please update it accordingly.
-  + `erpt` was partially updated to provide compatibility with 11.0.0.
-    + The latest firmware attaches additional fields and context information to logs.
-    + A future atmosphère update will implement this logic, so that users who are interested can also get the new information when examining their logs.
-  + **Please Note**: 11.0.0 introduced breaking changes to the `usb` system module's `usb:ds` API.
-    + Homebrew which uses the `usb:ds` service should rebuild with the latest libnx version to support running on 11.0.0.
-+ The `boot` system module was rewritten to reflect the huge driver changes introduced in 8.0.0.
-  + This includes a number of improvements to both logo display and battery management logic.
-+ Support was added for configuring the address space width for `hbl`.
-  + The `hbl_config!override_address_space_(#)` and `hbl_config!override_any_app_address_space` can now be set to `39_bit`, `36_bit`, or `32_bit` to control the address space for hbl on a per-override basis.
-  + If a configuration has not been set, hbl will now default to 39-bit address space.
-    + Previously, a legacy 36-bit address space was always used to maintain compatibility with 1.0.0.
-    + A new loader extension was added to support 39-bit whenever possible (including mesosphere-on-1.0.0), with fallback to 36-bit when unavailable.
-+ Support was added to a number of components for running on Mariko hardware.
-  + The `boot` system module can now safely be run on mariko hardware, performing correct hardware initialization.
-  + Daybreak (and generally, system update logic) were updated to be usable on Mariko.
-  + Boot0 protection/management logic was updated to perform correct actions on Mariko.
-  + Reboot to payload does not and cannot work on Mariko. Correspondingly, A "fatal error" handler was written, to display and save fatal errors from within TrustZone.
-  + **Please Note:** Atmosphere is still not properly usable on Mariko hardware.
-    + In particular, wake-from-sleep will not properly function (the magic numbers aren't set correctly), among a few other minor issues.
-+ `exosphère` received support for building under debug configuration.
-  + A small (otherwise unused) portion of IRAM is now reserved for debug-only exosphere code (this region is unused/untouched under release config).
-  + This enables logging (including printf) to uart from the secure monitor, for those interested.
-+ A number of bugs were fixed, including:
-  + Minor issues in a number of filesystem related code were fixed.
-  + An issue was fixed that could cause NCM to abort on consoles which came with 3.0.x and were never updated.
-+ Several issues were fixed, and usability and stability were improved.
-## 0.15.0
-+ fusee-primary's panic display was updated to automatically identify and give suggestions to resolve many of the most common errors users encounter.
-+ Having been tested as well as I can alone, `mesosphere` (atmosphère's reimplementation of the Nintendo Switch kernel) is now available for users interested in trying it.
-  + Beginning in this release and until it is stable and well-tested, atmosphère will distribute two zips.
-    + Users who wish to opt-in to mesosphere should download and extract the "cool kids" zip ("atmosphere-EXPERIMENTAL-").
-    + Users who do not wish to use mesosphere should continue using the normal zip ("atmosphere-").
-  + Users may detect whether mesosphere is active in system settings.
-    + When mesosphere is active, the system version string will display "M.15.0" rather than "0.15.0", and so on for future releases.
-    + Crash reports and the like will contain information on whether or not the user is using mesosphere, as well.
-  + There are "probably" no material user-facing benefits to using mesosphere at this time.
-    + Developers may be interested in the fact that mesosphere provides many newer SVC APIs even when on lower firmware versions.
-    + The primary benefit to using mesosphere is that any issues you may encounter and report to me will be fixed.
-      + All users who choose to opt in to using mesosphere have my deepest gratitude.
-  + **Note:** If using hekate instead of fusee-primary, you will have to wait for the next hekate release for mesosphere to function, as hekate's support has not yet been included in an official release build.
-    + This will be updated in the release notes when hekate provides a new release.
-  + As mentioned in previous release notes, when mesosphere is stable and well-tested, it will be enabled by default and atmosphère's version will transition to 1.0.0.
-+ Having been tested sufficiently over the last half-year, Atmosphere's NCM implementation is now opt-out, rather than opt in.
-  + In the unlikely event that any issues are encountered, please report them to @SciresM.
-  + Users interested in opting out of using our implementation should set `stratosphere!disable_ncm = 1` in BCT.ini.
-  + The NCM implementation will stop being opt-out in a future update, probably around the same time that mesosphere becomes opt-out instead of opt-in.
-+ Several bugs were fixed, including:
-  + Loader now sets HBL's thread priority to a higher value when loading it in applet mode.
-    + This fixes an extremely-slow launch ("hang") when using applet-HBL with certain games that do not suspend while inactive (e.g. Super Mario Sunshine).
-  + set.mitm now caches user language configuration much more heavily.
-    + This severely reduces lag in certain games which misuse the "nn::oe::GetDesiredLanguage()" API.
-  + A bug was fixed that could cause erpt to fatal when loading an official save file that had error report attachments in it.
-+ General system stability improvements to enhance the user's experience.
-## 0.14.4
-+ Several bugs were fixed involving the official jit sysmodule added in 10.0.0.
-  + A Process handle leak was fixed when JitPlugin NRRs were registered with the `ro` sysmodule.
-    + This prevented processes using jit from being able to exit, causing a full system freeze.
-  + The `sm` atmosphere extension to not unregister services when the server's connection is closed was special-case disabled for `jit:u`.
-    + This extension is normally desirable in order to allow more concurrent processes to exist (as only 0x40 sm connections may ever be concurrently open), but official jit sysmodule relies on the behavior.
-    + This would cause crashes on attempts to launch a program using jit services more than once per reboot.
-+ General system stability improvements to enhance the user's experience.
-## 0.14.3
-+ Support was added for 10.2.0.
-+ General system stability improvements to enhance the user's experience.
-## 0.14.2
-+ A bug was fixed that could cause a deadlock when installing mitm services.
-  + Fixing this required a breaking change to the client behavior when installing a mitm service, and so custom sysmodules which use mitm will need to be re-compiled to function properly.
-+ A bug was fixed that caused atmosphere sysmodules to respond incorrectly when receiving invalid messages.
-+ A bug was fixed that caused fatal auto-reboot timing to work improperly.
-+ Support was added to fusee for loading binaries for `mesosphere`, atmosphère's reimplementation of the Nintendo Switch kernel.
-  + 0.14.2 does not include mesosphere, but those who are especially interested can build and test mesosphere themselves.
-  + In the future, to enable a sufficient testing period Atmosphère releases will distribute two zips for some time.
-    + One zip will use mesosphere, and the other will not.
-    + This will allow users who are interested to opt-in to mesosphere usage before it has been tested to be stable.
-  + When mesosphere is stable and well-tested, it will be enabled by default and Atmosphère's version will transition to 1.0.0.
-+ General system stability improvements to enhance the user's experience.
-## 0.14.1
-+ An issue was fixed in 0.14.0 that would cause a black screen on boot when the INI1's size was not aligned to 8 bytes.
-+ General system stability improvements to enhance the user's experience.
-## 0.14.0
-+ An API (`ams:su`) was added to allow homebrew to safely install system upgrades or downgrades.
-  + This is a re-implementation of the logic that `ns` uses to install gamecard system updates.
-  + Nintendo (and now atmosphère) uses an installation process that can recover no matter where a failure occurs, which should significantly improve the safety of custom system update installation.
-+ Support was added to `exosphère` for running on Mariko hardware.
-  + **Please note**: Atmosphère still does not support Mariko, and should not be run on Mariko yet.
-    + Certain stratosphere components do not handle mariko-specific logic fully correctly yet, and may initialize or interact with hardware incorrectly.
-    + This will be fixed and support will be added over the remainder of the Summer.
-+ A homebrew application (`daybreak`) was added that uses the system updater API (with thanks to @Adubbz for both design and implementation).
-  + `daybreak` is included with atmosphère, and functions as a safer/more accurate equivalent to e.g. ChoiDujourNX.
-  + Upgrades/downgrades can be installed from a folder containing the update NCAs on the SD card.
-  + Because the update logic functions identically to Nintendo's, `daybreak` will be safe to use on Mariko when the rest of atmosphère has support.
-  + **Please note**: Daybreak requires that meta (.cnmt) NCAs have the correct extension `.cnmt.nca`.
-    + This is because gamecard system update logic uses extension to determine whether to mount the content.
-    + [Several](https://gist.github.com/HookedBehemoth/df36b5970e1c5b1b512ec7bdd9043c6e) [scripts](https://gist.github.com/antiKk/279966c27fdfd9c7fe63b4ae410f89c4) have been made by community members to automatically rename folders with incorrect extensions.
-+ A bug was fixed that would cause file-based emummc to throw an error (showing a hexdump) on boot.
-  + Major thanks to @hexkyz for tracking down and resolving this.
-+ A number of minor issues were resolved, including:
-  + fusee now prints information to the screen when an error occurs, instead of getting stuck trying to initialize the display.
-  + A race condition in Horizon was worked around that could prevent boot under certain circumstances.
-  + A bug was fixed that would cause atmosphère modules to open ten copies of certain filesystems instead of one.
-    + This could cause object exhaustion under certain circumstances.
-+ For those interested in atmosphère's future development plans, the project's [roadmap](https://github.com/Atmosphere-NX/Atmosphere/blob/ac9832c5ce7be5832f6d29f6564a9c03e7efd22f/docs/roadmap.md) was updated.
-+ General system stability improvements to enhance the user's experience.
-## 0.13.0
-+ `exosphère`, atmosphère's secure monitor re-implementation, was completely re-written.
-  + `exosphère` was the first component authored for the project in early 2018. It is written in C, and in a style very different from the rest of atmosphère's code.
-    + This has made the codebase difficult to maintain as time has gone on.
-  + `exosphère` was also written to conform to constraints and assumptions that simply no longer apply when cfw is not launched from the web browser, and when warmboothax is possible.
-  + Even beyond these issues, `exosphère` used all but 1KB of the 64KB of space available to it. This was a problem for a few reasons:
-    + Each new system update added requires additional space to support (to add new keys and reflect various changes); 10.0.0 support used up 3 of the 4KB we had left.
-    + atmosphère will want to have software support for mariko hardware, and this is not possible to fit in 1 KB.
-  + The `exosphère` rewrite (which was codenamed `exosphère2` during development) solves these problems.
-  + The new codebase is C++20 written in atmosphère's style.
-    + This solves the maintainability problem, and should make understanding how the secure monitor works *much* easier for those interested in using the code as a reference implementation.
-  + In addition, the new implementation currently uses ~59.5 of the 64KB available.
-    + Several potential code changes are planned that can save/grant access to an additional ~2-3 KB if needed.
-      + Unlike the first codebase, the new `exosphère` actually already has space allocated for future keys/etc. It is currently expected that the reserved space will never be required.
-    + The previous implementation chose not to implement a number of "unimportant" secure monitor functions due to space concerns. The new code has enough breathing room that it can implement them without worries. :)
-  + Finally, the groundwork for mariko support has been laid -- there are only a few minor changes needed for the new secure monitor implementation to work on both erista and mariko hardware.
-    + **Please note**: `exosphère` is only one of many components, and many more need changes to support running on mariko hardware.
-      + Software-side support for executing on mariko hardware is expected some time during Summer 2020, though it should also be noted that this is not a hard deadline.
-  + **Please note**: The new `exosphère` binary is not abi-compatible with the old one. Users who boot using hekate should wait for it to update before running 0.13.0 (or boot fusee-primary via hekate).
-+ atmosphère's api for target firmware was changed. All minor/micro system versions are now recognized, instead of only major versions.
-  + This was required in order to support firmware version 5.1.0, which made breaking changes to certain IPC APIs that caused atmosphère 0.12.0 to abort.
-  + **Please note**: this is (unavoidably) a breaking change. System modules using atmosphere-libs will need to update to understand what firmware version they are running.
-+ `emummc` was updated to include the new changes.
-  + `emummc` now uses an updated/improved/faster SDMMC driver.
-  + File-based emummc is now almost as fast as raw partition-based emummc.
-+ For those interested in atmosphère's future development plans, the project's [roadmap](https://github.com/Atmosphere-NX/Atmosphere/blob/f68d33b70aed8954cc2c539e5934bcaf37ba51da/docs/roadmap.md) was updated.
-+ General system stability improvements to enhance the user's experience.
-
-## 0.12.0
-+ Configuration for exosphere was moved to sd:/exosphere.ini.
-  + This is to facilitate BIS protection changes described below.
-  + Hopefully having this outside of the Atmosphere folder will prevent accidental deletion, since this now contains important settings.
-+ Atmosphere's bis protection policy for the PRODINFO partition was substantially reworked.
-  + Support was added for "automatically" performing a "blanking" operation to PRODINFO without actually modifying NAND.
-    + This is equivalent to using the "incognito" homebrew tool, but NAND is never actually modified.
-    + This can be turned on in sysmmc by setting `blank_prodinfo_sysmmc=1` in exosphere.ini, and in emummc by setting `blank_prodinfo_emummc=1` in exosphere.ini.
-    + **Please note**: This is not known to be safe. There is a lack of research on whether the information blanked out is cached elsewhere in the system.
-      + Usage of this option is not encouraged for this reason.
-  + Support was added for writing to the PRODINFO partition, if a verified encrypted backup has been made.
-    + PRODINFO is the only system data that cannot be recovered if not backed up, and thus Atmosphere has backed it up to the SD card on boot for some time now.
-    + Users who wish to modify their calibration data may now do so unconditionally in emummc, and in sysmmc if `allow_writing_to_cal_sysmmc=1` is set in exosphere.ini.
-      + **Please note**: This is heavily discouraged, and the typical user will almost never want to do this.
-      + Setting this option will cause Atmosphere to attempt to verify (or create) an encrypted backup of the PRODINFO data to an unused region in the partition.
-        + The backup is encrypted with per-console keys that Atmosphere's developers do not know.
-      + If the backup is not verified or created, writes will not work. Users who have corrupted their PRODINFO in the past are encouraged to flash a good backup to allow use of this setting.
-      + Reads and writes to the region used for the securely encrypted backup will appear to succeed, but will actually read/write from a buffer filled with garbage in memory.
-  + Support will be investigated in the future for supporting booting with fully blanked calibration.
-    + This is desirable to allow boot to succeed for users who lost their calibration data due to bricking homebrew before bis protection was implemented.
-+ `creport` has been updated to use the new screenshot APIs added in 9.0.0+.
-  + On 10.0.0+, if a crash occurs in an application (not applet or sysmodule) a screenshot will now be automatically saved to the SD card.
-  + If the user applies a patch to vi on 9.0.0 (as the command this uses was previously for dev-units only), this can also work on 9.0.0.
-+ The new sysmodule `pgl` added in 10.0.0 was reimplemented.
-  + `pgl` ("Program Launcher", probably) is responsible for managing launched user-processes, previously this was handled by NS.
-  + The most exciting thing about pgl is that it finally provides an API for multiple clients to subscribe to process events.
-  + Using these new APIs, system modules / other homebrew can subscribe to be notified whenever a process event occurs.
-    + This means action can be taken on process launch, process exit, process crash, etc.
-  + A slight concern with Nintendo's implementation is that each subscriber object uses 0x448 bytes of memory, and N only reserves 8KB for all allocations in pgl.
-  + Atmosphere's implementation uses a 32KB heap, which should not be exhaustible.
-  + Atmosphere's implementation has a total memory footprint roughly 0x28000 bytes smaller than Nintendo's.
-+ A reimplementation was added for the `jpegdec` system module (thanks @HookedBehemoth)!
-  + This allows two sessions instead of 1, so homebrew can now use it for software jpeg decoding in addition to the OS itself.
-  + As usual the implementation has a very slightly smaller memory footprint than Nintendo's.
-+ `dmnt`'s Cheat VM was extended to add three new opcodes.
-  + The first new opcode, "ReadWriteStaticRegister", allows for cheats to read from a bank of 128 read-only static registers, and write to a bank of 128 write-only static registers.
-    + This can be used in concert with new IPC commands that allow a cheat manager to read or write the value of these static registers to have "dynamic" cheats.
-      + As an example, a cheat manager could write a value to a static register that a cheat to control how many of an item to give in a game.
-      + As another example, a cheat manager could read a static register that a cheat writes to to learn how many items a player has.
-+ The second and third opcodes are a pair, "PauseProcess" and "ResumeProcess".
-  + Executing pause process in a cheat will pause the game (it will be frozen) until a resume process opcode is used.
-    + These are also available over IPC, for cheat managers or system modules that want to pause or resume the attached cheat process.
-  + This allows a cheat to know that the game won't modify or access data the cheat is accessing.
-    + For example, this can be used to prevent Pokemon from seeing a pokemon a cheat is in the middle of injecting and turning it into a bad egg.
-+ A bug was fixed that would cause the console to crash when connected to Wi-Fi on versions between 3.0.0 and 4.1.0 inclusive.
-+ A bug was fixed that could cause boot to fail sporadically due to cache/tlb mismanagement when doing physical ASLR of the kernel.
-+ A number of other minor issues were addressed (and more of Atmosphere was updated to reflect other changes in 10.0.x).
-+ General system stability improvements to enhance the user's experience.
-
-## 0.11.1
-+ A bug was fixed that could cause owls to flicker under certain circumstances.
-  + For those interested in technical details, in 10.0.0 kernelldr/kernel no longer set cpuactlr_el1, assuming that it was set correctly by the secure monitor.
-  + However, exosphere did not set cpuactlr_el1. This meant that the register held the reset value going into boot.
-  + This caused a variety of highly erratic symptoms, including causing basically any game to crash seemingly randomly.
-+ A number of other major inaccuracies in exosphere were corrected.
-+ General system stability improvements to enhance the user's experience.
-
 ## 0.11.0
 + Support was added for 10.0.0.
   + Exosphere has been updated to reflect the new key import semantics in 10.0.0.
@@ -809,7 +22,6 @@
   + In particular, code implementing the os namespace is significantly more accurate.
   + In addition, Nintendo's allocators were implemented, allowing for identical memory efficiency versus Nintendo's implementations.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.10.5
 + Changes were made to the way fs.mitm builds images when providing a layeredfs romfs.
   + Building romfs metadata previously had a memory cost of about ~4-5x the file table size.
@@ -822,7 +34,6 @@
     + Romfs building can be made even more memory efficient, but unless games show up with even more absurdly huge file tables it seems not worth the speed trade-off.
 + A bug was fixed that caused Atmosphere's fatal error context to not dump TLS for certain processes.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.10.4
 + With major thanks to @Adubbz for his work, the NCM system module has now been re-implemented.
   + This was a major stepping stone towards the goal of having implementations everything in the Switch's package1/package2 firmware.
@@ -845,7 +56,6 @@
 + Atmosphere's fatal error context now dumps 0x100 of TLS.
   + This will make it much easier to fix bugs when an error report is dumped for whatever caused the crash.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.10.3
 + Support was added for 9.2.0.
 + Support was added for redirecting manual html content for games.
@@ -860,7 +70,6 @@
 + `ro` has been updated to reflect changes made in 9.1.0.
 + The temporary auto-migration added in 0.10.0 has been removed, since the transitionary period is well over.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.10.2
 + hbl configuration was made more flexible.
   + Up to eight specific program ids can now be specified to have their own override keys.
@@ -895,7 +104,6 @@
   + For now, users may re-enable this mitm by use of a custom setting (`atmosphere!enable_deprecated_hid_mitm`) to ease the transition process some.
   + Please note: support for this setting may be removed to save memory in a future atmosphere release.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.10.1
 + A bug was fixed that caused memory reallocation to the system pool to work improperly on firmware 5.0.0 and above.
   + Atmosphere was always trying to deallocate memory away from the applet pool and towards the system pool.
@@ -924,7 +132,6 @@
     + Please ensure your homebrew is updated.
 + Random number generation now uses TinyMT instead of XorShift.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.10.0
 + Support was added for 9.1.0
   + **Please note**: The temporary hid-mitm added in Atmosphere 0.9.0 will be removed in Atmosphere 0.10.1.
@@ -989,7 +196,6 @@
   + An off-by-one was fixed that could cause memory corruption in server memory management.
   + ... and too many more bugs fixed to reasonably list them all :)
 + General system stability improvements to enhance the user's experience.
-
 ## 0.9.4
 + Support was added for 9.0.0.
   + **Please note**: 9.0.0 made a number of changes that may cause some issues with homebrew. Details:
@@ -1009,7 +215,6 @@
   + Newer hardware uses new, per-firmware device key to generate BIS keys instead of the first device key, so previously the wrong keys were generated as backup.
   + This only affects units manufactured after ~5.0.0.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.9.3
 + Thanks to hexkyz, fusee's boot sequence has been greatly optimized.
   + Memory training is now managed by a separate binary (`fusee-mtc`, loaded by fusee-primary before fusee-secondary).
@@ -1033,7 +238,6 @@
   + Incorrect display output ("2000-0000") has been fixed. Fatal will now correctly show 2162-0002 when this occurs.
   + A longstanding bug in how fatal manages the displays has been fixed, and official display init behavior is now matched precisely.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.9.2
 + A number of emummc bugfixes were added (all thanks to @m4xw's hard work). The following is a summary of emummc changes:
   + Support for file-based emummc instances was fixed.
@@ -1057,12 +261,10 @@
   + The rewritten modules consistently have lower memory footprints, and should be easier to maintain going forwards.
   + The `sm`, `boot`, `spl`, `ro`, and `loader` modules have been tackled so far.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.9.1
 + Support was added for 8.1.0.
 + Please note, emummc is still considered **beta/experimental** -- this is not the inevitable bugfix update for it, although some number of bugs have been fixed. :)
 + General system stability improvements to enhance the user's experience.
-
 ## 0.9.0
 + Creport output was improved significantly.
   + Thread names are now dumped on crash in addition to 0x100 of TLS from each thread.
@@ -1087,7 +289,6 @@
     + This can be set to any arbitrary directory by setting `emummc!emummc_nintendo_path`.
   + To create a backup usable for emummc, users may use tools provided by the [hekate](https://github.com/CTCaer/hekate) project.
   + If, when using emummc, you encounter a bug, *please be sure to report it* -- that's the only way we can fix it. :)
-
 ## 0.8.10
 + A bug was fixed that could cause incorrect system memory allocation on 5.0.0.
   + 5.0.0 should now correctly have an additional 12 MiB allocated for sysmodules.
@@ -1104,7 +305,6 @@
     + NAND repair occurs when an unexpected shutdown or error happens during a system update.
     + This fixes a final edge case where AutoRCM might be removed by HOS, which could cause a user to burn fuses.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.9
 + A number of bugs were fixed, including:
   + A data abort was fixed when mounting certain partitions on NAND.
@@ -1130,7 +330,6 @@
   + `spl` (Secure Platform Services) is responsible for cryptographic operations, including all communications with the secure monitor (exosphère).
   + In the future, this may be used to provide extensions to the API for interacting with exosphère from userland.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.8
 + Support was added for firmware version 8.0.0.
 + Custom exception handlers were added to stratosphere modules.
@@ -1138,7 +337,6 @@
 + A bug was fixed in creport that caused games to hang when crashing under certain circumstances.
 + A bug was fixed that prevented maintenance mode from booting on 7.0.0+.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.7
 + A few bugs were fixed that could cause fatal to fail to show an error under certain circumstances.
 + A bug was fixed that caused an error when launching certain games (e.g. Hellblade: Senua's Sacrifice).
@@ -1154,7 +352,6 @@
   + Please note, this feature is **experimental**, and may cause problems. Please use at your own risk (and back up your saves before enabling it), as it still needs testing.
   + This can be enabled by setting `atmosphere!fsmitm_redirect_saves_to_sd` to 1 in `system_settings.ini`.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.6
 + A number of bugs were fixed, including:
   + A case of inverted logic was fixed in fs.mitm which prevented the flags system from working correctly.
@@ -1192,7 +389,6 @@
   + fs.mitm will also now cause requests to mount the HtmlDocument content for HBL's title to open the `sdmc:/atmosphere/hbl_html` folder.
     + By default, this just contains a URL whitelist.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.5
 + Support was added for overriding content on a per-title basis, separate from HBL override.
   + This allows for using mods on the same title that one uses to launch HBL.
@@ -1214,7 +410,6 @@
 + A bug was fixed that would cause Atmosphère's fatal screen to not show on 1.0.0-2.3.0.
 + A bug was fixed that caused Atmosphère's automatic ProdInfo backups to be corrupt.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.4
 + Support for 7.0.0/7.0.1 was added.
   + This is facilitated through a new payload, `sept`, which can be signed, encrypted, and then loaded by Nintendo's TSEC firmware.
@@ -1230,7 +425,6 @@
   + Performing a reboot from the reboot menu now reboots to atmosphere. This can be configured via `system_settings.ini`.
   + Performing a shutdown from the reboot menu now works properly with AutoRCM, and does a real shutdown.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.3
 + A custom warmboot firmware was implemented, which does not perform anti-downgrade fuse checks.
   + This fixes sleep mode when using a downgraded NAND.
@@ -1251,7 +445,6 @@
   + Fatal will now use this to reboot to sdmc:/atmosphere/reboot_payload.bin if present, when a vol button is pressed.
   + An example homebrew ("reboot_to_payload") was also written and is now included with Atmosphère.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.2
 + A number of bugs were fixed causing users to sometimes see `Key Derivation Failed!`.
   + KFUSE clock enable timings have been adjusted to allow time to stabilize before TSEC is granted access.
@@ -1261,7 +454,6 @@
 + A bug was fixed causing sleep mode to not work with debugmode enabled.
   + As a result, debugmode is now enabled in the default BCT.ini.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.1
 + A bug was fixed causing users to see `Failed to enable SMMU!` if fusee had previously rebooted.
   + This message will still occur sporadically if fusee is not launched from coldboot, but it can never happen twice in a row.
@@ -1283,7 +475,6 @@
 + On fatal error, the user can now choose to perform a standard reboot via the power button, or a reboot into RCM via either volume button.
 + A custom message was added to `fatal` for when an Atmosphère API version mismatch is detected (2495-1623).
 + General system stability improvements to enhance the user's experience.
-
 ## 0.8.0
 + A custom `fatal` system module was added.
   + This re-implements and extends Nintendo's fatal module, with the following features:
@@ -1317,7 +508,6 @@
   + By default, new keys will automatically be derived without user input.
   + Support is also present for loading new keys from `atmosphere/prod.keys` or `atmosphere/dev.keys`
 + General system stability improvements to enhance the user's experience.
-
 ## 0.7.5
 + DRAM training was added to fusee-secondary, courtesy @hexkyz.
   + This greatly improves the speed of memory accesses during boot, resulting in a boot time that is ~200-400% faster.
@@ -1326,7 +516,6 @@
     + This matches the improvement Nintendo added to official creport in 6.1.0.
   + The code region detection heuristic was further improved by checking whether an address points to .rodata or .rwdata, instead of just .text.
   + This means that a crash appears in a loaded NRO (or otherwise discontiguous) code region, creport will be able to detect all active code regions, and not just that one.
-
 ## 0.7.4
 + [libstratosphere](https://github.com/Atmosphere-NX/libstratosphere) has been completely refactored/rewritten, and split into its own, separate submodule.
   + While this is mostly "under the hood" for end-users, the refactor is faster (improving both boot-time and runtime performance), more accurate (many of the internal IPC structures are now bug-for-bug compatible with Nintendo's implementations), and significantly more stable (it fixes a large number of bugs present in the old library).
@@ -1347,13 +536,11 @@
   + PM now only gives full FS permissions to the active KIPs. This fixes a potential crash where new processes might be unable to be registered with FS.
 + The `make dist` target now includes the branch in the generated zip name.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.7.3
 + Loader and fs.mitm now try to reload loader.ini before reading it. This allows for changing the override button combination/HBL title id at runtime.
 + Added a MitM between set:sys and qlaunch, used to override the system version string displayed in system settings.
   + The displayed system version will now display `<Actual version> (AMS <x>.<y>.<z>)`.
 + General system stability improvements to enhance the user's experience.
-
 ## 0.7.2
 + Fixed a bug in fs.mitm's LayeredFS read implementation that caused some games to crash when trying to read files.
 + Fixed a bug affecting 1.0.0 that caused games to crash with fatal error 2001-0106 on boot.

docs/cheats.md

@@ -0,0 +1,365 @@
+# Cheats
+Atmosphère supports Action-Replay style cheat codes, with cheats loaded off of the SD card.
+
+## Cheat Loading Process
+By default, Atmosphère will do the following when deciding whether to attach to a new application process:
+
++ Retrieve information about the new application process from `pm` and `loader`.
++ Check whether a user-defined key combination is held, and stop if not.
+  + This defaults to "L is not held", and can be configured the same way as `fs.mitm` override keys.
+  + The ini key to configure this is `cheat_enable_key`.
++ Check whether the process is a real application, and stop if not.
+  + This guards against applying cheat codes to the homebrew loader.
++ Attempt to load cheats from `atmosphere/titles/<title_id>/cheats/<build_id>.txt`, where `build_id` is the hexadecimal representation of the first 8 bytes of the application's main executable's build id.
+  + If no cheats are found, then the cheat manager will stop.
++ Open a kernel debug session for the new application process.
++ Signal to a system event that a new cheat process has been attached to.
+
+This behavior ensures that cheat codes are only loaded when the user would want them to.
+
+In cases where dmnt has not activated the cheat manager, but the user wants to make it do so anyway, the cheat manager's service API provides a `ForceOpenCheatProcess` command that homebrew can use. This command will cause the cheat manager to try to force itself to attach to the process.
+
+By default, all cheat codes listed in the loaded .txt file will be toggled on. This is configurable by the user, and the default can be set to toggled off by editing the `atmosphere!dmnt_cheats_enabled_by_default` entry to 0 instead of 1.
+
+Users may use homebrew programs to toggle cheats on and off at runtime via the cheat manager's service API.
+
+## Cheat Code Compatibility
+
+Atmosphère manages cheat code through the execution of a small, custom virtual machine. Care has been taken to ensure that Atmosphère's cheat code format is fully backwards compatible with the pre-existing cheat code format, though new features have been added and bugs in the pre-existing cheat code applier have been fixed. Here is a short summary of the changes from the pre-existing format:
+
++ A number of bugs were fixed in the processing of conditional instructions.
+  + The pre-existing implementation was fundamentally broken, and checked for the wrong value when detecting the end of a conditional block.
+  + The pre-existing implementation also did not properly decode instructions, and instead linearly scanned for the terminator value. This caused problems if an instruction happened to encode a terminator inside its immediate values.
+  + The pre-existing implementation did not bounds check, and thus certain conditional cheat codes could cause it to read out-of-bounds memory, and potentially crash due to a data abort.
++ Support was added for nesting conditional blocks.
++ An instruction was added to perform much more complex arbitrary arithmetic on two registers.
++ An instruction was added to allow writing the contents of register to a memory address specified by another register.
++ The pre-existing implementation did not correctly synchronize with the application process, and thus would cause heavy lag under certain circumstances (especially around loading screens). This has been fixed in Atmosphère's implementation.
+
+## Cheat Code Format
+
+The following provides documentation of the instruction format for the virtual machine used to manage cheat codes.
+
+Typically, instruction type is encoded in the upper nybble of the first instruction u32.
+
+### Code Type 0: Store Static Value to Memory
+
+Code type 0 allows writing a static value to a memory address.
+
+#### Encoding
+
+`0TMR00AA AAAAAAAA VVVVVVVV (VVVVVVVV)`
+
++ T: width of memory write (1, 2, 4, or 8 bytes)
++ M: memory region to write to (0 = Main NSO, 1 = Heap)
++ R: Register to use as an offset from memory region base.
++ A: Immediate offset to use from memory region base.
++ V: Value to write.
+
+---
+
+### Code Type 1: Begin Conditional Block
+
+Code type 1 performs a comparison of the contents of memory to a static value.
+
+If the condition is not met, all instructions until the appropriate conditional block terminator are skipped.
+
+#### Encoding
+
+`1TMC00AA AAAAAAAA VVVVVVVV (VVVVVVVV)`
+
++ T: width of memory write (1, 2, 4, or 8 bytes)
++ M: memory region to write to (0 = Main NSO, 1 = Heap)
++ C: Condition to use, see below.
++ A: Immediate offset to use from memory region base.
++ V: Value to compare to.
+
+#### Conditions
+
++ 1: >
++ 2: >=
++ 3: <
++ 4: <=
++ 5: ==
++ 6: !=
+
+---
+
+### Code Type 2: End Conditional Block
+
+Code type 2 marks the end of a conditional block (started by Code Type 1 or Code Type 8).
+
+#### Encoding
+
+`20000000`
+
+---
+
+### Code Type 3: Start/End Loop
+
+Code type 3 allows for iterating in a loop a fixed number of times.
+
+#### Start Loop Encoding
+
+`300R0000 VVVVVVVV`
+
++ R: Register to use as loop counter.
++ V: Number of iterations to loop.
+
+#### End Loop Encoding
+
+`310R0000`
+
++ R: Register to use as loop counter.
+
+---
+
+### Code Type 4: Load Register with Static Value
+
+Code type 4 allows setting a register to a constant value.
+
+#### Encoding
+
+`400R0000 VVVVVVVV VVVVVVVV`
+
++ R: Register to use.
++ V: Value to load.
+
+---
+
+### Code Type 5: Load Register with Memory Value
+
+Code type 5 allows loading a value from memory into a register, either using a fixed address or by dereferencing the destination register.
+
+#### Load From Fixed Address Encoding
+
+`5TMR00AA AAAAAAAA`
+
++ T: width of memory read (1, 2, 4, or 8 bytes)
++ M: memory region to write to (0 = Main NSO, 1 = Heap)
++ R: Register to load value into.
++ A: Immediate offset to use from memory region base.
+
+#### Load from Register Address Encoding
+
+`5TMR10AA AAAAAAAA`
+
++ T: width of memory read (1, 2, 4, or 8 bytes)
++ M: memory region to write to (0 = Main NSO, 1 = Heap)
++ R: Register to load value into.
++ A: Immediate offset to use from register R.
+
+---
+
+### Code Type 6: Store Static Value to Register Memory Address
+
+Code type 6 allows writing a fixed value to a memory address specified by a register.
+
+#### Encoding
+
+`6T0RIor0 VVVVVVVV VVVVVVVV`
+
++ T: width of memory write (1, 2, 4, or 8 bytes)
++ R: Register used as base memory address.
++ I: Increment register flag (0 = do not increment R, 1 = increment R by T).
++ o: Offset register enable flag (0 = do not add r to address, 1 = add r to address).
++ r: Register used as offset when o is 1.
++ V: Value to write to memory.
+
+---
+
+### Code Type 7: Legacy Arithmetic
+
+Code type 7 allows performing arithmetic on registers.
+
+However, it has been deprecated by Code type 9, and is only kept for backwards compatibility.
+
+#### Encoding
+
+`7T0RC000 VVVVVVVV`
+
++ T: width of arithmetic operation (1, 2, 4, or 8 bytes)
++ R: Register to apply arithmetic to.
++ C: Arithmetic operation to apply, see below.
++ V: Value to use for arithmetic operation.
+
+#### Arithmetic Types
+
++ 0: Addition
++ 1: Subtraction
++ 2: Multiplication
++ 3: Left Shift
++ 4: Right Shift
+
+---
+
+### Code Type 8: Begin Keypress Conditional Block
+
+Code type 8 enters or skips a conditional block based on whether a key combination is pressed.
+
+#### Encoding
+
+`8kkkkkkk`
+
++ k: Keypad mask to check against, see below.
+
+Note that for multiple button combinations, the bitmasks should be ORd together.
+
+#### Keypad Values
+
+Note: This is the direct output of `hidKeysDown()`.
+
++ 0000001: A
++ 0000002: B
++ 0000004: X
++ 0000008: Y
++ 0000010: Left Stick Pressed
++ 0000020: Right Stick Pressed
++ 0000040: L
++ 0000080: R
++ 0000100: ZL
++ 0000200: ZR
++ 0000400: Plus
++ 0000800: Minus
++ 0001000: Left
++ 0002000: Up
++ 0004000: Right
++ 0008000: Down
++ 0010000: Left Stick Left
++ 0020000: Left Stick Up
++ 0040000: Left Stick Right
++ 0080000: Left Stick Down
++ 0100000: Right Stick Left
++ 0200000: Right Stick Up
++ 0400000: Right Stick Right
++ 0800000: Right Stick Down
++ 1000000: SL
++ 2000000: SR
+
+---
+
+### Code Type 9: Perform Arithmetic
+
+Code type 9 allows performing arithmetic on registers.
+
+#### Register Arithmetic Encoding
+
+`9TCRS0s0`
+
++ T: width of arithmetic operation (1, 2, 4, or 8 bytes)
++ C: Arithmetic operation to apply, see below.
++ R: Register to store result in.
++ S: Register to use as left-hand operand.
++ s: Register to use as right-hand operand.
+
+#### Immediate Value Arithmetic Encoding
+
+`9TCRS100 VVVVVVVV (VVVVVVVV)`
+
++ T: width of arithmetic operation (1, 2, 4, or 8 bytes)
++ C: Arithmetic operation to apply, see below.
++ R: Register to store result in.
++ S: Register to use as left-hand operand.
++ V: Value to use as right-hand operand.
+
+#### Arithmetic Types
+
++ 0: Addition
++ 1: Subtraction
++ 2: Multiplication
++ 3: Left Shift
++ 4: Right Shift
++ 5: Logical And
++ 6: Logical Or
++ 7: Logical Not (discards right-hand operand)
++ 8: Logical Xor
++ 9: None/Move (discards right-hand operand)
+
+---
+
+### Code Type 10: Store Register to Memory Address
+
+Code type 10 allows writing a register to memory.
+
+#### Encoding
+
+`ATSRIOxa (aaaaaaaa)`
+
++ T: width of memory write (1, 2, 4, or 8 bytes)
++ S: Register to write to memory.
++ R: Register to use as base address.
++ I: Increment register flag (0 = do not increment R, 1 = increment R by T).
++ O: Offset type, see below.
++ x: Register used as offset when O is 1, Memory type when O is 3, 4 or 5.
++ a: Value used as offset when O is 2, 4 or 5.
+
+#### Offset Types
+
++ 0: No Offset
++ 1: Use Offset Register
++ 2: Use Fixed Offset
++ 3: Memory Region + Base Register
++ 4: Memory Region + Relative Address (ignore address register)
++ 5: Memory Region + Relative Address + Offset Register
+---
+
+### Code Type 11: Reserved
+
+Code Type 11 is currently reserved for future use.
+
+---
+
+### Code Type 12-15: Extended-Width Instruction
+
+Code Types 12-15 signal to the VM to treat the upper two nybbles of the first dword as instruction type, instead of just the upper nybble.
+
+This reserves an additional 64 opcodes for future use.
+
+---
+
+### Code Type 0xC0: Begin Register Conditional Block
+
+Code type 0xC0 performs a comparison of the contents of a register and another value. This code support multiple operand types, see below.
+
+If the condition is not met, all instructions until the appropriate conditional block terminator are skipped.
+
+#### Encoding
+
+```
+C0TcSX##
+C0TcS0Ma aaaaaaaa
+C0TcS1Mr
+C0TcS2Ra aaaaaaaa
+C0TcS3Rr
+C0TcS400 VVVVVVVV (VVVVVVVV)
+C0TcS5X0
+```
+
++ T: width of memory write (1, 2, 4, or 8 bytes)
++ c: Condition to use, see below.
++ S: Source Register
++ X: Operand Type, see below.
++ M: Memory Type (operand types 0 and 1)
++ R: Address Register (operand types 2 and 3)
++ a: Relative Address (operand types 0 and 2)
++ r: Offset Register (operand types 1 and 3)
++ X: Other Register (used for operand type 5)
++ V: Value to compare to (operand type 4)
+
+#### Operand Type
+
++ 0: Memory Base + Relative Offset
++ 1: Memory Base + Offset Register
++ 2: Register + Relative Offset
++ 3: Register + Offset Register
++ 4: Static Value
++ 5: Other Register
+
+#### Conditions
+
++ 1: >
++ 2: >=
++ 3: <
++ 4: <=
++ 5: ==
++ 6: !=

docs/components/detail/exosphere_memory_layout.txt

@@ -1,103 +0,0 @@
-exosphere, storage requirements:
-
-Nonvolatile memory:
-0xE000
-
-Volatile memory: 0x2000
-
-Physical Address Space:
--0x7C010000-0x7C012000 - boot code/volatile memory
--0x7C012000-0x7C01E000 - program region
--0x7C01E000-0x7C01F000 - global data/context
--0x7C01F000-0x7C020000 - L2/L3 page table
-
--0x7C020000-0x7C040000 - Mariko-only program region
--0x7C040000-0x7C048000 - Mariko-only program stack
--0x7C048000-0x7C050000 - Reserved Mariko TZRAM (SE context carveouts, etc)
-
-Virtual Address Space:
-
-L1: 0x40 bytes.
-
-L1 Entries:
-    -0 (0x000000000-0x040000000): Empty
-    -1 (0x040000000-0x080000000): Identity Mapping/Empty
-    -2 (0x080000000-0x0C0000000): DRAM Mapping/Empty
-    -3 (0x0C0000000-0x100000000): DRAM Mapping/Empty
-    -4 (0x100000000-0x140000000): Empty
-    -5 (0x140000000-0x180000000): Empty
-    -6 (0x180000000-0x1C0000000): Empty
-    -7 (0x1C0000000-0x200000000): Virtual Region
-
-L2 Page and L3 page are both0x7C01F000
-
-L2 Entries:
-    -0x040000000 (Identity IRAM Table)
-        - Entry Used: 0x000
-    -0x07C000000 (Identity TZRAM Table)
-        - Entry Used: 0x1E0
-    -0x1F0000000 (Virtual Region Table)
-        - Entry Used: 0x180
-
-L3 Entries:
-    - Identity TZRAM mapping (0x7C010000-0x7C020000)
-        - Entry Used: 0x010-0x01F
-    - Identity IRAM mapping  (0x40020000-0x40040000)
-        - Entry Used: 0x020-0x03F
-    - Virtual Device region (0x1F0040000-0x1F0080000)
-        - Entry Used: 0x040-0x07F
-    - Read Only TZRAM Alias (0x1F00A0000-0x1F00B0000)
-        - Entry Used: 0x0A0-0x0AF
-    - Program region        (0x1F00C0000-0x1F00CC000)
-        - Entry Used: 0x0C0-0x0CB
-    - Mariko Program region (0x1F00D0000-0x1F00F0000)
-        - Entry Used: 0x0D0-0x0EF
-    - Mariko Program stack  (0x1F00F4000-0x1F00FC000)
-        - Entry Used: 0x0F4-0x0FB
-    - Secure DRAM Storage   (0x1F0100000-0x1F0110000)
-        - Entry Used: 0x100-0x10F
-    - Debug DRAM Storage    (0x1F0110000-0x1F0114000)
-        - Entry Used: 0x110-0x113
-    - SC7 IRAM Work Space   (0x1F0120000-0x1F0130000)
-        - Entry Used: 0x120-0x12F
-    - SC7 IRAM Firmware     (0x1F0140000-0x1F0141000)
-        - Entry Used: 0x140-0x140
-    - Debug Code            (0x1F0150000-0x1F0154000)
-        - Entry Used: 0x150-0x153
-    - Reserved For Debug    (0x1F0160000-0x1F0170000)
-        - Entry Used: 0x160-0x16F
-    - Boot Code             (0x1F01C0000-0x1F01C2000)
-        - Entry Used: 0x1C0-0x1C1
-    - AMS IRAM Page         (0x1F01F2000-0x1F01F2000)
-        - Entry Used: 0x1F2-0x1F2
-    - AMS User Page         (0x1F01F4000-0x1F01F4000)
-        - Entry Used: 0x1F4-0x1F4
-    - SMC User Page         (0x1F01F6000-0x1F01F6000)
-        - Entry Used: 0x1F6-0x1F6
-    - Volatile (Data)       (0x1F01F8000-0x1F01F9000)
-        - Entry Used: 0x1F8-0x1F8
-    - Volatile (Stacks)     (0x1F01FA000-0x1F01FB000)
-        - Entry Used: 0x1FA-0x1FA
-    - Global Data           (0x1F01FC000-0x1F01FD000)
-
-
-NV Global Data needs:
-    Exosphere + Emummc Config (<=0x200)
-    Boot Config[0x400]
-    RSA Context(0x100)
-    Old Device Keys[0x20][0x10];
-    Old Master Keys[0x20][0x10];
-    Imported Rsa Keys[4][0x200];
-    CPU Ctx[4][0x100];
-
-Total: 0x1700
-
-Global Data Page (accessible via X18):
-    0x000-0x200: Exosphere Config
-    0x200-0x400: Emummc Config
-    0x400-0x800: Sealed AES Keys
-    0x800-0xC00: Boot Config
-    0xC00-0xFFF: CPU contexts. Can be replaced, but this fits exactly so minimizes program space waste.
-
-Volatile Global Data needs:
-    Random Cache 0x400 bytes

docs/components/emummc.md

@@ -1,4 +0,0 @@
-# emummc
-emummc is a collaborative project that provides eMMC storage emulation.
-
-Please refer to the project's repository [here](https://github.com/m4xw/emuMMC) for detailed instructions and documentation.

docs/components/exosphere.md

@@ -1,76 +1,10 @@
-# exosphère
-exosphère is a customized reimplementation of the Horizon OS's Secure Monitor.
-The Secure Monitor follows the same design principle as Arm's TrustZone and both terms can be used interchangeably in this context. It runs at the highest privilege mode (EL3) available to the main processor and is responsible for all the sensitive cryptographic operations needed by the system as well as power management for each CPU.
+# Exosphère
+Exosphère is a reimplementation of Arm's TrustZone (TZ), also known as Secure Monitor (Secure_Monitor.bin). It has the highest privilege mode available on the Switch’s processor, and has access to everything on the console.
+
+Exosphère will potentially play a big role in Jamais Vu and Déja Vu, which are upcoming software exploits for the Switch, allowing one to launch Atmosphère on a Fusée-Gélee patched (ipatched) Switch console, and will also enable one to launch into CFW directly from the Switch itself without the use of any sort of external device, such as a computer or RCM jig, provided they are on a low enough system firmware.
+
+## TrustZone/Secure Monitor
+TrustZone is responsible for all the cryptographic operations on the Switch. The idea behind the way it operates is that all the keys stay in the TrustZone, and userspace only gets "handles" to them. This would make sure that keydata never leaks and is kept secure. It also has a few more responsibilities, such as power management, providing a source of random numbers, and providing access to various pieces of information that are stored in the fuses.
 
 ## Extensions
-exosphère expands the original Secure Monitor design by providing custom SMCs (Secure Monitor Calls) necessary to the homebrew ecosystem. Currently, these are:
-```
-uint32_t smc_ams_iram_copy(smc_args_t *args);
-uint32_t smc_ams_write_address(smc_args_t *args);
-uint32_t smc_ams_get_emummc_config(smc_args_t *args);
-```
-
-Additionally, exosphère expands the functionality of two SMCs provided by the Horizon OS for getting/setting configuration items. The following custom configuration items are provided by exosphère:
-```
-CONFIGITEM_EXOSPHERE_VERSION = 65000,
-CONFIGITEM_NEEDS_REBOOT = 65001,
-CONFIGITEM_NEEDS_SHUTDOWN = 65002,
-CONFIGITEM_EXOSPHERE_VERHASH = 65003,
-CONFIGITEM_HAS_RCM_BUG_PATCH = 65004,
-CONFIGITEM_SHOULD_BLANK_PRODINFO = 65005,
-CONFIGITEM_ALLOW_CAL_WRITES = 65006,
-```
-
-### smc_ams_iram_copy
-This function implements a copy of up to one page between DRAM and IRAM. Its arguments are:
-```
-args->X[1] = DRAM address (translated by kernel), must be 4-byte aligned.
-args->X[2] = IRAM address, must be 4-byte aligned.
-args->X[3] = Size (must be <= 0x1000 and 4-byte aligned).
-args->X[4] = 0 for read, 1 for write.
-```
-
-### smc_ams_write_address
-This function implements a write to a DRAM page. Its arguments are:
-```
-args->X[1] = Virtual address, must be size-bytes aligned and readable by EL0.
-args->X[2] = Value.
-args->X[3] = Size (must be 1, 2, 4, or 8).
-```
-
-### smc_ams_get_emummc_config
-This function retrieves configuration for the current [emummc](emummc.md) context. Its arguments are:
-```
-args->X[1] = MMC id, must be size-bytes aligned and readable by EL0.
-args->X[2] = Pointer to output (for paths for filebased + nintendo dir), must be at least 0x100 bytes.
-```
-
-### CONFIGITEM_EXOSPHERE_VERSION
-This custom configuration item gets information about the current exosphere version.
-
-### CONFIGITEM_NEEDS_REBOOT
-This custom configuration item is used to issue a system reboot into RCM or into a warmboot payload leveraging a secondary vulnerability to achieve code execution from warm booting.
-
-### CONFIGITEM_NEEDS_SHUTDOWN
-This custom configuration item is used to issue a system shutdown with a warmboot payload leveraging a secondary vulnerability to achieve code execution from warm booting.
-
-### CONFIGITEM_EXOSPHERE_VERHASH
-This custom configuration item gets information about the current exosphere git commit hash.
-
-### CONFIGITEM_HAS_RCM_BUG_PATCH
-This custom configuration item gets whether the unit has the CVE-2018-6242 vulnerability patched.
-
-### CONFIGITEM_SHOULD_BLANK_PRODINFO
-This custom configuration item gets whether the unit should simulate a "blanked" PRODINFO. See [here](../features/configurations.md) for more information.
-
-### CONFIGITEM_ALLOW_CAL_WRITES
-This custom configuration item gets whether the unit should allow writing to the calibration partition.
-
-## lp0fw
-This is a small, built-in payload that is responsible for waking up the system during a warm boot.
-
-## sc7fw
-This is a small, built-in payload that is responsible for putting the system to sleep during a warm boot.
-
-## rebootstub
-This is a small, built-in payload that provides functionality to reboot the system into any payload of choice.
+Exosphère currently only contains one extension, an SMC allowing homebrew to find which version of Atmosphère is currently running, in order to find out what extensions are allowed to be used.

docs/components/fusee.md

@@ -1,8 +0,0 @@
-# fusée
-fusée is a custom bootloader used to start the Atmosphère environment.
-
-## fusée
-fusée is the first piece of Atmosphère's code that runs on the hardware.
-It is distributed as a standalone payload designed to be launched via RCM by abusing the CVE-2018-6242 vulnerability.
-
-This payload is responsible for all the low-level hardware initialization required by the Nintendo Switch, setting up the cryptosystem, mounting/emulating the eMMC, injecting/patching system modules, and launching the exosphère component.

docs/components/fusee/BCT.md

@@ -0,0 +1,73 @@
+# BCT.ini
+BCT.ini is the configuration file used by fusée-primary and fusée-secondary. It is read by fusee-primary.bin to setup and boot fusee-secondary.bin and is also read by fusee-secondary.bin to configure Exosphère, specify the environment it should boot, or configure other miscellaneous options such as setting a custom boot splashscreen.
+
+## Configuration
+This file is located in the `atmosphere` folder on your SD card. The default configuration file will look similar to this.
+```
+BCT0
+[stage1]
+stage2_path = atmosphere/fusee-secondary.bin
+stage2_addr = 0xF0000000
+stage2_entrypoint = 0xF0000000
+
+[exosphere]
+; Note: Disabling debugmode will cause parts of ams.tma to not work, in the future.
+debugmode = 1 
+debugmode_user = 0
+
+[stratosphere]
+; To force-enable nogc, add nogc = 1
+; To force-disable nogc, add nogc = 0
+```
+
+## Adding a Custom Boot Splashscreen
+Add the following lines to BCT.ini and change the value of `custom_splash` to the actual path and filename of your boot splashscreen.
+```
+[stage2]
+custom_splash = /path/to/your/bootlogo.bmp
+```
+
+The boot splashscreen must be a BMP file, it must be 720x1280 (1280x720 rotated 90 degrees left/counterclockwise/anti-clockwise) resolution, and be in 32-bit ARGB format. You can use image editing software such as GIMP or Photoshop to export the image in this format.
+
+## Configuring "nogc" Protection
+Nogc is a feature provided by fusée-secondary which disables the Nintendo Switch's Game Card reader. Its purpose is to prevent the reader from being updated when the console has been updated without burning fuses from a firmware lower than 4.0.0, to a newer firmware that is at least 4.0.0 or higher. By default, Atmosphère will protect the Game Card reader automatically, but you are free to change it.
+
+To change its functionality, add the following line to the `stratosphere` section and change the value of `X` according to the following list.
+```
+nogc = X
+```
+```
+1 = force-enable nogc, so Atmosphère will always disable the Game Card reader.
+0 = force-disable nogc, so Atmosphère will always enable the Game Card reader.
+```
+
+
+## Changing Target Firmware
+Add the following line to the `exosphere` section and replace the `X` according to the following list if you have trouble booting past the firmware version detection.
+`target_firmware` is the OFW major version. 
+```
+target_firmware = X
+```
+```
+1.0.0 = 1
+2.X.X = 2
+3.X.X = 3
+4.X.X = 4
+5.X.X = 5
+6.X.X = 6
+6.2.0 = 7
+7.X.X = 8
+```
+
+Note that 6.X.X indicates 6.0.0 through 6.1.0.
+
+## Configuring Debugging Modes
+By default, Atmosphère signals to the Horizon kernel that debugging is enabled while leaving usermode debugging disabled, since this can cause undesirable side-effects. If you wish to change these behaviours, go to the `exosphere` section and change the value of `X` according to the following list.
+```
+debugmode = X
+debugmode_user = X
+```
+```
+1 = enable
+0 = disable
+```

docs/components/fusee/fusee.md

@@ -0,0 +1,20 @@
+# Fusée
+Fusée (not to be confused with Fusée Gelée) is a custom bootloader needed to start Atmosphère and replaces Nintendo's Package1loader/bootloader. It currently utilizes the [Tegra X1 RCM Vulnerability](https://nvidia.custhelp.com/app/answers/detail/a_id/4660/~/security-notice%3A-nvidia-tegra-rcm-vulnerability) in order to function.
+
+Fusée is split into two separate parts: fusée-primary and fusée-secondary. This is due to the RCM Vulnerability only allowing payloads of a limited filesize to be sent to the device.
+
+As of June 2018, there are new Switch systems being sold that prevent Fusée (or any payload that requires the Fusée Gelée exploit) from working due to having an ipatched bootrom. All ipatched systems share the HAC-S-JXE-C3 product code. While Fusée cannot work on these ipatched units, they still come on firmware 4.1.0, which is vulnerable to the upcoming Déja Vu software exploit. Note that if you update past 4.1.0 on one of these ipatched units, your odds of being able to install Atmosphère or run any homebrew become practically non-existent.
+
+Additionally, a hardware revision of the Switch known as “Mariko” is believed to be in development. No such units have been seen in stores yet, but it is expected Nintendo will roll them out silently. The Mariko units will most likely patch the bootrom vulnerability Fusée Gelée, which is currently used to access CFW, and will likely have their own proprietary bootloader.
+
+## Fusée-Primary
+Fusée-primary is the payload file (fusee-primary.bin) sent to the Switch from an external device. Once sent, fusée-primary makes initial preparations before loading fusée-secondary from the Switch’s SD Card.
+
+Fusée-primary can be configured via the [BCT.ini](../fusee/BCT.md) file located on the Switch’s SD card.
+
+## Fusée-Secondary
+Fusée-secondary is a payload file that stays on the root of the Switch’s SD Card (fusee-secondary.bin). It is automatically launched once fusée-primary has finished, and is responsible for preparing the Switch’s hardware for future running environments, such as the homebrew menu. Fusée-secondary is also responsible for validating and launching Exosphère.
+
+Fusée-secondary contains various [.kip modules](/docs/main.md#modules). These modules modify existing features in the OS, and can also add new ones.
+
+Fusée is also capable of chainloading other payloads such as Linux.

docs/components/fusee/sept.md

@@ -0,0 +1,15 @@
+# sept
+Sept is a payload that facilitates booting Atmosphère when targeting firmware version 7.0.0+.
+
+It consists of a primary and a secondary payload.
+
+## Sept-Primary
+Sept-primary is essentially a stand-in for Nintendo's package1ldr, on 7.0.0+. To use it, the caller (normally Fusée-secondary) loads the sept-primary binary to `0x4003F000`,
+loads the 7.0.0+ TSEC firmware to `0x40010F00`, and loads a signed, encrypted payload to `0x40016FE0`.
+
+This signed, encrypted payload is normally Sept-secondary.
+
+## Sept-Secondary
+Sept-secondary is a payload that performs 7.0.0+ key derivation, and then chainloads to `sept/payload.bin`.
+
+It is normally stored encrypted/signed; if one wishes to build sept-secondary instead of using release builds, one must bring his/her own keys.

docs/components/libraries.md

@@ -1,11 +0,0 @@
-# libraries
-This is a collection of libraries for doing operating system development for the Nintendo Switch.
-
-## libmesosphere
-libmesosphere is a work-in-progress C++ library implementing functionality for the Horizon Kernel.
-
-## libstratosphere
-libstratosphere is a work-in-progress C++ library for development of system modules for the Nintendo Switch.
-
-## libvapours
-Common boilerplate code for various purposes. 

docs/components/mesosphere.md

@@ -1,3 +0,0 @@
-# mesosphère
-mesosphère is a work in progress customized kernel reimplementation.
-The Horizon OS's kernel follows microkernel design principles and runs at the EL1 level. It is currently subdivided into a loader (kernel_ldr) and the main kernel code.

docs/components/modules/ams_mitm.md

@@ -1,40 +0,0 @@
-# ams_mitm
-This module provides methods to intercept services provided by other system modules. It is further sub-divided according to the service it targets.
-
-## bpc_mitm
-bpc_mitm enables intercepting requests to power control services. It currently intercepts:
-+ `am` system module (to intercept the Reboot/Power buttons in the overlay menu)
-+ `fatal` system module (to simplify payload reboot logic significantly)
-+ [nx-hbloader](https://github.com/switchbrew/nx-hbloader) (to allow homebrew to take advantage of the feature)
-
-## fs_mitm
-fs_mitm enables intercepting file system operations. It can deny, delay, replace, or redirect any request made to the file system. It enables LayeredFS to function, which allows for replacement of game assets.
-
-## hid_mitm
-hid_mitm enables intercepting requests to controller device services. It is currently disabled by default. If enabled, it intercepts:
-+ [nx-hbloader](https://github.com/switchbrew/nx-hbloader) (to help homebrew not need to be recompiled due to a breaking change introduced in the past)
-
-Note that hid_mitm is currently deprecated and might be removed entirely in the future.
-
-## ns_mitm
-ns_mitm enables intercepting requests to application control services. It currently intercepts:
-+ Web Applets (to facilitate nx-hbloader web browser launching)
-
-## set_mitm
-set_mitm enables intercepting requests to the system settings service. It currently intercepts:
-+ `ns` system module and games (to allow for overriding game locales)
-+ All firmware debug settings requests (to allow modification of system settings not directly exposed to the user)
-
-### Firmware Version
-set_mitm intercepts the `GetFirmwareVersion` command, if the requester is `qlaunch` or `maintenance`.
-It modifies the `display_version` field of the returned system version, causing the version to display
-in settings as `#.#.#|AMS #.#.#|?` with `? = S` when running under system eMMC or `? = E` when running under emulated eMMC. This allows users to easily verify what version of Atmosphère and what eMMC environment they are running.
-
-### System Settings
-set_mitm intercepts the `GetSettingsItemValueSize` and `GetSettingsItemValue` commands for all requesters.
-It does so in order to enable user configuration of system settings, which are parsed from `/atmosphere/system_settings.ini` on boot. See [here](../../features/configurations.md) for more information on the system settings format.
-
-## dns_mitm
-dns_mitm enables intercepting requests to dns resolution services, to enable redirecting requests for specified hostnames.
-
-For documentation, see [here](../../features/dns_mitm.md).

docs/components/modules/boot.md

@@ -1,4 +0,0 @@
-# boot
-This module is a reimplementation of the Horizon OS's `boot` system module, which is responsible for initializing and configuring hardware.
-
-Atmosphère's reimplementation displays its own black and white splash screen and battery icons as replacements for the original assets used during display initialization.

docs/components/modules/boot2.md

@@ -1,4 +0,0 @@
-# boot2
-This module is a reimplementation of the Horizon OS's `boot2` system module, which is responsible for launching all the other necessary system modules.
-
-Atmosphère's reimplementation allows launching user provided system modules from the SD card. See [here](../../features/configurations.md) for more information.

docs/components/modules/creport.md

@@ -1,4 +0,0 @@
-# creport
-This module is a reimplementation of the Horizon OS's `creport` system module, which is responsible for managing crash reports.
-
-Atmosphère's reimplementation redirects writing of generated crash reports to the SD card under the folder `/atmosphere/crash_reports/`. It also prevents the automatic uploading of said crash reports.

docs/components/modules/dmnt.md

@@ -1,42 +0,0 @@
-# dmnt
-This module is a reimplementation of the Horizon OS's `dmnt` system module, which provides a debug monitor.
-
-## Extensions
-Atmosphère implements an extension to provide cheat code functionality.
-
-### Cheat Service
-A HIPC service API is provided for interacting with the cheat code manager through the service `dmnt:cht`. See [here](../../features/cheats.md) for more information on the cheat code format.
-
-The SwIPC definition for `dmnt:cht` follows:
-```
-interface ams::dmnt::cheat::CheatService is dmnt:cht {
-  [65000] HasCheatProcess() -> sf::Out<bool> out;
-  [65001] GetCheatProcessEvent() -> sf::OutCopyHandle out_event;
-  [65002] GetCheatProcessMetadata() -> sf::Out<CheatProcessMetadata> out_metadata;
-  [65003] ForceOpenCheatProcess();
-  [65004] PauseCheatProcess();
-  [65005] ResumeCheatProcess();
-
-  [65100] GetCheatProcessMappingCount() -> sf::Out<u64> out_count;
-  [65101] GetCheatProcessMappings(u64 offset) -> sf::OutArray<MemoryInfo> &mappings, sf::Out<u64> out_count;
-  [65102] ReadCheatProcessMemory(u64 address, u64 out_size) -> sf::OutBuffer &buffer;
-  [65103] WriteCheatProcessMemory(sf::InBuffer &buffer, u64 address, u64 in_size);
-  [65104] QueryCheatProcessMemory(u64 address) -> sf::Out<MemoryInfo> mapping;
-
-  [65200] GetCheatCount() -> sf::Out<u64> out_count;
-  [65201] GetCheats(u64 offset) -> sf::OutArray<CheatEntry> &cheats, sf::Out<u64> out_count;
-  [65202] GetCheatById(u32 cheat_id) -> sf::Out<CheatEntry> cheat;
-  [65203] ToggleCheat(u32 cheat_id);
-  [65204] AddCheat(CheatDefinition &cheat, bool enabled) -> sf::Out<u32> out_cheat_id;
-  [65205] RemoveCheat(u32 cheat_id);
-  [65206] ReadStaticRegister(u8 which) -> sf::Out<u64> out;
-  [65207] WriteStaticRegister(u8 which, u64 value);
-  [65208] ResetStaticRegisters();
-
-  [65300] GetFrozenAddressCount() -> sf::Out<u64> out_count;
-  [65301] GetFrozenAddresses(u64 offset) ->sf::OutArray<FrozenAddressEntry> &addresses, sf::Out<u64> out_count;
-  [65302] GetFrozenAddress(u64 address) -> sf::Out<FrozenAddressEntry> entry;
-  [65303] EnableFrozenAddress(u64 address, u64 width) -> sf::Out<u64> out_value;
-  [65304] DisableFrozenAddress(u64 address);
-}
-```

docs/components/modules/eclct.stub.md

@@ -1,4 +0,0 @@
-# eclct.stub
-This module is a reimplementation of the Horizon OS's `eclct` system module, which collects error reports.
-
-Atmosphère's reimplementation is a stub to remove any and all functionality pertaining to error report collection.

docs/components/modules/erpt.md

@@ -1,4 +0,0 @@
-# erpt
-This module is a reimplementation of the Horizon OS's `erpt` system module, which is responsible for managing error reports.
-
-Atmosphère's reimplementation redirects writing of generated error reports to the SD card under the folder `/atmosphere/erpt_reports/`.

docs/components/modules/fatal.md

@@ -1,4 +0,0 @@
-# fatal
-This module is a reimplementation of the Horizon OS's `fatal` system module, which is responsible for managing fatal reports.
-
-Atmosphère's reimplementation prevents error report creation and draws a custom error screen, showing registers and a backtrace. It also attempts to gather debugging info for any and all crashes and tries to save reports to the SD card under the folder `/atmosphere/fatal_reports/`.

docs/components/modules/jpegdec.md

@@ -1,4 +0,0 @@
-# jpegdec
-This module is a reimplementation of the Horizon OS's `jpegdec` system module, which is responsible for JPEG format decoding.
-
-Atmosphère's reimplementation allows two sessions instead of 1, so homebrew can use it for software JPEG decoding in addition to the OS itself.

docs/components/modules/loader.md

@@ -1,106 +0,0 @@
-# loader
-This module is a reimplementation of the Horizon OS's `ldr` system module, which is responsible for creating processes from executable NSO images and registering their access control.
-
-## Extensions
-Atmosphère extends this module to allow executables to be replaced or patched by files stored on the SD card. Note that a few services are required for SD card access and therefore cannot be replaced or patched in this manner.
-
-### Exefs Replacement
-Atmosphère's reimplementation allows replacing executable files in the file system.
-
-#### Partition Replacement
-It is possible to replace the full exefs partition at once with a PFS0 file. In that case, Atmosphère will load the following file:
-```
-/atmosphere/contents/<program id>/exefs.nsp
-```
-
-#### File Replacement
-When a process is created, loader will search for several NSO filenames in the program's exefs directory.
-These filenames are, in this order:
-  - rtld
-  - main
-  - subsdk0
-  - subsdk1
-  - ...
-  - subsdk9
-  - sdk
-
-Each NSO that is found will be loaded into the process contiguously. The process's entrypoint is at the first NSO to be loaded, usually `rtld` or `main`.
-
-Additionally, when a process is loaded, loader will search for a `main.npdm` file in the exefs directory specifying the program's permissions.
-
-Atmosphère extends this functionality by also searching for these files on the SD card. When searching for a file, loader will first check if it exists on the SD card. If it does, that file will be used instead. Otherwise, it will use the copy located in the exefs, if that is present. The following directory will be searched:
-```
-/atmosphere/contents/<program id>/exefs/
-```
-
-This allows the replacement of applets, system modules, or even games with homebrew versions.
-
-##### File Stubbing
-In order to prevent an NSO from being loaded even if it exists in the exefs, loader will also check if a stub file exists. If such a file exists, the NSO will not be loaded. The files should be named like `rtld.stub`, `main.stub`, etc. and may be empty.
-
-##### Technical Semantics
-
-loader's semantics for content override can (as you may observe from reading the above) be complicated to understand. The following is an abbreviated description of the very technical semantics by which loader decides what content to read when trying to read a file for a program id.
-
-* If an external content filesystem exists for the program id, the external content filesystem is used directly with no further redirection.
-* Otherwise, if the program ID is being overridden with [nx-hbloader](https://github.com/switchbrew/nx-hbloader/releases) (see Homebrew Support below), the nsp filesystem for hbl is used directly with no further redirection.
-* Otherwise, if content redirection is enabled for the program ID (controlled by a configurable button combination) and a loose file exists on the SD card, the loose file is used.
-* Otherwise, if a stub file exists, a "Not Found" error is returned.
-* Otherwise, if an SD card executable filesystem ("exefs.nsp") exists, it is used without further redirection.
-* Finally, the "real"/base code file system is used without further redirection.
-
-In addition, there are a few other technical details relevant to Atmosphere's redirection:
-* When overriding with nx-hbloader, the real code filesystem must exist. When "main.npdm" (a program capabilities descriptor file) is read, the content from the real code filesystem is read in order to determine whether an applet or an application is being overridden. This allows nx-hbloader to automatically support both applet and application environments.
-* When overriding applications, the real code filesystem must exist and contain valid content. This is required to perform accurate-to-Nintendo content verification procedures.
-* When programs are launched, both a program id and a "storage id" are specified by the launch requester. When the storage id specified is "none" (normally always invalid), Atmosphere assumes that a custom system module is attempting to be launched. This removes the aforementioned requirement on base content validity; the above procedure is still used to determine how to redirect content, however reads to the "real"/base code file system may return "Not Found" errors if the real/base code file system does not exist.
-
-### NSO Patching
-When an NSO is loaded, Atmosphère's reimplementation will search for IPS patch files on the SD card in the following locations.
-```
-/atmosphere/exefs_patches/<patchset name>/<nso build id>.ips
-```
-
-This organization allows patch sets affecting multiple NSOs to be distributed as a single directory and also allows patches from multiple patch sets to be stacked. Patches will be searched for in each patch set directory. The name of each patch file should match the hexadecimal build ID of the NSO to affect, except that trailing zero bytes may be left off. Because the NSO build ID is unique for every NSO, this means patches will only apply to the files they are meant to apply to.
-
-Patch files are accepted in either IPS format or IPS32 format.
-
-Because NSO files are compressed, patch files are not made between the original version of a compressed NSO and the modified version of such an NSO. Instead, they are made between the uncompressed version of an NSO and the modified (and still uncompressed) version of that NSO. This also means that a patch file cannot be manually applied to the compressed version of an NSO; it must be applied to the uncompressed version. Atmosphère's reimplementation will correctly apply these patches while loading the process regardless of whether the NSO it finds is compressed or not.
-
-When authoring patches, [hactool](https://github.com/SciresM/hactool) can be used to find an NSO's build ID and to uncompress NSOs. Recent versions of the [ReSwitched IDA loaders](https://github.com/reswitched/loaders) can be used to load uncompressed NSOs into IDA in such a way that you can [apply patches to the input file](https://www.hex-rays.com/products/ida/support/idadoc/1618.shtml). From there, any IPS tool can be used to create the patch between the original NSO and the patched NSO. Note that if the NSO you are patching is larger than 16 MiB, you will have to use a tool that supports IPS32.
-
-### Homebrew Support
-Atmosphère provides first class support for [nx-hbloader](https://github.com/switchbrew/nx-hbloader/releases) and [nx-hbmenu](https://github.com/switchbrew/nx-hbmenu/releases).
-
-Launching of the nx-hbloader process is controlled by configurable button inputs. See [here](../../features/configurations.md) for more detailed information.
-
-In addition, loader has extensions to enable homebrew to launch web applets. This normally requires the application launching the applet to have HTML Manual content inside an installed NCA. Atmosphère's reimplementation will automatically ensure that the commands used to check this succeed, and will redirect the relevant file system to the `/atmosphere/hbl_html/` subdirectory.
-
-### IPC Commands
-Atmosphère's reimplementation extends the HIPC loader services' API with several custom commands.
-
-The SwIPC definition for the `ldr:pm` extension commands follows:
-```
-interface ams::ldr::pm::ProcessManagerInterface is ldr:pm {
-  ...
-  [65000] AtmosphereHasLaunchedProgram(ncm::ProgramId program_id) -> sf::Out<bool> out;
-  [65001] AtmosphereGetProgramInfo(ncm::ProgramLocation &loc) -> sf::Out<ProgramInfo> out_program_info, sf::Out<cfg::OverrideStatus> out_status;
-  [65002] AtmospherePinProgram(ncm::ProgramLocation &loc, cfg::OverrideStatus &override_status) -> sf::Out<PinId> out_id;
-}
-```
-
-The SwIPC definition for the `ldr:dmnt` extension commands follows:
-```
-interface ams::ldr::dmnt::DebugMonitorInterface is ldr:dmnt {
-  ...
-  [65000] AtmosphereHasLaunchedProgram(ncm::ProgramId program_id) -> sf::Out<bool> out;
-}
-```
-
-The SwIPC definition for the `ldr:shel` extension commands follows:
-```
-interface ams::ldr::shell::ShellInterface is ldr:shel {
-  ...
-  [65000] AtmosphereRegisterExternalCode(ncm::ProgramId program_id) -> sf::OutMoveHandle out;
-  [65001] AtmosphereUnregisterExternalCode(ncm::ProgramId program_id);
-}
-```

docs/components/modules/ncm.md

@@ -1,4 +0,0 @@
-# ncm
-This module is a reimplementation of the Horizon OS's `ncm` system module, which is responsible for content management.
-
-Atmosphère's reimplementation is currently opt-in only. See [here](../../features/configurations.md) for more information.

docs/components/modules/pgl.md

@@ -1,4 +0,0 @@
-# pgl
-This module is a reimplementation of the Horizon OS's `pgl` system module, which is responsible for launching programs and was introduced by firmware version `10.0.0`.
-
-Currently, Atmosphère's reimplementation doesn't backport this module's functionalities to firmware versions lower than `10.0.0`.

docs/components/modules/pm.md

@@ -1,30 +0,0 @@
-# pm
-This module is a reimplementation of the Horizon OS's `pm` system module, which is responsible for tracking running processes on the system, and managing resource limits.
-
-## Extensions
-Atmosphère extends this module with extra IPC commands and memory restriction changes.
-
-### IPC Commands
-Atmosphère's reimplementation extends the HIPC loader services' API with several custom commands.
-
-The SwIPC definition for the `pm:dmnt` extension commands follows:
-```
-interface ams::pm::dmnt::DebugMonitorServiceBase is pm:dmnt {
-  ...
-  [65000] AtmosphereGetProcessInfo(os::ProcessId process_id) -> sf::OutCopyHandle out_process_handle, sf::Out<ncm::ProgramLocation> out_loc, sf::Out<cfg::OverrideStatus> out_status;
-  [65001] AtmosphereGetCurrentLimitInfo(u32 group, u32 resource) -> sf::Out<s64> out_cur_val, sf::Out<s64> out_lim_val;
-}
-```
-
-The SwIPC definition for the `pm:info` extension commands follows:
-```
-interface ams::pm::info::InformationService is pm:info {
-  ...
-  [65000] AtmosphereGetProcessId(ncm::ProgramId program_id) -> sf::Out<os::ProcessId> out;
-  [65001] AtmosphereHasLaunchedProgram(ncm::ProgramId program_id) -> sf::Out<bool> out;
-  [65002] AtmosphereGetProcessInfo(os::ProcessId process_id) -> sf::Out<ncm::ProgramLocation> out_loc, sf::Out<cfg::OverrideStatus> out_status;
-}
-```
-
-### Extra System Memory
-Atmosphère's reimplementation shrinks the APPLET memory pool by 24 MiB by default, giving this memory to the SYSTEM pool. This allows custom system modules to use more memory without hitting the SYSTEM memory limit.

docs/components/modules/ro.md

@@ -1,16 +0,0 @@
-# ro
-This module is a reimplementation of the Horizon OS's `ro` system module, which is responsible for loading dynamic libraries and was introduced by firmware version `3.0.0`.
-
-Atmosphère's reimplementation backports this module's functionalities to firmware versions lower than `3.0.0` where said functionalities were provided by the `ldr` system module instead.
-
-## Extensions
-Atmosphère extends this module to allow libraries to be patched by files stored on the SD card.
-
-### NRO Patching
-When an NRO is loaded, Atmosphère's reimplementation will search for IPS patch files on the SD card in the following locations.
-```
-/atmosphere/nro_patches/<patchset name>/<nro build id>.ips
-```
-This organization allows patch sets affecting multiple NROs to be distributed as a single directory. Patches will be searched for in each patch set directory. The name of each patch file should match the hexadecimal build ID of the NRO to affect, except that trailing zero bytes may be left off. Because the NRO build ID is unique for every NRO, this means patches will only apply to the files they are meant to apply to.
-
-Patch files are accepted in either IPS format or IPS32 format.

docs/components/modules/sm.md

@@ -1,47 +0,0 @@
-# sm
-This module is a reimplementation of the Horizon OS's `sm` system module, which is responsible for service management.
-
-## Extensions
-Atmosphère extends this module with extra IPC commands and new services.
-
-### Debug Monitor
-Atmosphère's reimplementation provides an interface `sm:dmnt` to allow a debug monitor to query the service manager's state.
-
-The SwIPC definition for `sm:dmnt` follows:
-```
-interface ams::sm::DmntService is sm:dmnt {
-  [65000] AtmosphereGetRecord(ServiceName service) -> sf::Out<ServiceRecord> record;
-  [65001] AtmosphereListRecords(u64 offset) -> sf::OutArray<ServiceRecord> &records, sf::Out<u64> out_count;
-  [65002] AtmosphereGetRecordSize() -> sf::Out<u64> record_size;
-}
-```
-
-### IPC Commands
-Atmosphère's reimplementation extends the HIPC loader services' API with several custom commands.
-
-The SwIPC definition for the `sm:` extension commands follows:
-```
-interface ams::sm::UserService is sm: {
-  ...
-  [65000] AtmosphereInstallMitm(ServiceName service) -> sf::OutMoveHandle srv_h, sf::OutMoveHandle qry_h;
-  [65001] AtmosphereUninstallMitm(ServiceName service);
-  [65002] Deprecated_AtmosphereAssociatePidTidForMitm();
-  [65003] AtmosphereAcknowledgeMitmSession(ServiceName service) -> sf::Out<MitmProcessInfo> client_info, sf::OutMoveHandle fwd_h;
-  [65004] AtmosphereHasMitm(ServiceName service) -> sf::Out<bool> out;
-  [65005] AtmosphereWaitMitm(ServiceName service);
-  [65006] AtmosphereDeclareFutureMitm(ServiceName service);
-  
-  [65100] AtmosphereHasService(ServiceName service) -> sf::Out<bool> out;
-  [65101] AtmosphereWaitService(ServiceName service);
-}
-```
-
-The SwIPC definition for the `sm:m` extension commands follows:
-```
-interface ams::sm::ManagerService is sm:m {
-  ...
-  [65000] AtmosphereEndInitDefers(os::ProcessId process_id, sf::InBuffer &acid_sac, sf::InBuffer &aci_sac);
-  [65001] AtmosphereHasMitm(ServiceName service) -> sf::Out<bool> out;
-  [65002] AtmosphereRegisterProcess(os::ProcessId process_id, ncm::ProgramId program_id, cfg::OverrideStatus override_status, sf::InBuffer &acid_sac, sf::InBuffer &aci_sac);
-}
-```

docs/components/modules/spl.md

@@ -1,2 +0,0 @@
-# spl
-This module is a reimplementation of the Horizon OS's `spl` system module, which is responsible for providing secure platform services such as cryptographic operations.

docs/components/stratosphere.md

@@ -1,21 +1,10 @@
-# stratosphère
-stratosphère provides customization of the Horizon OS at the system level. This includes a reimplementation of several system modules and additional, custom system modules that extend or add a variety of features.
+# Stratosphère
+Stratosphère allows customization of the Horizon OS and Switch kernel. It includes custom sysmodules that extend the kernel and provide new features. It also includes a reimplementation of the loader sysmodules to hook important system actions.
 
-## Modules
-The modules currently provided by stratosphère are:
-+ [ams_mitm](modules/ams_mitm.md)
-+ [boot](modules/boot.md)
-+ [boot2](modules/boot2.md)
-+ [creport](modules/creport.md)
-+ [dmnt](modules/dmnt.md)
-+ [eclct.stub](modules/eclct.stub.md)
-+ [erpt](modules/erpt.md)
-+ [fatal](modules/fatal.md)
-+ [jpegdec](modules/jpegdec.md)
-+ [loader](modules/loader.md)
-+ [ncm](modules/ncm.md)
-+ [pgl](modules/pgl.md)
-+ [pm](modules/pm.md)
-+ [ro](modules/ro.md)
-+ [sm](modules/sm.md)
-+ [spl](modules/spl.md)
+The sysmodules that Stratosphère includes are:
++ [boot](../modules/boot.md): This module boots the system and initalizes hardware.
++ [creport](../modules/creport.md): Reimplementation of Nintendo’s crash report system. Dumps all error logs to the SD card instead of saving them to the NAND and sending them to Nintendo.
++ [fs_mitm](../modules/fs_mitm.md): This module can log, deny, delay, replace, and redirect any request made to the File System.
++ [loader](../modules/loader.md): Enables modifying the code of binaries that are not stored inside the kernel.
++ [pm](../modules/pm.md): Reimplementation of Nintendo’s Process Manager.
++ [sm](../modules/sm.md): Reimplementation of Nintendo’s Service Manager.

docs/components/thermosphere.md

@@ -1,3 +1,4 @@
-# thermosphère
-thermosphère is a work in progress hypervisor implementation.
-This aims to provide functionality at the EL2 level which remains unused by the Horizon OS.
+# Thermosphère
+Thermosphère is a hypervisor based implementation of emuNAND.
+
+Thermosphère is currently planned to be included in a future release of Atmosphère.

docs/components/troposphere.md

@@ -1,5 +1,2 @@
-# troposphère
-troposphère provides customization of the Horizon OS at the application level.
-
-## reboot_to_payload
-Sample application to perform a system reboot into a payload of choice.
+# Troposphère
+Troposphère contains various application-level modifications to the OS, such as launching homebrew directly from the homemenu or executing cheat/gameshark codes, similar to Luma3DS. Troposphère is not yet implemented in Atmosphère.

docs/faq.md

@@ -1,18 +0,0 @@
-# Frequently Asked Questions
-
-This document serves as a place to store answers for common questions received about Atmosphère.
-
-## What does "June 15th" mean?
-When Atmosphère began development in February 2018, "June 15" was given as the estimate/target date for a first release, to coincide with the planned disclosure of a vulnerability.
-
-This deadline was missed, hard.
-
-People made rather a lot of fun of me (SciresM) for this.
-
-Several months later, when the first Atmosphère release occurred, I captioned it "Happy June 15th!" and pretended like I hadn't missed the first deadline.
-
-This amused me a lot, and so the practice has been kept up for every single release since.
-
-Depending on who you ask, you may be told that this is a dumb joke and it is not funny.
-
-This is incorrect. It is definitely a dumb joke, but it is also hilarious.

docs/features/cheats.md

@@ -1,512 +0,0 @@
-# Cheats
-Atmosphère supports Action-Replay style cheat codes, with cheats loaded off of the SD card.
-
-## Cheat Loading Process
-By default, Atmosphère will do the following when deciding whether to attach to a new application process:
-
-+ Retrieve information about the new application process from `pm` and `loader`.
-+ Check whether a user-defined key combination is held, and stop if not.
-  + This defaults to "L is not held", but can be configured with override keys.
-  + The ini key to configure this is `cheat_enable_key`.
-+ Check whether the process is a real application, and stop if not.
-  + This guards against applying cheat codes to the Homebrew Loader.
-+ Attempt to load cheats from `/atmosphere/contents/<program_id>/cheats/<build_id>.txt`, where `build_id` is the hexadecimal representation of the first 8 bytes of the application's main executable's build id.
-  + If no cheats are found, then the cheat manager will stop.
-+ Open a kernel debug session for the new application process.
-+ Signal to a system event that a new cheat process has been attached to.
-
-This behavior ensures that cheat codes are only loaded when the user would want them to.
-
-In cases where `dmnt` has not activated the cheat manager, but the user wants to make it do so anyway, the cheat manager's service API provides a `ForceOpenCheatProcess` command that homebrew can use. This command will cause the cheat manager to try to force itself to attach to the process.
-
-In cases where `dmnt` has activated the cheat manager, but the user wants to use an alternate debugger, the cheat manager's service API provides a `ForceCloseCheatProcess` command that homebrew can use. This command will cause the cheat manager to detach itself from the process.
-
-By default, all cheat codes listed in the loaded .txt file will be toggled on. This is configurable by the user by editing the `atmosphere!dmnt_cheats_enabled_by_default` [system setting](configurations.md).
-
-Users may use homebrew programs to toggle cheats on and off at runtime via the cheat manager's service API.
-
-## Cheat Code Compatibility
-Atmosphère manages cheat code through the execution of a small, custom virtual machine. Care has been taken to ensure that Atmosphère's cheat code format is fully backwards compatible with the pre-existing cheat code format, though new features have been added and bugs in the pre-existing cheat code applier have been fixed. Here is a short summary of the changes from the pre-existing format:
-
-+ A number of bugs were fixed in the processing of conditional instructions.
-  + The pre-existing implementation was fundamentally broken, and checked for the wrong value when detecting the end of a conditional block.
-  + The pre-existing implementation also did not properly decode instructions, and instead linearly scanned for the terminator value. This caused problems if an instruction happened to encode a terminator inside its immediate values.
-  + The pre-existing implementation did not bounds check, and thus certain conditional cheat codes could cause it to read out-of-bounds memory, and potentially crash due to a data abort.
-+ Support was added for nesting conditional blocks.
-+ An instruction was added to perform much more complex arbitrary arithmetic on two registers.
-+ An instruction was added to allow writing the contents of register to a memory address specified by another register.
-+ The pre-existing implementation did not correctly synchronize with the application process, and thus would cause heavy lag under certain circumstances (especially around loading screens). This has been fixed in Atmosphère's implementation.
-
-## Cheat Code Format
-The following provides documentation of the instruction format for the virtual machine used to manage cheat codes.
-
-Typically, instruction type is encoded in the upper nybble of the first instruction u32.
-
-### Code Type 0x0: Store Static Value to Memory
-Code type 0x0 allows writing a static value to a memory address.
-
-#### Encoding
-`0TMR00AA AAAAAAAA VVVVVVVV (VVVVVVVV)`
-
-+ T: Width of memory write (1, 2, 4, or 8 bytes).
-+ M: Memory region to write to (0 = Main NSO, 1 = Heap, 2 = Alias, 3 = Aslr, 4 = non-relative).
-+ R: Register to use as an offset from memory region base.
-+ A: Immediate offset to use from memory region base.
-+ V: Value to write.
-
----
-
-### Code Type 0x1: Begin Conditional Block
-Code type 0x1 performs a comparison of the contents of memory to a static value.
-
-If the condition is not met, all instructions until the appropriate End or Else conditional block terminator are skipped.
-
-#### Encoding
-`1TMCXrAA AAAAAAAA VVVVVVVV (VVVVVVVV)`
-
-+ T: Width of memory read (1, 2, 4, or 8 bytes).
-+ M: Memory region to read from (0 = Main NSO, 1 = Heap, 2 = Alias, 3 = Aslr, 4 = non-relative).
-+ C: Condition to use, see below.
-+ X: Operand Type, see below.
-+ r: Offset Register (operand types 1).
-+ A: Immediate offset to use from memory region base.
-+ V: Value to compare to.
-
-#### Conditions
-+ 1: >
-+ 2: >=
-+ 3: <
-+ 4: <=
-+ 5: ==
-+ 6: !=
-
-#### Operand Type
-+ 0: Memory Base + Relative Offset
-+ 1: Memory Base + Offset Register + Relative Offset
----
-
-### Code Type 0x2: End Conditional Block
-Code type 0x2 marks the end of a conditional block (started by Code Type 0x1 or Code Type 0x8).
-
-When an Else is executed, all instructions until the appropriate End conditional block terminator are skipped.
-
-#### Encoding
-`2X000000`
-
-+ X: End type (0 = End, 1 = Else).
-
----
-
-### Code Type 0x3: Start/End Loop
-Code type 0x3 allows for iterating in a loop a fixed number of times.
-
-#### Start Loop Encoding
-`300R0000 VVVVVVVV`
-
-+ R: Register to use as loop counter.
-+ V: Number of iterations to loop.
-
-#### End Loop Encoding
-`310R0000`
-
-+ R: Register to use as loop counter.
-
----
-
-### Code Type 0x4: Load Register with Static Value
-Code type 0x4 allows setting a register to a constant value.
-
-#### Encoding
-`400R0000 VVVVVVVV VVVVVVVV`
-
-+ R: Register to use.
-+ V: Value to load.
-
----
-
-### Code Type 0x5: Load Register with Memory Value
-Code type 0x5 allows loading a value from memory into a register, either using a fixed address or by dereferencing the destination register.
-
-#### Load From Fixed Address Encoding
-`5TMR00AA AAAAAAAA`
-
-+ T: Width of memory read (1, 2, 4, or 8 bytes).
-+ M: Memory region to write to (0 = Main NSO, 1 = Heap, 2 = Alias, 3 = Aslr, 4 = non-relative).
-+ R: Register to load value into.
-+ A: Immediate offset to use from memory region base.
-
-#### Load from Register Address Encoding
-`5T0R10AA AAAAAAAA`
-
-+ T: Width of memory read (1, 2, 4, or 8 bytes).
-+ R: Register to load value into. (This register is also used as the base memory address).
-+ A: Immediate offset to use from register R.
-
-#### Load from Register Address Encoding
-`5T0R2SAA AAAAAAAA`
-
-+ T: Width of memory read (1, 2, 4, or 8 bytes).
-+ R: Register to load value into. 
-+ S: Register to use as the base memory address.
-+ A: Immediate offset to use from register R.
-
-#### Load From Fixed Address Encoding with offset register
-`5TMR3SAA AAAAAAAA`
-
-+ T: Width of memory read (1, 2, 4, or 8 bytes).
-+ M: Memory region to write to (0 = Main NSO, 1 = Heap, 2 = Alias, 3 = Aslr, 4 = non-relative).
-+ R: Register to load value into.
-+ S: Register to use as offset register.
-+ A: Immediate offset to use from memory region base.
----
-
-### Code Type 0x6: Store Static Value to Register Memory Address
-Code type 0x6 allows writing a fixed value to a memory address specified by a register.
-
-#### Encoding
-`6T0RIor0 VVVVVVVV VVVVVVVV`
-
-+ T: Width of memory write (1, 2, 4, or 8 bytes).
-+ R: Register used as base memory address.
-+ I: Increment register flag (0 = do not increment R, 1 = increment R by T).
-+ o: Offset register enable flag (0 = do not add r to address, 1 = add r to address).
-+ r: Register used as offset when o is 1.
-+ V: Value to write to memory.
-
----
-
-### Code Type 0x7: Legacy Arithmetic
-Code type 0x7 allows performing arithmetic on registers.
-
-However, it has been deprecated by Code type 0x9, and is only kept for backwards compatibility.
-
-#### Encoding
-`7T0RC000 VVVVVVVV`
-
-+ T: Width of arithmetic operation (1, 2, 4, or 8 bytes).
-+ R: Register to apply arithmetic to.
-+ C: Arithmetic operation to apply, see below.
-+ V: Value to use for arithmetic operation.
-
-#### Arithmetic Types
-+ 0: Addition
-+ 1: Subtraction
-+ 2: Multiplication
-+ 3: Left Shift
-+ 4: Right Shift
-
----
-
-### Code Type 0x8: Begin Keypress Conditional Block
-Code type 0x8 enters or skips a conditional block based on whether a key combination is pressed.
-
-#### Encoding
-`8kkkkkkk`
-
-+ k: Keypad mask to check against, see below.
-
-Note that for multiple button combinations, the bitmasks should be ORd together.
-
-#### Keypad Values
-Note: This is the direct output of `hidKeysDown()`.
-
-+ 0000001: A
-+ 0000002: B
-+ 0000004: X
-+ 0000008: Y
-+ 0000010: Left Stick Pressed
-+ 0000020: Right Stick Pressed
-+ 0000040: L
-+ 0000080: R
-+ 0000100: ZL
-+ 0000200: ZR
-+ 0000400: Plus
-+ 0000800: Minus
-+ 0001000: Left
-+ 0002000: Up
-+ 0004000: Right
-+ 0008000: Down
-+ 0010000: Left Stick Left
-+ 0020000: Left Stick Up
-+ 0040000: Left Stick Right
-+ 0080000: Left Stick Down
-+ 0100000: Right Stick Left
-+ 0200000: Right Stick Up
-+ 0400000: Right Stick Right
-+ 0800000: Right Stick Down
-+ 1000000: SL
-+ 2000000: SR
-
----
-
-### Code Type 0x9: Perform Arithmetic
-Code type 0x9 allows performing arithmetic on registers.
-
-#### Register Arithmetic Encoding
-`9TCRS0s0`
-
-+ T: Width of arithmetic operation (1, 2, 4, or 8 bytes).
-+ C: Arithmetic operation to apply, see below.
-+ R: Register to store result in.
-+ S: Register to use as left-hand operand.
-+ s: Register to use as right-hand operand.
-
-#### Immediate Value Arithmetic Encoding
-`9TCRS100 VVVVVVVV (VVVVVVVV)`
-
-+ T: Width of arithmetic operation (1, 2, 4, or 8 bytes).
-+ C: Arithmetic operation to apply, see below.
-+ R: Register to store result in.
-+ S: Register to use as left-hand operand.
-+ V: Value to use as right-hand operand.
-
-#### Arithmetic Types
-+ 0: Addition
-+ 1: Subtraction
-+ 2: Multiplication
-+ 3: Left Shift
-+ 4: Right Shift
-+ 5: Logical And
-+ 6: Logical Or
-+ 7: Logical Not (discards right-hand operand)
-+ 8: Logical Xor
-+ 9: None/Move (discards right-hand operand)
-+ 10: Float Addition, T==4 single T==8 double
-+ 11: Float Subtraction, T==4 single T==8 double
-+ 12: Float Multiplication, T==4 single T==8 double
-+ 13: Float Division, T==4 single T==8 double
----
-
-### Code Type 0xA: Store Register to Memory Address
-Code type 0xA allows writing a register to memory.
-
-#### Encoding
-`ATSRIOxa (aaaaaaaa)`
-
-+ T: Width of memory write (1, 2, 4, or 8 bytes).
-+ S: Register to write to memory.
-+ R: Register to use as base address.
-+ I: Increment register flag (0 = do not increment R, 1 = increment R by T).
-+ O: Offset type, see below.
-+ x: Register used as offset when O is 1, Memory type when O is 3, 4 or 5.
-+ a: Value used as offset when O is 2, 4 or 5.
-
-#### Offset Types
-+ 0: No Offset
-+ 1: Use Offset Register
-+ 2: Use Fixed Offset
-+ 3: Memory Region + Base Register
-+ 4: Memory Region + Relative Address (ignore address register)
-+ 5: Memory Region + Relative Address + Offset Register
-
----
-
-### Code Type 0xB: Reserved
-Code Type 0xB is currently reserved for future use.
-
----
-
-### Code Type 0xC-0xF: Extended-Width Instruction
-Code Types 0xC-0xF signal to the VM to treat the upper two nybbles of the first dword as instruction type, instead of just the upper nybble.
-
-This reserves an additional 64 opcodes for future use.
-
----
-
-### Code Type 0xC0: Begin Register Conditional Block
-Code type 0xC0 performs a comparison of the contents of a register and another value. This code support multiple operand types, see below.
-
-If the condition is not met, all instructions until the appropriate conditional block terminator are skipped.
-
-#### Encoding
-```
-C0TcSX##
-C0TcS0Ma aaaaaaaa
-C0TcS1Mr
-C0TcS2Ra aaaaaaaa
-C0TcS3Rr
-C0TcS400 VVVVVVVV (VVVVVVVV)
-C0TcS5X0
-```
-
-+ T: Width of memory write (1, 2, 4, or 8 bytes).
-+ c: Condition to use, see below.
-+ S: Source Register.
-+ X: Operand Type, see below.
-+ M: Memory Type (operand types 0 and 1).
-+ R: Address Register (operand types 2 and 3).
-+ a: Relative Address (operand types 0 and 2).
-+ r: Offset Register (operand types 1 and 3).
-+ X: Other Register (operand type 5).
-+ V: Value to compare to (operand type 4).
-
-#### Operand Type
-+ 0: Memory Base + Relative Offset
-+ 1: Memory Base + Offset Register
-+ 2: Register + Relative Offset
-+ 3: Register + Offset Register
-+ 4: Static Value
-+ 5: Other Register
-
-#### Conditions
-+ 1: >
-+ 2: >=
-+ 3: <
-+ 4: <=
-+ 5: ==
-+ 6: !=
-
----
-
-### Code Type 0xC1: Save or Restore Register
-Code type 0xC1 performs saving or restoring of registers.
-
-#### Encoding
-`C10D0Sx0`
-
-+ D: Destination index.
-+ S: Source index.
-+ x: Operand Type, see below.
-
-#### Operand Type
-+ 0: Restore register
-+ 1: Save register
-+ 2: Clear saved value
-+ 3: Clear register
-
----
-
-### Code Type 0xC2: Save or Restore Register with Mask
-Code type 0xC2 performs saving or restoring of multiple registers using a bitmask.
-
-#### Encoding
-`C2x0XXXX`
-
-+ x: Operand Type, see below.
-+ X: 16-bit bitmask, bit i == save or restore register i.
-
-#### Operand Type
-+ 0: Restore register
-+ 1: Save register
-+ 2: Clear saved value
-+ 3: Clear register
-
----
-
-### Code Type 0xC3: Read or Write Static Register
-Code type 0xC3 reads or writes a static register with a given register.
-
-#### Encoding
-`C3000XXx`
-
-+ XX: Static register index, 0x00 to 0x7F for reading or 0x80 to 0xFF for writing.
-+ x: Register index.
-
----
-
-### Code Type 0xC4: Begin Extended Keypress Conditional Block
-Code type 0xC4 enters or skips a conditional block based on whether a key combination is pressed.
-
-#### Encoding
-`C4r00000 kkkkkkkk kkkkkkkk`
-
-+ r: Auto-repeat, see below.
-+ kkkkkkkkkk: Keypad mask to check against output of `hidKeysDown()`.
-
-Note that for multiple button combinations, the bitmasks should be OR'd together.
-
-#### Auto-repeat
-
-+ 0: The conditional block executes only once when the keypad mask matches. The mask must stop matching to reset for the next trigger.
-+ 1: The conditional block executes as long as the keypad mask matches.
-
-#### Keypad Values
-Note: This is the direct output of `hidKeysDown()`.
-
-+ 00000000 00000001: A
-+ 00000000 00000002: B
-+ 00000000 00000004: X
-+ 00000000 00000008: Y
-+ 00000000 00000010: Left Stick Pressed
-+ 00000000 00000020: Right Stick Pressed
-+ 00000000 00000040: L
-+ 00000000 00000080: R
-+ 00000000 00000100: ZL
-+ 00000000 00000200: ZR
-+ 00000000 00000400: Plus
-+ 00000000 00000800: Minus
-+ 00000000 00001000: Left
-+ 00000000 00002000: Up
-+ 00000000 00004000: Right
-+ 00000000 00008000: Down
-+ 00000000 00010000: Left Stick Left
-+ 00000000 00020000: Left Stick Up
-+ 00000000 00040000: Left Stick Right
-+ 00000000 00080000: Left Stick Down
-+ 00000000 00100000: Right Stick Left
-+ 00000000 00200000: Right Stick Up
-+ 00000000 00400000: Right Stick Right
-+ 00000000 00800000: Right Stick Down
-+ 00000000 01000000: SL Left Joy-Con
-+ 00000000 02000000: SR Left Joy-Con
-+ 00000000 04000000: SL Right Joy-Con
-+ 00000000 08000000: SR Right Joy-Con
-+ 00000000 10000000: Top button on Poké Ball Plus (Palma) controller
-+ 00000000 20000000: Verification
-+ 00000000 40000000: B button on Left NES/HVC controller in Handheld mode
-+ 00000000 80000000: Left C button in N64 controller
-+ 00000001 00000000: Up C button in N64 controller
-+ 00000002 00000000: Right C button in N64 controller
-+ 00000004 00000000: Down C button in N64 controller
-
-### Code Type 0xF0: Double Extended-Width Instruction
-Code Type 0xF0 signals to the VM to treat the upper three nybbles of the first dword as instruction type, instead of just the upper nybble.
-
-This reserves an additional 16 opcodes for future use.
-
----
-
-### Code Type 0xFF0: Pause Process
-Code type 0xFF0 pauses the current process.
-
-#### Encoding
-`FF0?????`
-
----
-
-### Code Type 0xFF1: Resume Process
-Code type 0xFF1 resumes the current process.
-
-#### Encoding
-`FF1?????`
-
----
-
-### Code Type 0xFFF: Debug Log
-Code type 0xFFF writes a debug log to the SD card under the folder `/atmosphere/cheat_vm_logs/`.
-
-#### Encoding
-```
-FFFTIX##
-FFFTI0Ma aaaaaaaa
-FFFTI1Mr
-FFFTI2Ra aaaaaaaa
-FFFTI3Rr
-FFFTI4X0
-```
-
-+ T: Width of memory write (1, 2, 4, or 8 bytes).
-+ I: Log id.
-+ X: Operand Type, see below.
-+ M: Memory Type (operand types 0 and 1).
-+ R: Address Register (operand types 2 and 3).
-+ a: Relative Address (operand types 0 and 2).
-+ r: Offset Register (operand types 1 and 3).
-+ X: Value Register (operand type 4).
-
-#### Operand Type
-+ 0: Memory Base + Relative Offset
-+ 1: Memory Base + Offset Register
-+ 2: Register + Relative Offset
-+ 3: Register + Offset Register
-+ 4: Register Value

docs/features/configurations.md

@@ -1,125 +0,0 @@
-# Configurations
-Atmosphère provides a variety of customizable configurations to better adjust to users' needs.
-
-## stratosphere.ini
-This is the configuration file used by fusée for configuring user-space system modules.
-This file is located under the `/atmosphere/config/` folder on your SD card and a default template can be found inside the `/atmosphere/config_templates/` folder.
-
-### Configuring "nogc" Protection
-"nogc" is a feature provided by fusée-secondary which disables the Nintendo Switch's Game Card reader. Its purpose is to prevent the reader from being updated when the console has been updated, without burning fuses, from a lower firmware version. More specifically, from firmware versions 4.0.0 or 9.0.0 which introduced updates to the Game Card reader's firmware. By default, Atmosphère will protect the Game Card reader automatically, but you are free to change it.
-
-To change its functionality, add the following line to the `stratosphere` section and change the value of `X` according to the following list:
-```
-[stratosphere]
-nogc = X
-```
-```
-1 = force-enable nogc, so Atmosphère will always disable the Game Card reader.
-0 = force-disable nogc, so Atmosphère will always enable the Game Card reader.
-```
-
-## Adding a Custom Boot Splashscreen
-Atmosphère provides its own default splashscreen which is displayed at boot time. However, this can be replaced at will.
-
-Boot splash screens must be 1280x720 resolution.
-
-A script can be found inside the source tree (`/utilities/insert_splash_screen.py`) for inserting a custom splash screen into a release binary.
-
-To do so, execute the following command on the script:
-`python insert_splash_screen.py <path to your splash screen image> <path to /atmosphere/package3 on your SD card>`
-
-## emummc.ini
-This is the configuration file used for the [emummc](../components/emummc.md) component.
-This file is located under the `/emuMMC/` folder on your SD card.
-
-Please refer to the project's repository [here](https://github.com/m4xw/emuMMC) for detailed instructions and documentation.
-
-## exosphere.ini
-This is the configuration file used by exosphère.
-This file is located in the root of your SD card and a default template can be found inside the `/atmosphere/config_templates/` folder.
-
-### Configuring Debugging Modes
-By default, Atmosphère signals to the Horizon kernel that debugging is enabled while leaving usermode debugging disabled, but this can cause undesirable side-effects. If you wish to change this behavior, go to the `exosphere` section and change the value of `X` according to the following list.
-```
-[exosphere]
-debugmode = X
-debugmode_user = X
-```
-```
-1 = enable
-0 = disable
-```
-
-### Blanking PRODINFO
-Atmosphère provides a way for users to blank their factory installed calibration data (known as PRODINFO) in either emulated or system eMMC environments. You can find more detailed information on this inside the respective template file. Usage of this configuration is not encouraged.
-
-## override_config.ini
-This file is located under the `/atmosphere/config/` folder on your SD card and a default template can be found inside the `/atmosphere/config_templates/` folder.
-
-### Overrides Format
-Overrides are parsed from the `/atmosphere/config/override_config.ini` file during the boot process.
-
-By default `override_config.ini` is not configured. It can be used to select the behavior of certain buttons and bind them to functionalities such as launching the Homebrew Menu or enabling the cheat code manager.
-
-You can modify the override_key entries in `override_config.ini` with this list of valid buttons:
-| Formal Name | .ini Name |
-| ----------- | --------- |
-| A Button    | A         |
-| B Button    | B         |
-| X Button    | X         |
-| Y Button    | Y         |
-| Left Stick  | LS        |
-| Right Stick | RS        |
-| L Button    | L         |
-| R Button    | R         |
-| ZL Button   | ZL        |
-| ZR Button   | ZR        |
-| + Button    | PLUS      |
-| - Button    | MINUS     |
-| Left Dpad   | DLEFT     |
-| Up Dpad     | DUP       |
-| Right Dpad  | DRIGHT    |
-| Down Dpad   | DDOWN     |
-| SL Button   | SL        |
-| SR Button   | SR        |
-
-To invert the behavior of the override key, place an exclamation point in front of whatever button you wish to use. It will launch the actual game while holding down that button, instead of going into the Homebrew Menu. For example, `override_key=!R` will run the game only while holding down R when launching it, otherwise it will boot into the Homebrew Menu. Afterwards you may reinsert your SD card into your Switch and boot into Atmosphère as you normally would. You should now be able to boot into the Homebrew Menu by launching your designated program of choice.
-
-## system_settings.ini
-This file is located under the `/atmosphere/config/` folder on your SD card and a default template can be found inside the `/atmosphere/config_templates/` folder.
-
-### Settings Format
-Atmosphère provides a way to override the firmware debug settings used by the system. These can be parsed from the `/atmosphere/config/system_settings.ini` file during the boot process. This file is a normal ini file, with some specific interpretations.
-
-The standard representation of a setting's identifier takes the form `name!key`. This is represented within `system_settings.ini` as a section `name`, with an entry `key`. For example:
-```
-[name]
-key = ...
-```
-
-Settings can have variable types (strings, integral values, byte arrays, etc). To accommodate this, `system_settings.ini` must store values as a `type_identifier!value_store` pair. A number of different types are supported, with identifiers detailed below.
-Please note that a malformed value string will cause a fatal error to occur on boot. A full example of a custom setting is given below (setting `eupld!upload_enabled = 0`), for posterity:
-```
-[eupld]
-upload_enabled = u8!0x0
-```
-
-#### Supported Types
-* Strings
-    * Type identifiers: `str`, `string`
-    * The value string is used directly as the setting, with null terminator appended.
-* Integral types
-    * Type identifiers: `u8`, `u16`, `u32`, `u64`
-    * The value string is parsed via a call to `strtoul(value, NULL, 0)`.
-    * Setting bitwidth is determined by the identifier (8 for 1 byte, 16 for 2 bytes, and so on).
-* Raw bytes
-    * Type identifiers: `hex`, `bytes`
-    * The value string is parsed as a hexadecimal string.
-        * The value string must be of even length, or a fatal error will be thrown on parse.
-
-## Content Specific Flags
-Atmosphère supports customizing CFW behavior based on the presence of `flags` on the SD card.
-
-The following flags are supported on a per-program basis, by placing `<flag_name>.flag` inside `/atmosphere/contents/<program_id>/flags/`:
-+ `boot2`, which indicates that the program should be launched during the `boot2` process.
-+ `redirect_save`, which indicates that the program wants its savedata to be redirected to the SD card.

docs/features/dns_mitm.md

@@ -1,53 +0,0 @@
-# DNS.mitm
-As of 0.18.0, atmosphère provides a mechanism for redirecting DNS resolution requests.
-
-By default, atmosphère redirects resolution requests for official telemetry servers, redirecting them to a loopback address.
-
-## Hosts files
-
-DNS.mitm can be configured through the usage of a slightly-extended `hosts` file format, which is parsed only once on system startup.
-
-In particular, hosts files parsed by DNS.mitm have the following extensions to the usual format:
-+ `*` is treated as a wildcard character, matching any collection of 0 or more characters wherever it occurs in a hostname.
-+ `%` is treated as a stand-in for the value of `nsd!environment_identifier`. This is always `lp1`, on production devices.
-
-If multiple entries in a host file match a domain, the last-defined match is used.
-
-Please note that homebrew may trigger a hosts file re-parse by sending the extension IPC command 65000 ("AtmosphereReloadHostsFile") to a connected `sfdnsres` session.
-
-### Hosts file selection
-
-Atmosphère will try to read hosts from the following file paths, in order, stopping once it successfully performs a file read:
-
-+ (emummc only) `/atmosphere/hosts/emummc_%04lx.txt`, formatted with the emummc's id number (see `emummc.ini`).
-+ (emummc only) `/atmosphere/hosts/emummc.txt`.
-+ (sysmmc only) `/atmosphere/hosts/sysmmc.txt`.
-+ `/atmosphere/hosts/default.txt`
-
-If `/atmosphere/hosts/default.txt` does not exist, atmosphère will create it to contain the defaults.
-
-### Atmosphère defaults
-
-By default, atmosphère's default redirections are parsed **in addition to** the contents of the loaded hosts file.
-
-This is equivalent to thinking of the loaded hosts file as having the atmosphère defaults prepended to it.
-
-This setting is considered desirable, because it minimizes the telemetry risks if a user forgets to update a custom hosts file on a system update which changes the telemetry servers.
-
-This behavior can be opted-out from by setting `atmosphere!add_defaults_to_dns_hosts = u8!0x0` in `system_settings.ini`.
-
-The current default redirections are:
-
-```
-# Nintendo telemetry servers
-127.0.0.1 receive-%.dg.srv.nintendo.net receive-%.er.srv.nintendo.net
-```
-
-## Debugging
-
-On startup (or on hosts file re-parse), DNS.mitm will log both what hosts file it selected and the contents of all redirections it parses to `/atmosphere/logs/dns_mitm_startup.log`.
-
-In addition, if the user sets `atmosphere!enable_dns_mitm_debug_log = u8!0x1` in `system_settings.ini`, DNS.mitm will log all requests to GetHostByName/GetAddrInfo to `/atmosphere/logs/dns_mitm_debug.log`. All redirections will be noted when they occur.
-
-## Opting-out of DNS.mitm entirely
-If you wish to disable DNS.mitm entirely, `system_settings.ini` can be edited to set `atmosphere!enable_dns_mitm = u8!0x0`.

docs/flags.md

@@ -0,0 +1,12 @@
+# Flags
+Atmosphère supports customizing CFW behavior based on the presence of `flags` on the SD card.
+
+The following flags are supported on a per-title basis, by placing `<flag_name>.flag` inside `/atmosphere/titles/<title_id>/flags/`:
++ `boot2`, which indicates to PM that the title should be launched during the `boot2` process.
++ `fsmitm`, which indicates that `fs.mitm` should override contents for the title even if it otherwise wouldn't.
++ `fsmitm_disable`, which indicates that `fs.mitm` should not override contents for the title, even it it otherwise would.
++ `bis_write`, which indicates that `fs.mitm` should allow the title to write to BIS partitions.
++ `cal_read`, which indicates that `fs.mitm` should allow the title to read the CAL0/PRODINFO partition.
+
+The following global flags are supported, by placing `<flag name>.flag` inside `/atmosphere/flags/`:
++ `hbl_bis_write` and `hbl_cal_read` enable the BIS write and CAL0 read functionality for HBL, without needing to specify its title id.

docs/licensing_exemptions/MIT_LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) Atmosphère-NX
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

docs/main.md

@@ -1,32 +1,29 @@
 # Atmosphère
-Atmosphère is a work-in-progress customized firmware for the Nintendo Switch. Its design principle consists of a multi-layered approach where each layer replaces/modifies a different component of the Nintendo Switch's system.
+Atmosphère is a work-in-progress customized firmware for the Nintendo Switch. Atmosphère consists of several different components, each in charge of performing different system functions of the Nintendo Switch.
 
-## Components
-Atmosphère provides six core components, mimicking to some degree the various layers of the Earth's atmosphere:
-+ [fusée](components/fusee.md)
-+ [exosphère](components/exosphere.md)
-+ [thermosphère](components/thermosphere.md)
-+ [mesosphère](components/mesosphere.md)
-+ [stratosphère](components/stratosphere.md)
-+ [troposphère](components/troposphere.md)
+The components of Atmosphère are:
++ [Fusée](../docs/components/fusee/fusee.md), a custom bootloader.
++ [Exosphère](../docs/components/exosphere.md), a fully-featured custom secure monitor.
++ [Stratosphère](../docs/components/stratosphere.md), a set of custom system modules.
++ [Thermosphère](../docs/components/thermosphere.md), a hypervisor-based emuNAND implementation. This component has not been implemented yet.
++ [Troposphère](../docs/components/troposphere.md), Application-level patches to the Horizon OS. This component has also not been implemented yet.
 
-Additionally, Atmosphère also provides the following secondary components:
-+ [emummc](components/emummc.md)
-+ [libraries](components/libraries.md)
+### Modules
+The Stratosphère component of Atmosphère contains various modules. These have a `.kip` extension. They provide custom features, extend existing features, or replace Nintendo sysmodules.
 
-## Features
-Atmosphère provides several original features which add or expand functionalities for the customized firmware environment:
-+ [Cheats](features/cheats.md)
-+ [Configurations](features/configurations.md)
+Stratosphère's modules include:
++ [boot](../docs/modules/boot.md)
++ [creport](../docs/modules/creport.md)
++ [fs_mitm](../docs/modules/fs_mitm.md)
++ [loader](../docs/modules/loader.md)
++ [pm](../docs/modules/pm.md)
++ [sm](../docs/modules/sm.md)
 
-## Building Atmosphère
-A guide to building Atmosphère can be found [here](building.md).
+### Building Atmosphère
+A guide to building Atmosphère can be found [here](../docs/building.md).
 
-## Upcoming Features
-A list of planned features for Atmosphère can be found [here](roadmap.md).
+### Upcoming Features
+A list of planned features for Atmosphère can be found [here](../docs/roadmap.md).
 
-## Release History
-A changelog of previous versions of Atmosphère can be found [here](changelog.md).
-
-## Frequently Asked Questions
-Answers to one or more frequently asked questions may be found [here](faq.md).
+### Release History
+A changelog of previous versions of Atmosphère can be found [here](../docs/changelog.md).

docs/modules/boot.md

@@ -0,0 +1,2 @@
+# boot
+The boot module is responsible for booting the system and initalizing hardware. A second boot module known as boot2 is integrated with the [pm (process manager)](../modules/pm.md) sysmodule in Atmosphère, and launches other processes.

docs/modules/creport.md

@@ -0,0 +1,2 @@
+# creport
+creport is a reimplementation of Nintendo's crash reporter. Atmosphère's creport catches all error logs that would have been saved to the NAND and instead saves them to the SD card for debugging purposes. This is helpful because the errors no longer go to Nintendo and developers of homebrew can still see the errors to help with the debugging process. creport catches system errors, game crashes, and homebrew crashes.

docs/modules/dmnt.md

@@ -0,0 +1,38 @@
+# dmnt
+
+dmnt is a reimplementation of Nintendo's debug monitor. It provides Atmosphère a rich set of debugging functionality, so that users can easily analyze the behaviors of programs. In addition, Atmosphère implements an extension in dmnt to provide cheat code functionality.
+
+## Atmosphère Cheat Extension
+
+In addition to the functionality provided by Nintendo's debug monitor, Atmosphère's dmnt has an extension for providing cheat code functionality. A HIPC Service API is provided for interacting with the cheat code manager, through the service `dmnt:cht`.
+
+Those looking for more information on the cheat code functionality may wish to read `cheats.md`.
+
+The SwIPC definition for `dmnt:cht` follows.
+```
+interface DmntCheatService is dmnt:cht {
+  [65000] HasCheatProcess() -> bool;
+  [65001] GetCheatProcessEvent() -> KObject;
+  [65002] GetCheatProcessMetadata() -> CheatProcessMetadata;
+  [65003] ForceOpenCheatProcess();
+
+  [65100] GetCheatProcessMappingCount() -> u64;
+  [65101] GetCheatProcessMappings(u64 offset) -> buffer<MemoryInfo, 6>, u64 count;
+  [65102] ReadCheatProcessMemory(u64 address, u64 size) -> buffer<u8, 6> data;
+  [65103] WriteCheatProcessMemory(u64 address, u64 size, buffer<u8, 5> data);
+  [65104] QueryCheatProcessMemory(u64 address) -> MemoryInfo;
+
+  [65200] GetCheatCount() -> u64;
+  [65201] GetCheats(u64 offset) -> buffer<CheatEntry, 6>, u64 count;
+  [65202] GetCheatById(u32 cheat_id) -> buffer<CheatEntry, 6> cheat;
+  [65203] ToggleCheat(u32 cheat_id);
+  [65204] AddCheat(buffer<CheatDefinition, 5> cheat, bool enabled) -> u32 cheat_id;
+  [65203] RemoveCheat(u32 cheat_id);
+
+  [65300] GetFrozenAddressCount() -> u64;
+  [65301] GetFrozenAddresses(u64 offset) -> buffer<FrozenAddressEntry, 6>, u64 count;
+  [65302] GetFrozenAddress(u64 address) -> FrozenAddressEntry;
+  [65303] EnableFrozenAddress(u64 address, u64 width) -> u64 value;
+  [65304] DisableFrozenAddress(u64 address);
+}
+```

docs/modules/fs_mitm.md

@@ -0,0 +1,2 @@
+# fs_mitm
+fs_mitm is a sysmodule that enables intercepting file system operations. This module can log, deny, delay, replace, or redirect any request made to the filesystem. It enables LayeredFS to function, which allows for replacement of game assets.

docs/modules/loader.md

@@ -0,0 +1,126 @@
+# loader
+
+loader is a reimplementation of the loader sysmodule. This module is responsible for creating processes from executable NSO images and registering their access control with the kernel, sm, and fs.
+
+## Atmosphère Extensions
+
+Atmosphère extends this module to allow executables to be replaced or patched by files stored on the SD card. Note that a few services are required for SD card access and therefore cannot be replaced or patched in this manner. This includes psc, bus, and pcv.
+
+### Exefs Replacement
+
+TODO: details on buttons affecting this.
+
+When a process is created, loader will search for several NSO filenames in the title's exefs directory.
+These filenames are, in this order:
+
+  - rtld
+  - main
+  - subsdk0
+  - subsdk1
+  - ...
+  - subsdk9
+  - sdk
+
+Each NSO that is found will be loaded into the process contiguously. The process's entrypoint is at the first NSO to be loaded, usually `rtld` or `main`.
+
+Additionally, when a process is loaded, loader will search for a `main.npdm` file in the exefs directory specifying the title's permissions.
+
+Atmosphère extends this functionality by also searching for these files on the SD card. When searching for a file, loader will first check if it exists on the SD card. If it does, that file will be used instead. Otherwise, it will use the copy located in the exefs, if that is present. The following directory will be searched.
+
+```
+sdmc:/atmosphere/titles/<title id>/exefs/
+```
+
+This allows the replacement of applets, sysmodules, or even games with homebrew versions.
+
+In order to prevent an NSO from being loaded even if it exists in the exefs, loader will also check if a stub file exists. If such a file exists, the NSO will not be loaded. The files should be named like `rtld.stub`, `main.stub`, etc. and may be empty.
+
+### NSO Patching
+
+TODO: details on buttons affecting this.
+
+When an NSO is loaded, the stratosphere implementatin of loader will search for IPS patch files on the SD card in the following locations.
+```
+sdmc:/atmosphere/exefs_patches/<patchset name>/<nso build id>.ips
+```
+This organization allows patchsets affecting multiple NSOs to be distributed as a single directory. Patches will be searched for in each patchset directory. The name of each patch file should match the hexadecimal build ID of the NSO to affect, except that trailing zero bytes may be left off. Because the NSO build ID is unique for every NSO, this means patches will only apply to the files they are meant to apply to.
+
+Patch files are accepted in either IPS format or IPS32 format.
+
+Because NSO files are compressed, patch files are not made between the original version of a compressed NSO and the modified version of such an NSO. Instead, they are made between the uncompressed version of an NSO and the modified (and still uncompressed) version of that NSO. This also means that a patch file cannot be manually applied to the compressed version of an NSO; it must be applied to the uncompressed version. The Stratosphere implementation of loader will correctly apply these patches while loading the process regardless of whether the NSO it finds is compressed or not.
+
+When authoring patches, [hactool](https://github.com/SciresM/hactool) can be used to find an NSO's build ID and to uncompress NSOs. Recent versions of the [ReSwitched IDA loaders](https://github.com/reswitched/loaders) can be used to load uncompressed NSOs into IDA in such a way that you can [apply patches to the input file](https://www.hex-rays.com/products/ida/support/idadoc/1618.shtml). From there, any IPS tool can be used to create the patch between the original NSO and the patched NSO. Note that if the NSO you are patching is larger than 16 MiB, you will have to use a tool that supports IPS32.
+
+### HBL Support
+
+Atmosphère can use the loader module in order to turn any game on your Switch's home menu into a launchpoint for the Homebrew Menu, rather than launching it through the album applet. This allows one to launch the Homebrew Menu with access to the ~3.2GB of RAM that the Switch reserves for games and applications, as opposed to the 442MB of RAM we are limited to when launching the Homebrew Menu from the album. This also means that it is no longer necessary to install homebrew as `.nsp` files on your Switch so long as you are using this method, as the only reason to do so is to allow the homebrew to access all of the Switch's available memory.
+
+In order to setup this method you will need the latest release of [hbmenu](https://github.com/switchbrew/nx-hbmenu/releases), and the latest release of [hbloader](https://github.com/switchbrew/nx-hbloader/releases). Place `hbmenu.nro` on the root of your Switch's SD Card, and place `hbl.nsp` in the atmosphere folder. From there, simply launch any title while holding the button specified in `loader.ini`.
+
+In addition, loader has extensions to enable homebrew to launch web applets. This normally requires the application launching the applet have HTML Manual content inside an installed NCA; Atmosphère's loader will automatically ensure that the commands used to check this succeed, and will (in tandem with `fs.mitm`) redirect the relevant filesystem to the `sdmc:/atmosphere/hbl_html/` subdirectory.
+
+### Button Overrides
+
+By default `loader.ini` is configured to launch the Homebrew Menu when launching any game while holding down the override key (defaults to R). If you wish to change this, you can modify the override_key section of `loader.ini`. Alternatively, if you would like to only allow hbmenu on a specific app, configure `loader.ini` in the atmosphere folder by replacing the Title ID in the ini (title_id in the [hbl_config] section, it is the Title ID for the album by default) with the Title ID of whatever game you wish to use to launch the Homebrew Menu, and set override_any_app to false. A list of Title IDs for Switch Games can be found [here](https://switchbrew.org/wiki/Title_list/Games).
+
+To invert the behaviour of the override key, place an exclamation point in front of whatever button you wish to use. It will launch the actual game while holding down that button, instead of going into the Homebrew Menu. For example, `override_key=!R` will run the game only while holding down R when launching it, otherwise it will boot into the Homebrew Menu. Afterwards you may reinsert your SD Card into your Switch and boot into Atmosphère as you normally would. You should now be able to boot into the Homebrew Menu by launching your designated title of choice.
+
+A list of valid buttons can be found here:
+
+| Formal Name | .ini Name |
+| ----------- | --------- |
+| A Button    | A         |
+| B Button    | B         |
+| X Button    | X         |
+| Y Button    | Y         |
+| Left Stick  | LS        |
+| Right Stick | RS        |
+| L Button    | L         |
+| R Button    | R         |
+| ZL Button   | ZL        |
+| ZR Button   | ZR        |
+| + Button    | PLUS      |
+| - Button    | MINUS     |
+| Left Dpad   | DLEFT     |
+| Up Dpad     | DUP       |
+| Right Dpad  | DRIGHT    |
+| Down Dpad   | DDOWN     |
+| SL Button   | SL        |
+| SR Button   | SR        |
+
+### SM MITM Integration
+
+When the Stratosphere implementation of loader creates a new process, it notifies [sm](sm.md) through the `AtmosphereAssociatePidTidForMitm` command to notify any MITM services of new processes' identities.
+
+### IPC: AtmosphereSetExternalContentSource and AtmosphereClearExternalContentSource
+
+Two additional commands are added to the [`ldr:shel`](https://reswitched.github.io/SwIPC/ifaces.html#nn::ro::detail::ILdrShellInterface) interface, called `AtmosphereSetExternalContentSource` and `AtmosphereClearExternalContentSource`.
+Their command IDs are `65000` and `65001` on all system firmware versions.
+
+`AtmosphereSetExternalContentSource` takes a `u64 tid` and returns a server-side session handle.
+The client is expected to implement the `IFileSystem` interface on the returned handle. The next
+time the title specified by the given title ID is launched, its ExeFS contents will be loaded from
+the custom `IFileSystem` instead of from SD card or original ExeFS. NSOs loaded from external
+content source may still be subject to exefs IPS patches. After the title is launched successfuly,
+the `IFileSystem` is closed and the external content source override is removed. If
+`AtmosphereSetExternalContentSource` is called on a title that already has an external content
+source set for it, the existing one will be removed and replaced with the new one. It is illegal to
+call `AtmosphereSetExternalContentSource` while the title is being launched.
+
+If title launching fails, the external content source remains registered. The
+`AtmosphereClearExternalContentSource` command can be used to clear an external content source if
+title launch fails.
+
+The `IFileSystem` only needs to implement `OpenFile` and `GetFileTimeStampRaw`. The paths received
+by the `IFileSystem`'s `OpenFile` command begin with slashes, as in `/main`, `/rtld`, and `/main.npdm`.
+A result code of 0x202 should be returned if the file does not exist. `GetFileTimeStampRaw` can just
+be a stub. The `IFile`s returned from `OpenFile` only need to implement `Read` and `GetSize`.
+
+The SwIPC definitions for the extension commands follow.
+```
+interface nn::ldr::detail::IShellInterface is ldr:shel {
+  ...
+  [65000] AtmosphereSetExternalContentSource(u64 tid) -> handle<copy, session_server> ifilesystem_handle;
+  [65001] AtmosphereClearExternalContentSource(u64 tid);
+}
+```

docs/modules/pm.md

@@ -0,0 +1,23 @@
+# pm
+
+pm is a reimplementation of Nintendo's process manager. This module is responsible for tracking running processes on the system, and managing resource limits. pm is also required to create and manage processes for homebrew applications.
+
+## Atmosphère Extensions
+
+There are a few ways in which the Stratosphere implementation of pm differs intentionally from the stock pm.
+
+### IPC: AtmosphereGetProcessHandle
+
+The Stratosphere implementation of pm adds an additional command to the [`pm:dmnt`](https://reswitched.github.io/SwIPC/ifaces.html#nn::pm::detail::IDebugMonitorInterface) interface, called `AtmosphereGetProcessHandle`. Its command ID is `65000` on all system firmware versions. It takes a `u64 process_id` and returns a process handle for the specified process, if that process is known. Notable exceptions include KIPs, which are not known to pm. If the specified process cannot be found, error code 0x20F is returned.
+
+The SwIPC definition for this command follows.
+```
+interface nn::pm::detail::IDebugMonitorInterface is pm:dmnt {
+  ...
+  [65000] AtmosphereGetProcessInfo(u64 pid) -> handle<copy, process> process_handle, u64 title_id, u64 storage_id;
+}
+```
+
+### Extra System Memory for Sysmodules
+
+The Stratosphere implementation of pm shrinks the APPLET memory pool by 24 MiB by default, giving this memory to the SYSTEM pool. This allows custom sysmodules to use more memory without hitting the SYSTEM memory limit.

docs/modules/set_mitm.md

@@ -0,0 +1,79 @@
+# set_mitm
+set_mitm is a sysmodule that enables intercepting requests to the system settings service.
+
+## Atmosphère Extensions
+
+set_mitm intercepts the `GetFirmwareVersion` command, if the requester is `qlaunch` or `maintenance`.\
+It modifies the `display_version` field of the returned system version, causing the version to display\
+in settings as `#.#.# (AMS #.#.#)`. This allows users to easily verify what version of Atmosphère they are running.
+
+set_mitm also intercepts the `GetSettingsItemValueSize` and `GetSettingsItemValue` commands for all requesters.\
+It does so in order to enable user configuration of system settings, which are parsed from `atmosphere/system_settings.ini` on boot.\
+The format for settings is described below.
+
+### Atmosphère Settings Format
+
+Settings are parsed from the `atmosphere/system_settings.ini` file during the boot process. This file is a normal ini file,\
+with some specific interpretations.
+
+The standard representation of a system setting's identifier takes the form `name!key`. This is represented within\
+`system_settings.ini` as a section `name`, with an entry `key`. For example:
+
+```
+[name]
+key = ...
+```
+
+System settings can have variable types (strings, integral values, byte arrays, etc). To accommodate this, `system_settings.ini`\
+must store values as a `type_identifier!value_store` pair. A number of different types are supported, with identifiers detailed below.\
+Please note that a malformed value string will cause a fatal error to occur on boot. A full example of a custom setting is given below\
+(setting `eupld!upload_enabled = 0`), for posterity:
+
+```
+[eupld]
+upload_enabled = u8!0x0
+```
+
+### Supported Types
+
+* Strings
+    * Type identifiers: `str`, `string`
+    * The value string is used directly as the setting, with null terminator appended.
+* Integral types
+    * Type identifiers: `u8`, `u16`, `u32`, `u64`
+    * The value string is parsed via a call to `strtoul(value, NULL, 0)`.
+    * Setting bitwidth is determined by the identifier (8 for 1 byte, 16 for 2 bytes, and so on).
+* Raw bytes
+    * Type identifiers: `hex`, `bytes`
+    * The value string is parsed as a hexadecimal string.
+        * The value string must be of even length, or a fatal error will be thrown on parse.
+
+### Atmosphère Custom Settings
+
+At the time of writing, Atmosphère implements two custom settings, found in the `atmosphere` section.\
+
+While not used for set_mitm, `power_menu_reboot_function` is loaded and controls the reboot behaviour of the console. By default, this value\
+is "payload", where the console will automatically reboot into the RCM payload stored in `sdmc:/atmosphere/reboot_payload.bin`.\
+(This payload is also used for fatal, upon a serious crash.) Setting the value to "rcm" reboots directly into RCM, and setting the value\
+to "normal" skips these behaviours.
+
+```
+[atmosphere]
+power_menu_reboot_function = str!payload
+```
+
+`dmnt_cheats_enabled_by_default` controls the behaviour of dmnt's cheat functionality. By default, this value is "0x1", enabling any cheats\
+defined by the user. Check [cheats](../cheats.md) for more information about Atmosphère's cheat functionality.
+
+```
+[atmosphere]
+dmnt_cheats_enabled_by_default = u8!0x1
+```
+
+`dmnt_always_save_cheat_toggles` controls the behaviour of dmnt's cheat toggle functionality. By default, this value is "0x0", causing toggles to\
+only be saved on game quit if a toggle file existed on game boot. Check [cheats](../cheats.md) for more information about Atmosphère's cheat functionality.
+
+```
+[atmosphere]
+dmnt_always_save_cheat_toggles = u8!0x0
+```

docs/modules/sm.md

@@ -0,0 +1,125 @@
+# sm
+
+sm is a reimplementation of Nintendo's service manager. It allows Atmosphère to add or remove process handle limits, add new services, or intercept service calls. This allows high-level intercepting of Horizon OS functionality.
+
+## Atmosphère Extensions
+
+There are a few ways in which the Stratosphere implementation of sm differs intentionally from the stock sm.
+
+### IPC: MITM Commands
+
+The Stratosphere implementation of sm adds a few additional commands to the [`sm:`](https://reswitched.github.io/SwIPC/ifaces.html#nn::sm::detail::IUserInterface) port session.
+
+Their SwIPC definitions follow.
+```
+interface nn::sm::detail::IUserInterface is sm: {
+  ...
+  [65000] AtmosphereInstallMitm(ServiceName service) -> handle<port, move> service, handle<server_session, move> query;
+  [65001] AtmosphereUninstallMitm(ServiceName service);
+  [65002] AtmosphereAssociatePidTidForMitm(u64 pid, u64 tid);
+}
+```
+
+Additionally, an interface `sm:dmnt` has been created to allow a debug monitor to query sm's state.
+
+Its SwIPC definition follows.
+```
+interface nn::sm::detail::IDebugMonitorInterface is sm:dmnt {
+  [65000] AtmosphereGetServiceRecord(ServiceName name) -> SmServiceRecord;
+  [65001] AtmosphereListServiceRecords(u64 offset) -> buffer<SmServiceRecord, 6>, u64 count;
+  [65002] AtmosphereGetServiceRecordSize() -> u64 record_size;
+}
+```
+
+
+#### AtmosphereInstallMitm
+
+This command alters the registration for the named service, in order to allow services to intercept communication between client processes and their intended services. It is used by [fs_mitm](fs_mitm.md).
+
+It takes the name of the service to install an MITM for, and returns two handles. The first is a port handle, similar to those returned from the [RegisterService](https://reswitched.github.io/SwIPC/ifaces.html#nn::sm::detail::IUserInterface(2)) command. The second is the server side of a session, called the query session. This session will used by sm to determine whether or not a new session should be intercepted, and to inform the MITM service of the identity of new processes.
+
+The query session is expected to implement the following interface.
+```
+interface MitmQueryService {
+  [65000] ShouldMitm(u64 pid) -> u64 should_mitm;
+  [65001] AssociatePidTid(u64 pid, u64 tid);
+}
+```
+
+The `ShouldMitm` command is invoked whenever a process attempts to make a new connection to the MITM'd service. It should return `0` if the process's connection should not be intercepted. Any other value will cause the process's connection to be intercepted. If the command returns an error code, the process's connection will not be intercepted.
+
+The `AssociatePidTid` command is invoked on all MITM query sessions whenever a new process is created, in order to inform those services of the identity of a newly created process before it attempts to connect to any services.
+
+If the process that installed the MITM attempts to connect to the service, it will always connect to the original service.
+
+This command requires that the session be initialized, returning error code 0x415 if it is not.\
+If the given service name is invalid, error code 0xC15 is returned.\
+If the user does not have service registration permission for the named service, error code 0x1015 is returned.\
+If the service already has an MITM installed, error code 0x815 is returned.\
+If the service has not yet been registered, the request will be deferred until the service is registered in the same manner as IUserInterface::GetService.
+
+#### AtmosphereUninstallMitm
+
+Removes any installed MITM for the named service.
+
+This command requires that the session be initialized, returning error code 0x415 if it is not.
+
+#### AtmosphereAssociatePidTidForMitm
+
+This command is used internally by the Stratosphere implementation of the [loader](loader.md) sysmodule, when a new process is created. It will call the `AssociatePidTid` command on every registered MITM query session.
+
+If the given process ID refers to a kernel internal process, error code 0x1015 is returned. This command requires that the session be initialized, returning error code 0x415 if it is not.
+
+#### AtmosphereGetServiceRecordSize
+
+Retrieves `sizeof(SmServiceRecord)` for a service. The current format of `SmServiceRecord` structure follows.
+
+```
+struct SmServiceRecord {
+    uint64_t service_name;
+    uint64_t owner_pid;
+    uint64_t max_sessions;
+    uint64_t mitm_pid;
+    uint64_t mitm_waiting_ack_pid;
+    bool is_light;
+    bool mitm_waiting_ack;
+};
+```
+
+#### AtmosphereGetServiceRecord
+
+Retrieves a service registration record for a service.
+
+#### AtmosphereListServiceRecords
+
+Provides a list of service registrations records.
+
+The command will return an array of `SmServiceRecord`s, skipping `offset` records. The number of records returned is indicated by `count`.
+If `count` is less than the size of the buffer divided by `sizeof(SmServiceRecord)` (the buffer was not completely filled), the end of the service registration list has been reached. Otherwise, client code
+should increment `offset` by `count` and call again. Client code should retrieve a record size using `AtmosphereGetServiceRecordSize`, and either make sure that the size of a record matches what it expects,
+or should make sure to use the correct size as the stride while iterating over the array of returned records. Example pseudocode is shown below.
+
+```
+offset = 0;
+record_size = AtmosphereGetServiceRecordSize();
+do {
+    SmServiceRecord records[16];
+    count = AtmosphereListServiceRecords(offset, buffer(records));
+    for (i = 0; i < count; i++) {
+        SmServiceRecord record = {0};
+        memcpy(&record, &records[i], min(record_size, sizeof(SmServiceRecord));
+        /* process record */
+        offset++;
+    }
+} while(count == sizeof(records) / record_size);
+```
+
+### Minimum Session Limit
+
+When a service is registered, the sysmodule registering it must specify a limit on the number of sessions that are allowed to be active for that service at a time. This is used to ensure that services like `fs-pr`, `fs-ldr`, and `ldr:pm` can only be connected to once, adding an additional layer of safety over the regular service verification to ensure that those services are only connected to by the highly priveleged process they are intended to be used by.
+
+By default, the Stratosphere implementation of PM will raise any session limits to at least 8, meaning that for services like `fs-pr` and those mentioned above, up to 8 processes will be able to connect to those sessions, leaving 7 sessions for homebrew to use.
+
+### Weak Service Verification
+
+In system firmware versions before 3.0.1, if a process did not call the [Initialize](https://reswitched.github.io/SwIPC/ifaces.html#nn::sm::detail::IUserInterface(0)) command on its `sm:` session, normally used to inform sm of the process's identity, sm would assume that the process was a kernel internal process and skip any service registration or access checks. The Stratosphere implementation of sm does not implement this vulnerability, and initialization is required on all firmware versions.

docs/roadmap.md

@@ -1,60 +1,16 @@
 # Planned Features
-atmosphère has a number of features that are either works-in-progress or planned. Please note that while time-estimates are given, they are loose, and things may be completed sooner or later than advertised.
-
-The following descriptions were last updated on January 14th, 2021
-
-## tma reimplementation
-* **Description** tma ("target manager agent") is a system module that manages communication between the Switch and a client PC. Atmosphere's implementation will allow homebrew on the switch to communicate with a connected PC to do various operations such as exchanging data or interacting with files. It will also serve as the communicator for Atmosphère's planned debugger. This will also include PC-side software for interacting with the Switch.
-* **Development Status**: Planned. Switch-side code is fully implemented but needs heavy refactoring/rebasing, as the code was originally authored in 2018.
-* **Estimated Time**: 2021-2022.
-
-## dmnt.gen2 reimplementation
-* **Description**: A reimplementation of the Switch's debug monitor, dmnt will provide an interface for debugging applications or system modules running on the Switch. This will include a gdbstub for debugging actively-running system components or applications.
-* **Development Status**: Planned
-* **Estimated Time**: 2021-2022
-
-## fs reimplementation
-* **Description**: Following mesosphère's completion, atmosphère will have reimplemented all components of the BootImagePackage firmware except for the filesystem services system module. Reimplementing fs will allow for fixing Nintendo bugs (such as corruption when using exFAT filesystems and encoding inconsistencies with UTF-8 and Shift-JIS).
-* **Development Status**: Planned.
-* **Estimated Time**: 2021-2022.
-
-## settings reimplementation
-* **Description**: A planned reimplementation of the settings system module, and with it a removal of the settings mitm. This will greatly simplify atmosphère's boot process, and will allow much more flexible control over the various system settings.
-* **Development Status**: Pending development by Adubbz.
-* **Estimated Time**: Unclear, pending developer availability.
-
-## thermosphère
-* **Description**: A general-purpose hypervisor, thermosphère will enable the virtualization of the Switch's operating system; this is planned to enable debugging of the Switch's kernel.
-* **Development Status**: Pending development by TuxSH.
-* **Estimated Time**: Unclear, pending developer availability.
-
-## other planned features
-* **Description**: General system stability improvements to enhance the user's experience.
-* **Development Status**: Undergoing active development by all members of the atmosphère team.
-* **Estimated Time**: June 15th.
-
-# Completed features
-
-The following features were previously included under the planned features section and are now complete.
-
-Please note that this is not an exhaustive list of features present in atmosphère, and only serves to indicate what from the above has been completed.
-
-## system updater homebrew
-* **Description**: A user homebrew making use of the new system updater api, so that users can actually use the new api in practice.
-* **Completion Time**: July 2020
-
-## system updater api
-* **Description**: A planned extension api for stratosphere (tenatively `ams:su`), this will provide an interface for homebrew to safely install system upgrades or downgrades. This will allow for much more easily transitioning safely between different versions of the operating system.
-* **Completion Time**: June 2020
-
-## exosphere re-write
-* **Description**: exosphère, atmosphère's reimplementation of Horizon's Secure Monitor, was the first component authored for the project in early 2018. It is written in C, and in a style very different from the rest of atmosphère's code. In addition, exosphère was written to conform to constraints that no longer apply in an environment where it is not launched from the web browser, and where using a custom firmware image to orchestrate wake-from-sleep is possible. exosphère currently uses all but 1 KB of the space available to it, putting it at risk of breaking as future firmware updates are supported. A re-write will solve these issues.
-* **Completion Time**: June 2020
-
-## mesosphere
-* **Description**: mesosphère is a reimplementation of the Horizon operating system's Kernel. It aims to provide an open-source reference for Nintendo's code.
-* **Estimated Time**: September 2020
-
-## ams-on-mariko
-* **Description**: Atmosphere cannot run as-is on Mariko hardware. A large number of changes are needed in many components. Although secure monitor support is complete in exosphere, additional work is needed on the bootloader and stratosphere sides as well. Mariko support will also require further design thought; atmosphere's debugging design heavily relies on reboot-to-payload and (more generally) the ability to perform warmboot bootrom hax at will. This is not possible on Mariko, and will require a new design/software support for whatever solution is chosen.
-* **Completion Time**: January 2021
+The following features are planned to be added in future versions of Atmosphère:
++ Thermosphère, a hypervisor-based emunand implementation.
++ A feature-rich debugging toolset (a component of Stratosphère).
+  + A custom debug monitor system module, providing an API for debugging Switch's processes. This may not be a reimplementation of Nintendo's own debug monitor.
+    + This should include a gdbstub implementation, possibly borrowing from Luma3DS's.
+    + This API should be additionally usable for RAM Editing/"Cheat Engine" purposes.
+  + A custom shell system module, providing an means for users to perform various RPC (with support for common/interesting functionality) on their Switch remotely. This may not be a reimplementation of Nintendo's own shell.
+    + This should support client connections over both Wi-Fi and USB.
+  + A custom logging system module, providing a means for other Atmosphère components (and possibly Nintendo's own system modules) to log debug output.
+    + This should support logging to the SD card, over Wi-Fi, and over USB.
++ An application-level plugin system.
+  + This will, ideally, work somewhat like NTR-CFW's plugin system on the 3DS, allowing users to run their own code in a game's process in their own thread.
++ An AR Code/Gameshark analog implementation, allowing for easy sharing/development of cheat codes to run on device.
++ Further extensions to existing Atmosphère components.
++ General system stability improvements to enhance the user's experience.

emummc/.gitrepo

@@ -4,9 +4,9 @@
 ; git-subrepo command. See https://github.com/git-commands/git-subrepo#readme
 ;
 [subrepo]
-	remote = https://github.com/m4xw/emummc
+	remote = https://github.com/m4xw/emuMMC
 	branch = develop
-	commit = a8e5f1a184aeb8ba884166a1e4f386088d4a6cf1
-	parent = 409c3cf9e190dbb65fe76570954939cbe8a5eca0
-	method = merge
+	commit = b168ddf5fbb31013ff529a4859110c82b11eb361
+	parent = c07f54f3709a4710e0aead6c91139fa0893b5e5c
+	method = rebase
 	cmdver = 0.4.1

emummc/Makefile

@@ -21,10 +21,9 @@ include $(DEVKITPRO)/libnx/switch_rules
 
 ARCH	:=	-march=armv8-a -mtune=cortex-a57 -mtp=soft -fPIE
 
-# Current max usage is 0x4600. (512 * 34 FatFS file objects + 1 fsync buffer).
-DEFINES := -DINNER_HEAP_SIZE=0x8000
+DEFINES := -DINNER_HEAP_SIZE=0x80000
 
-CFLAGS	:=	-Wall -O2 -ffunction-sections -fdata-sections -Wno-unused-function \
+CFLAGS	:=	-Wall -O2 -ffunction-sections -Wno-unused-function \
 			$(ARCH) $(DEFINES)
 
 CFLAGS	+=	$(INCLUDE) -D__SWITCH__
@@ -32,7 +31,7 @@ CFLAGS	+=	$(INCLUDE) -D__SWITCH__
 CXXFLAGS	:= $(CFLAGS) -fno-rtti -fno-exceptions -std=gnu++17
 
 ASFLAGS	:=	-g $(ARCH)
-LDFLAGS	=	-specs=$(EMUMMCDIR)/emummc.specs -g $(ARCH) -Wl,-Map,$(notdir $*.map)
+LDFLAGS	=	-specs=$(DEVKITPRO)/libnx/switch.specs -g $(ARCH) -Wl,-Map,$(notdir $*.map)
 
 ifneq ($(BUILD),$(notdir $(CURDIR)))
 
@@ -98,10 +97,7 @@ else
 
 DEPENDS	:=	$(OFILES:.o=.d)
 
-all	:	$(OUTPUT)_unpacked.kip
-
-$(OUTPUT)_unpacked.kip	:	$(OUTPUT).kip
-	@hactool -t kip --uncompressed=$(OUTPUT)_unpacked.kip $(OUTPUT).kip
+all	:	$(OUTPUT).kip
 
 $(OUTPUT).kip	:	$(OUTPUT).elf
 

emummc/README.md

@@ -2,7 +2,7 @@
 *A SDMMC driver replacement for Nintendo's Filesystem Services, by **m4xw***  
 
 ### Supported Horizon Versions
-**1.0.0 - 20.1.0**
+**1.0.0 - 10.0.0**
 
 ## Features
 * Arbitrary SDMMC backend selection  

emummc/emummc.json

@@ -117,8 +117,6 @@
                 "svcReplyAndReceiveWithUserBuffer": "0x44",
                 "svcCreateEvent": "0x45",
                 "svcReadWriteRegister": "0x4E",
-                "svcMapTransferMemory": "0x51",
-                "svcUnmapTransferMemory": "0x52",
                 "svcCreateInterruptEvent": "0x53",
                 "svcQueryIoMapping": "0x55",
                 "svcCreateDeviceAddressSpace": "0x56",
@@ -128,8 +126,6 @@
                 "svcUnmapDeviceAddressSpace": "0x5c",
                 "svcGetSystemInfo": "0x6f",
                 "svcSetProcessMemoryPermission": "0x73",
-                "svcMapProcessMemory": "0x74",
-                "svcUnmapProcessMemory": "0x75",
                 "svcCallSecureMonitor": "0x7f"
             }
         }

emummc/emummc.ld

@@ -1,201 +0,0 @@
-OUTPUT_ARCH(aarch64)
-ENTRY(_start)
-
-PHDRS
-{
-	code   PT_LOAD FLAGS(5) /* Read | Execute */;
-	rodata PT_LOAD FLAGS(4) /* Read */;
-	data   PT_LOAD FLAGS(6) /* Read | Write */;
-	dyn    PT_DYNAMIC;
-}
-
-SECTIONS
-{
-	/* =========== CODE section =========== */
-	PROVIDE(__start__ = 0x0);
-	. = __start__;
-	__code_start = . ;
-
-	.crt0 :
-	{
-		KEEP (*(.crt0))
-		. = ALIGN(8);
-	} :code
-
-	.init :
-	{
-		KEEP( *(.init) )
-		. = ALIGN(8);
-	} :code
-
-	.plt :
-	{
-		*(.plt)
-		*(.iplt)
-		. = ALIGN(8);
-	} :code
-
-	.text :
-	{
-		*(.text.unlikely .text.*_unlikely .text.unlikely.*)
-		*(.text.exit .text.exit.*)
-		*(.text.startup .text.startup.*)
-		*(.text.hot .text.hot.*)
-		*(.text .stub .text.* .gnu.linkonce.t.*)
-		. = ALIGN(8);
-	} :code
-
-	.fini :
-	{
-		KEEP( *(.fini) )
-		. = ALIGN(8);
-	} :code
-
-	/* =========== RODATA section =========== */
-	. = ALIGN(0x1000);
-	__rodata_start = . ;
-
-	.nx-module-name : { KEEP (*(.nx-module-name)) } :rodata
-
-	.rodata :
-	{
-		*(.rodata .rodata.* .gnu.linkonce.r.*)
-		. = ALIGN(8);
-	} :rodata
-
-	.eh_frame_hdr     : { __eh_frame_hdr_start = .; *(.eh_frame_hdr) *(.eh_frame_entry .eh_frame_entry.*) __eh_frame_hdr_end = .; } :rodata
-	.eh_frame         : ONLY_IF_RO { KEEP (*(.eh_frame)) *(.eh_frame.*) } :rodata
-	.gcc_except_table : ONLY_IF_RO { *(.gcc_except_table .gcc_except_table.*) } :rodata
-	.gnu_extab        : ONLY_IF_RO { *(.gnu_extab*) } : rodata
-
-	.dynamic           : { *(.dynamic) } :rodata :dyn
-	.dynsym            : { *(.dynsym) } :rodata
-	.dynstr            : { *(.dynstr) } :rodata
-	.rela.dyn          : { *(.rela.*) } :rodata
-	.interp            : { *(.interp) } :rodata
-	.hash              : { *(.hash) } :rodata
-	.gnu.hash          : { *(.gnu.hash) } :rodata
-	.gnu.version       : { *(.gnu.version) } :rodata
-	.gnu.version_d     : { *(.gnu.version_d) } :rodata
-	.gnu.version_r     : { *(.gnu.version_r) } :rodata
-	.note.gnu.build-id : { *(.note.gnu.build-id) } :rodata
-
-	/* =========== DATA section =========== */
-	. = ALIGN(0x1000);
-	__data_start = . ;
-
-	.eh_frame : ONLY_IF_RW { KEEP (*(.eh_frame)) *(.eh_frame.*) } :data
-	.gcc_except_table : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) } :data
-	.gnu_extab : ONLY_IF_RW { *(.gnu_extab*) } : data
-	.exception_ranges : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) } :data
-
-	.tdata ALIGN(8) :
-	{
-		__tdata_lma = .;
-		*(.tdata .tdata.* .gnu.linkonce.td.*)
-		. = ALIGN(8);
-		__tdata_lma_end = .;
-	} :data
-
-	.tbss ALIGN(8) :
-	{
-		*(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon)
-		. = ALIGN(8);
-	} :data
-
-	.preinit_array ALIGN(8) :
-	{
-		PROVIDE (__preinit_array_start = .);
-		KEEP (*(.preinit_array))
-		PROVIDE (__preinit_array_end = .);
-	} :data
-
-	.init_array ALIGN(8) :
-	{
-		PROVIDE (__init_array_start = .);
-		KEEP( *(SORT_BY_INIT_PRIORITY(.init_array.*) SORT_BY_INIT_PRIORITY(.ctors.*)) )
-		KEEP( *(.init_array .ctors) )
-		PROVIDE (__init_array_end = .);
-	} :data
-
-	.fini_array ALIGN(8) :
-	{
-		PROVIDE (__fini_array_start = .);
-		KEEP( *(SORT_BY_INIT_PRIORITY(.fini_array.*) SORT_BY_INIT_PRIORITY(.dtors.*)) )
-		KEEP( *(.fini_array .dtors) )
-		PROVIDE (__fini_array_end = .);
-	} :data
-
-	__got_start__ = .;
-
-	.got            : { *(.got) *(.igot) } :data
-	.got.plt        : { *(.got.plt)  *(.igot.plt) } :data
-
-	__got_end__ = .;
-
-	.data ALIGN(8) :
-	{
-		*(.data .data.* .gnu.linkonce.d.*)
-		SORT(CONSTRUCTORS)
-	} :data
-
-	__bss_start__ = .;
-	.bss ALIGN(8) :
-	{
-		*(.dynbss)
-		*(.bss .bss.* .gnu.linkonce.b.*)
-		*(COMMON)
-		. = ALIGN(8);
-
-		/* Reserve space for the TLS segment of the main thread */
-		__tls_start = .;
-		. += + SIZEOF(.tdata) + SIZEOF(.tbss);
-		__tls_end = .;
-	} : data
-	__bss_end__ = .;
-
-	__end__ = ABSOLUTE(.) ;
-
-	. = ALIGN(0x1000);
-	__argdata__ = ABSOLUTE(.) ;
-
-	/* ==================
-	   ==== Metadata ====
-	   ================== */
-
-	/* Discard sections that difficult post-processing */
-	/DISCARD/ : { *(.group .comment .note) }
-
-	/* Stabs debugging sections. */
-	.stab          0 : { *(.stab) }
-	.stabstr       0 : { *(.stabstr) }
-	.stab.excl     0 : { *(.stab.excl) }
-	.stab.exclstr  0 : { *(.stab.exclstr) }
-	.stab.index    0 : { *(.stab.index) }
-	.stab.indexstr 0 : { *(.stab.indexstr) }
-
-	/* DWARF debug sections.
-	   Symbols in the DWARF debugging sections are relative to the beginning
-	   of the section so we begin them at 0. */
-
-	/* DWARF 1 */
-	.debug          0 : { *(.debug) }
-	.line           0 : { *(.line) }
-
-	/* GNU DWARF 1 extensions */
-	.debug_srcinfo  0 : { *(.debug_srcinfo) }
-	.debug_sfnames  0 : { *(.debug_sfnames) }
-
-	/* DWARF 1.1 and DWARF 2 */
-	.debug_aranges  0 : { *(.debug_aranges) }
-	.debug_pubnames 0 : { *(.debug_pubnames) }
-
-	/* DWARF 2 */
-	.debug_info     0 : { *(.debug_info) }
-	.debug_abbrev   0 : { *(.debug_abbrev) }
-	.debug_line     0 : { *(.debug_line) }
-	.debug_frame    0 : { *(.debug_frame) }
-	.debug_str      0 : { *(.debug_str) }
-	.debug_loc      0 : { *(.debug_loc) }
-	.debug_macinfo  0 : { *(.debug_macinfo) }
-}

emummc/emummc.specs

@@ -1,8 +0,0 @@
-%rename link                old_link
-
-*link:
-%(old_link) -T %:getenv(TOPDIR /emummc.ld) -pie --no-dynamic-linker --spare-dynamic-tags=0 --gc-sections -z text -z nodynamic-undefined-weak --build-id=sha1 --nx-module-name
-
-*startfile:
-crti%O%s crtbegin%O%s
-

emummc/source/FS/FS.h

@@ -37,15 +37,4 @@
 #define BOOT_PARTITION_SIZE 0x2000
 #define FS_READ_WRITE_ERROR 1048
 
-#define NAND_PATROL_SECTOR 0xC20
-#define NAND_PATROL_OFFSET 0x184000
-
-typedef struct _fs_nand_patrol_t
-{
-	uint8_t hmac[0x20];
-	unsigned int offset;
-	unsigned int count;
-	uint8_t rsvd[0x1D8];
-} fs_nand_patrol_t;
-
 #endif /* __FS_H__ */

emummc/source/FS/FS_offsets.c

@@ -47,38 +47,6 @@
 #include "offsets/910_exfat.h"
 #include "offsets/1000.h"
 #include "offsets/1000_exfat.h"
-#include "offsets/1020.h"
-#include "offsets/1020_exfat.h"
-#include "offsets/1100.h"
-#include "offsets/1100_exfat.h"
-#include "offsets/1200.h"
-#include "offsets/1200_exfat.h"
-#include "offsets/1203.h"
-#include "offsets/1203_exfat.h"
-#include "offsets/1300.h"
-#include "offsets/1300_exfat.h"
-#include "offsets/1310.h"
-#include "offsets/1310_exfat.h"
-#include "offsets/1400.h"
-#include "offsets/1400_exfat.h"
-#include "offsets/1500.h"
-#include "offsets/1500_exfat.h"
-#include "offsets/1600.h"
-#include "offsets/1600_exfat.h"
-#include "offsets/1603.h"
-#include "offsets/1603_exfat.h"
-#include "offsets/1700.h"
-#include "offsets/1700_exfat.h"
-#include "offsets/1800.h"
-#include "offsets/1800_exfat.h"
-#include "offsets/1810.h"
-#include "offsets/1810_exfat.h"
-#include "offsets/1900.h"
-#include "offsets/1900_exfat.h"
-#include "offsets/2000.h"
-#include "offsets/2000_exfat.h"
-#include "offsets/2010.h"
-#include "offsets/2010_exfat.h"
 #include "../utils/fatal.h"
 
 #define GET_OFFSET_STRUCT_NAME(vers) g_offsets##vers
@@ -99,7 +67,6 @@ static const fs_offsets_t GET_OFFSET_STRUCT_NAME(vers) = { \
     .nand_mutex                      = FS_OFFSET##vers##_NAND_MUTEX, \
     .active_partition                = FS_OFFSET##vers##_ACTIVE_PARTITION, \
     .sdmmc_das_handle                = FS_OFFSET##vers##_SDMMC_DAS_HANDLE, \
-    .sdmmc_accessor_controller_open  = FS_OFFSET##vers##_SDMMC_WRAPPER_CONTROLLER_OPEN, \
     .sdmmc_accessor_controller_close = FS_OFFSET##vers##_SDMMC_WRAPPER_CONTROLLER_CLOSE, \
     .sd_das_init                     = FS_OFFSET##vers##_SD_DAS_INIT, \
     .nintendo_paths                  = FS_OFFSET##vers##_NINTENDO_PATHS, \
@@ -137,38 +104,6 @@ DEFINE_OFFSET_STRUCT(_910);
 DEFINE_OFFSET_STRUCT(_910_EXFAT);
 DEFINE_OFFSET_STRUCT(_1000);
 DEFINE_OFFSET_STRUCT(_1000_EXFAT);
-DEFINE_OFFSET_STRUCT(_1020);
-DEFINE_OFFSET_STRUCT(_1020_EXFAT);
-DEFINE_OFFSET_STRUCT(_1100);
-DEFINE_OFFSET_STRUCT(_1100_EXFAT);
-DEFINE_OFFSET_STRUCT(_1200);
-DEFINE_OFFSET_STRUCT(_1200_EXFAT);
-DEFINE_OFFSET_STRUCT(_1203);
-DEFINE_OFFSET_STRUCT(_1203_EXFAT);
-DEFINE_OFFSET_STRUCT(_1300);
-DEFINE_OFFSET_STRUCT(_1300_EXFAT);
-DEFINE_OFFSET_STRUCT(_1310);
-DEFINE_OFFSET_STRUCT(_1310_EXFAT);
-DEFINE_OFFSET_STRUCT(_1400);
-DEFINE_OFFSET_STRUCT(_1400_EXFAT);
-DEFINE_OFFSET_STRUCT(_1500);
-DEFINE_OFFSET_STRUCT(_1500_EXFAT);
-DEFINE_OFFSET_STRUCT(_1600);
-DEFINE_OFFSET_STRUCT(_1600_EXFAT);
-DEFINE_OFFSET_STRUCT(_1603);
-DEFINE_OFFSET_STRUCT(_1603_EXFAT);
-DEFINE_OFFSET_STRUCT(_1700);
-DEFINE_OFFSET_STRUCT(_1700_EXFAT);
-DEFINE_OFFSET_STRUCT(_1800);
-DEFINE_OFFSET_STRUCT(_1800_EXFAT);
-DEFINE_OFFSET_STRUCT(_1810);
-DEFINE_OFFSET_STRUCT(_1810_EXFAT);
-DEFINE_OFFSET_STRUCT(_1900);
-DEFINE_OFFSET_STRUCT(_1900_EXFAT);
-DEFINE_OFFSET_STRUCT(_2000);
-DEFINE_OFFSET_STRUCT(_2000_EXFAT);
-DEFINE_OFFSET_STRUCT(_2010);
-DEFINE_OFFSET_STRUCT(_2010_EXFAT);
 
 const fs_offsets_t *get_fs_offsets(enum FS_VER version) {
     switch (version) {
@@ -234,70 +169,6 @@ const fs_offsets_t *get_fs_offsets(enum FS_VER version) {
             return &(GET_OFFSET_STRUCT_NAME(_1000));
         case FS_VER_10_0_0_EXFAT:
             return &(GET_OFFSET_STRUCT_NAME(_1000_EXFAT));
-        case FS_VER_10_2_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1020));
-        case FS_VER_10_2_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1020_EXFAT));
-        case FS_VER_11_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1100));
-        case FS_VER_11_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1100_EXFAT));
-        case FS_VER_12_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1200));
-        case FS_VER_12_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1200_EXFAT));
-        case FS_VER_12_0_3:
-            return &(GET_OFFSET_STRUCT_NAME(_1203));
-        case FS_VER_12_0_3_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1203_EXFAT));
-        case FS_VER_13_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1300));
-        case FS_VER_13_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1300_EXFAT));
-        case FS_VER_13_1_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1310));
-        case FS_VER_13_1_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1310_EXFAT));
-        case FS_VER_14_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1400));
-        case FS_VER_14_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1400_EXFAT));
-        case FS_VER_15_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1500));
-        case FS_VER_15_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1500_EXFAT));
-        case FS_VER_16_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1600));
-        case FS_VER_16_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1600_EXFAT));
-        case FS_VER_16_0_3:
-            return &(GET_OFFSET_STRUCT_NAME(_1603));
-        case FS_VER_16_0_3_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1603_EXFAT));
-        case FS_VER_17_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1700));
-        case FS_VER_17_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1700_EXFAT));
-        case FS_VER_18_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1800));
-        case FS_VER_18_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1800_EXFAT));
-        case FS_VER_18_1_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1810));
-        case FS_VER_18_1_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1810_EXFAT));
-        case FS_VER_19_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_1900));
-        case FS_VER_19_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_1900_EXFAT));
-        case FS_VER_20_0_0:
-            return &(GET_OFFSET_STRUCT_NAME(_2000));
-        case FS_VER_20_0_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_2000_EXFAT));
-        case FS_VER_20_1_0:
-            return &(GET_OFFSET_STRUCT_NAME(_2010));
-        case FS_VER_20_1_0_EXFAT:
-            return &(GET_OFFSET_STRUCT_NAME(_2010_EXFAT));
         default:
             fatal_abort(Fatal_UnknownVersion);
     }

emummc/source/FS/FS_offsets.h

@@ -41,7 +41,6 @@ typedef struct {
     // Misc funcs
     uintptr_t lock_mutex;
     uintptr_t unlock_mutex;
-    uintptr_t sdmmc_accessor_controller_open;
     uintptr_t sdmmc_accessor_controller_close;
     // Misc data
     uintptr_t sd_mutex;

emummc/source/FS/FS_structs.h

@@ -35,7 +35,7 @@ typedef struct sdmmc_accessor_vt
     void *dtor;
     void *map_device_addr_space;
     void *unmap_device_addr_space;
-    uint64_t (*sdmmc_accessor_controller_open)(void *);
+    void *controller_open;
     uint64_t (*sdmmc_accessor_controller_close)(void *);
     uint64_t (*read_write)(void *, uint64_t, uint64_t, void *, uint64_t, uint64_t);
     // More not included because we don't use it.

emummc/source/FS/FS_versions.h

@@ -68,54 +68,6 @@ enum FS_VER
     FS_VER_10_0_0,
     FS_VER_10_0_0_EXFAT,
 
-    FS_VER_10_2_0,
-    FS_VER_10_2_0_EXFAT,
-
-    FS_VER_11_0_0,
-    FS_VER_11_0_0_EXFAT,
-
-    FS_VER_12_0_0,
-    FS_VER_12_0_0_EXFAT,
-
-    FS_VER_12_0_3,
-    FS_VER_12_0_3_EXFAT,
-
-    FS_VER_13_0_0,
-    FS_VER_13_0_0_EXFAT,
-
-    FS_VER_13_1_0,
-    FS_VER_13_1_0_EXFAT,
-
-    FS_VER_14_0_0,
-    FS_VER_14_0_0_EXFAT,
-
-    FS_VER_15_0_0,
-    FS_VER_15_0_0_EXFAT,
-
-    FS_VER_16_0_0,
-    FS_VER_16_0_0_EXFAT,
-
-    FS_VER_16_0_3,
-    FS_VER_16_0_3_EXFAT,
-
-    FS_VER_17_0_0,
-    FS_VER_17_0_0_EXFAT,
-
-    FS_VER_18_0_0,
-    FS_VER_18_0_0_EXFAT,
-
-    FS_VER_18_1_0,
-    FS_VER_18_1_0_EXFAT,
-
-    FS_VER_19_0_0,
-    FS_VER_19_0_0_EXFAT,
-
-    FS_VER_20_0_0,
-    FS_VER_20_0_0_EXFAT,
-
-    FS_VER_20_1_0,
-    FS_VER_20_1_0_EXFAT,
-
     FS_VER_MAX,
 };
 

emummc/source/FS/offsets/100.h

@@ -34,7 +34,6 @@
 #define FS_OFFSET_100_LOCK_MUTEX          0x2884
 #define FS_OFFSET_100_UNLOCK_MUTEX        0x28F0
 
-#define FS_OFFSET_100_SDMMC_WRAPPER_CONTROLLER_OPEN  0
 #define FS_OFFSET_100_SDMMC_WRAPPER_CONTROLLER_CLOSE 0x6A8AC
 
 // Misc Data

emummc/source/FS/offsets/1000.h

@@ -34,7 +34,6 @@
 #define FS_OFFSET_1000_LOCK_MUTEX          0x28910
 #define FS_OFFSET_1000_UNLOCK_MUTEX        0x28960
 
-#define FS_OFFSET_1000_SDMMC_WRAPPER_CONTROLLER_OPEN  0
 #define FS_OFFSET_1000_SDMMC_WRAPPER_CONTROLLER_CLOSE 0x1422E0
 
 // Misc Data

emummc/source/FS/offsets/1000_exfat.h

@@ -34,7 +34,6 @@
 #define FS_OFFSET_1000_EXFAT_LOCK_MUTEX          0x28910
 #define FS_OFFSET_1000_EXFAT_UNLOCK_MUTEX        0x28960
 
-#define FS_OFFSET_1000_EXFAT_SDMMC_WRAPPER_CONTROLLER_OPEN  0
 #define FS_OFFSET_1000_EXFAT_SDMMC_WRAPPER_CONTROLLER_CLOSE 0x1422E0
 
 // Misc Data

emummc/source/FS/offsets/1020.h

@@ -1,59 +0,0 @@
-/*
- * Copyright (c) 2019 m4xw <m4x@m4xw.net>
- * Copyright (c) 2019 Atmosphere-NX
- *
- * This program is free software; you can redistribute it and/or modify it
- * under the terms and conditions of the GNU General Public License,
- * version 2, as published by the Free Software Foundation.
- *
- * This program is distributed in the hope it will be useful, but WITHOUT
- * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
- * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
- * more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program.  If not, see <http://www.gnu.org/licenses/>.
- */
-#ifndef __FS_1020_H__
-#define __FS_1020_H__
-
-// Accessor vtable getters
-#define FS_OFFSET_1020_SDMMC_ACCESSOR_GC   0x14E0F0
-#define FS_OFFSET_1020_SDMMC_ACCESSOR_SD   0x14C200
-#define FS_OFFSET_1020_SDMMC_ACCESSOR_NAND 0x147080
-
-// Hooks
-#define FS_OFFSET_1020_SDMMC_WRAPPER_READ  0x1427E0
-#define FS_OFFSET_1020_SDMMC_WRAPPER_WRITE 0x1428C0
-#define FS_OFFSET_1020_RTLD                0x634
-#define FS_OFFSET_1020_RTLD_DESTINATION    0x9C
-
-#define FS_OFFSET_1020_CLKRST_SET_MIN_V_CLK_RATE 0x141A00
-
-// Misc funcs
-#define FS_OFFSET_1020_LOCK_MUTEX          0x28910
-#define FS_OFFSET_1020_UNLOCK_MUTEX        0x28960
-
-#define FS_OFFSET_1020_SDMMC_WRAPPER_CONTROLLER_OPEN  0
-#define FS_OFFSET_1020_SDMMC_WRAPPER_CONTROLLER_CLOSE 0x142740
-
-// Misc Data
-#define FS_OFFSET_1020_SD_MUTEX            0xE273E8
-#define FS_OFFSET_1020_NAND_MUTEX          0xE22DA0
-#define FS_OFFSET_1020_ACTIVE_PARTITION    0xE22DE0
-#define FS_OFFSET_1020_SDMMC_DAS_HANDLE    0xE0AB90
-
-// NOPs
-#define FS_OFFSET_1020_SD_DAS_INIT         0x15214C
-
-// Nintendo Paths
-#define FS_OFFSET_1020_NINTENDO_PATHS \
-{ \
-	{.opcode_reg = 3, .adrp_offset = 0x0006BBA4, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x00078520, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x0007ED0C, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 4, .adrp_offset = 0x0009115C, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 0, .adrp_offset = 0, .add_rel_offset = 0}, \
-}
-
-#endif // __FS_1020_H__

emummc/source/FS/offsets/1020_exfat.h

@@ -1,59 +0,0 @@
-/*
- * Copyright (c) 2019 m4xw <m4x@m4xw.net>
- * Copyright (c) 2019 Atmosphere-NX
- *
- * This program is free software; you can redistribute it and/or modify it
- * under the terms and conditions of the GNU General Public License,
- * version 2, as published by the Free Software Foundation.
- *
- * This program is distributed in the hope it will be useful, but WITHOUT
- * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
- * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
- * more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program.  If not, see <http://www.gnu.org/licenses/>.
- */
-#ifndef __FS_1020_EXFAT_H__
-#define __FS_1020_EXFAT_H__
-
-// Accessor vtable getters
-#define FS_OFFSET_1020_EXFAT_SDMMC_ACCESSOR_GC   0x14E0F0
-#define FS_OFFSET_1020_EXFAT_SDMMC_ACCESSOR_SD   0x14C200
-#define FS_OFFSET_1020_EXFAT_SDMMC_ACCESSOR_NAND 0x147080
-
-// Hooks
-#define FS_OFFSET_1020_EXFAT_SDMMC_WRAPPER_READ  0x1427E0
-#define FS_OFFSET_1020_EXFAT_SDMMC_WRAPPER_WRITE 0x1428C0
-#define FS_OFFSET_1020_EXFAT_RTLD                0x634
-#define FS_OFFSET_1020_EXFAT_RTLD_DESTINATION    0x9C
-
-#define FS_OFFSET_1020_EXFAT_CLKRST_SET_MIN_V_CLK_RATE 0x141A00
-
-// Misc funcs
-#define FS_OFFSET_1020_EXFAT_LOCK_MUTEX          0x28910
-#define FS_OFFSET_1020_EXFAT_UNLOCK_MUTEX        0x28960
-
-#define FS_OFFSET_1020_EXFAT_SDMMC_WRAPPER_CONTROLLER_OPEN  0
-#define FS_OFFSET_1020_EXFAT_SDMMC_WRAPPER_CONTROLLER_CLOSE 0x142740
-
-// Misc Data
-#define FS_OFFSET_1020_EXFAT_SD_MUTEX            0xE353E8
-#define FS_OFFSET_1020_EXFAT_NAND_MUTEX          0xE30DA0
-#define FS_OFFSET_1020_EXFAT_ACTIVE_PARTITION    0xE30DE0
-#define FS_OFFSET_1020_EXFAT_SDMMC_DAS_HANDLE    0xE18B90
-
-// NOPs
-#define FS_OFFSET_1020_EXFAT_SD_DAS_INIT         0x15214C
-
-// Nintendo Paths
-#define FS_OFFSET_1020_EXFAT_NINTENDO_PATHS \
-{ \
-	{.opcode_reg = 3, .adrp_offset = 0x0006BBA4, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x00078520, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x0007ED0C, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 4, .adrp_offset = 0x0009115C, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 0, .adrp_offset = 0, .add_rel_offset = 0}, \
-}
-
-#endif // __FS_1020_EXFAT_H__

emummc/source/FS/offsets/1100.h

@@ -1,59 +0,0 @@
-/*
- * Copyright (c) 2019 m4xw <m4x@m4xw.net>
- * Copyright (c) 2019 Atmosphere-NX
- *
- * This program is free software; you can redistribute it and/or modify it
- * under the terms and conditions of the GNU General Public License,
- * version 2, as published by the Free Software Foundation.
- *
- * This program is distributed in the hope it will be useful, but WITHOUT
- * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
- * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
- * more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program.  If not, see <http://www.gnu.org/licenses/>.
- */
-#ifndef __FS_1100_H__
-#define __FS_1100_H__
-
-// Accessor vtable getters
-#define FS_OFFSET_1100_SDMMC_ACCESSOR_GC   0x156D90
-#define FS_OFFSET_1100_SDMMC_ACCESSOR_SD   0x154F40
-#define FS_OFFSET_1100_SDMMC_ACCESSOR_NAND 0x1500F0
-
-// Hooks
-#define FS_OFFSET_1100_SDMMC_WRAPPER_READ  0x14B990
-#define FS_OFFSET_1100_SDMMC_WRAPPER_WRITE 0x14BA70
-#define FS_OFFSET_1100_RTLD                0x688
-#define FS_OFFSET_1100_RTLD_DESTINATION    ((uintptr_t)(INT64_C(-0x3C)))
-
-#define FS_OFFSET_1100_CLKRST_SET_MIN_V_CLK_RATE 0x14AC40
-
-// Misc funcs
-#define FS_OFFSET_1100_LOCK_MUTEX          0x28FF0
-#define FS_OFFSET_1100_UNLOCK_MUTEX        0x29040
-
-#define FS_OFFSET_1100_SDMMC_WRAPPER_CONTROLLER_OPEN  0x14B840
-#define FS_OFFSET_1100_SDMMC_WRAPPER_CONTROLLER_CLOSE 0x14B8F0
-
-// Misc Data
-#define FS_OFFSET_1100_SD_MUTEX            0xE323E8
-#define FS_OFFSET_1100_NAND_MUTEX          0xE2D338
-#define FS_OFFSET_1100_ACTIVE_PARTITION    0xE2D378
-#define FS_OFFSET_1100_SDMMC_DAS_HANDLE    0xE15D40
-
-// NOPs
-#define FS_OFFSET_1100_SD_DAS_INIT         0x273B4
-
-// Nintendo Paths
-#define FS_OFFSET_1100_NINTENDO_PATHS \
-{ \
-	{.opcode_reg = 3, .adrp_offset = 0x0006D944, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x0007A3C0, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x00080708, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 4, .adrp_offset = 0x00092198, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 0, .adrp_offset = 0, .add_rel_offset = 0}, \
-}
-
-#endif // __FS_1100_H__

emummc/source/FS/offsets/1100_exfat.h

@@ -1,59 +0,0 @@
-/*
- * Copyright (c) 2019 m4xw <m4x@m4xw.net>
- * Copyright (c) 2019 Atmosphere-NX
- *
- * This program is free software; you can redistribute it and/or modify it
- * under the terms and conditions of the GNU General Public License,
- * version 2, as published by the Free Software Foundation.
- *
- * This program is distributed in the hope it will be useful, but WITHOUT
- * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
- * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
- * more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program.  If not, see <http://www.gnu.org/licenses/>.
- */
-#ifndef __FS_1100_EXFAT_H__
-#define __FS_1100_EXFAT_H__
-
-// Accessor vtable getters
-#define FS_OFFSET_1100_EXFAT_SDMMC_ACCESSOR_GC   0x156D90
-#define FS_OFFSET_1100_EXFAT_SDMMC_ACCESSOR_SD   0x154F40
-#define FS_OFFSET_1100_EXFAT_SDMMC_ACCESSOR_NAND 0x1500F0
-
-// Hooks
-#define FS_OFFSET_1100_EXFAT_SDMMC_WRAPPER_READ  0x14B990
-#define FS_OFFSET_1100_EXFAT_SDMMC_WRAPPER_WRITE 0x14BA70
-#define FS_OFFSET_1100_EXFAT_RTLD                0x688
-#define FS_OFFSET_1100_EXFAT_RTLD_DESTINATION    ((uintptr_t)(INT64_C(-0x3C)))
-
-#define FS_OFFSET_1100_EXFAT_CLKRST_SET_MIN_V_CLK_RATE 0x14AC40
-
-// Misc funcs
-#define FS_OFFSET_1100_EXFAT_LOCK_MUTEX          0x28FF0
-#define FS_OFFSET_1100_EXFAT_UNLOCK_MUTEX        0x29040
-
-#define FS_OFFSET_1100_EXFAT_SDMMC_WRAPPER_CONTROLLER_OPEN  0x14B840
-#define FS_OFFSET_1100_EXFAT_SDMMC_WRAPPER_CONTROLLER_CLOSE 0x14B8F0
-
-// Misc Data
-#define FS_OFFSET_1100_EXFAT_SD_MUTEX            0xE403E8
-#define FS_OFFSET_1100_EXFAT_NAND_MUTEX          0xE3B338
-#define FS_OFFSET_1100_EXFAT_ACTIVE_PARTITION    0xE3B378
-#define FS_OFFSET_1100_EXFAT_SDMMC_DAS_HANDLE    0xE23D40
-
-// NOPs
-#define FS_OFFSET_1100_EXFAT_SD_DAS_INIT         0x273B4
-
-// Nintendo Paths
-#define FS_OFFSET_1100_EXFAT_NINTENDO_PATHS \
-{ \
-	{.opcode_reg = 3, .adrp_offset = 0x0006D944, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x0007A3C0, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x00080708, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 4, .adrp_offset = 0x00092198, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 0, .adrp_offset = 0, .add_rel_offset = 0}, \
-}
-
-#endif // __FS_1100_EXFAT_H__

emummc/source/FS/offsets/1200.h

@@ -1,59 +0,0 @@
-/*
- * Copyright (c) 2019 m4xw <m4x@m4xw.net>
- * Copyright (c) 2019 Atmosphere-NX
- *
- * This program is free software; you can redistribute it and/or modify it
- * under the terms and conditions of the GNU General Public License,
- * version 2, as published by the Free Software Foundation.
- *
- * This program is distributed in the hope it will be useful, but WITHOUT
- * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
- * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
- * more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program.  If not, see <http://www.gnu.org/licenses/>.
- */
-#ifndef __FS_1200_H__
-#define __FS_1200_H__
-
-// Accessor vtable getters
-#define FS_OFFSET_1200_SDMMC_ACCESSOR_GC   0x154FD0
-#define FS_OFFSET_1200_SDMMC_ACCESSOR_SD   0x156DE0
-#define FS_OFFSET_1200_SDMMC_ACCESSOR_NAND 0x155500
-
-// Hooks
-#define FS_OFFSET_1200_SDMMC_WRAPPER_READ  0x150970
-#define FS_OFFSET_1200_SDMMC_WRAPPER_WRITE 0x150A30
-#define FS_OFFSET_1200_RTLD                0x688
-#define FS_OFFSET_1200_RTLD_DESTINATION    ((uintptr_t)(INT64_C(-0x3C)))
-
-#define FS_OFFSET_1200_CLKRST_SET_MIN_V_CLK_RATE 0x14FCC0
-
-// Misc funcs
-#define FS_OFFSET_1200_LOCK_MUTEX          0x29350
-#define FS_OFFSET_1200_UNLOCK_MUTEX        0x293A0
-
-#define FS_OFFSET_1200_SDMMC_WRAPPER_CONTROLLER_OPEN  0x150850
-#define FS_OFFSET_1200_SDMMC_WRAPPER_CONTROLLER_CLOSE 0x1508E0
-
-// Misc Data
-#define FS_OFFSET_1200_SD_MUTEX            0xE3D3E8
-#define FS_OFFSET_1200_NAND_MUTEX          0xE38768
-#define FS_OFFSET_1200_ACTIVE_PARTITION    0xE387A8
-#define FS_OFFSET_1200_SDMMC_DAS_HANDLE    0xE20DB0
-
-// NOPs
-#define FS_OFFSET_1200_SD_DAS_INIT         0x27244
-
-// Nintendo Paths
-#define FS_OFFSET_1200_NINTENDO_PATHS \
-{ \
-	{.opcode_reg = 3, .adrp_offset = 0x0006E810, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x0007AEC0, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 4, .adrp_offset = 0x00081254, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 4, .adrp_offset = 0x00092850, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 0, .adrp_offset = 0, .add_rel_offset = 0}, \
-}
-
-#endif // __FS_1200_H__

emummc/source/FS/offsets/1200_exfat.h

@@ -1,59 +0,0 @@
-/*
- * Copyright (c) 2019 m4xw <m4x@m4xw.net>
- * Copyright (c) 2019 Atmosphere-NX
- *
- * This program is free software; you can redistribute it and/or modify it
- * under the terms and conditions of the GNU General Public License,
- * version 2, as published by the Free Software Foundation.
- *
- * This program is distributed in the hope it will be useful, but WITHOUT
- * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
- * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
- * more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program.  If not, see <http://www.gnu.org/licenses/>.
- */
-#ifndef __FS_1200_EXFAT_H__
-#define __FS_1200_EXFAT_H__
-
-// Accessor vtable getters
-#define FS_OFFSET_1200_EXFAT_SDMMC_ACCESSOR_GC   0x154FD0
-#define FS_OFFSET_1200_EXFAT_SDMMC_ACCESSOR_SD   0x156DE0
-#define FS_OFFSET_1200_EXFAT_SDMMC_ACCESSOR_NAND 0x155500
-
-// Hooks
-#define FS_OFFSET_1200_EXFAT_SDMMC_WRAPPER_READ  0x150970
-#define FS_OFFSET_1200_EXFAT_SDMMC_WRAPPER_WRITE 0x150A30
-#define FS_OFFSET_1200_EXFAT_RTLD                0x688
-#define FS_OFFSET_1200_EXFAT_RTLD_DESTINATION    ((uintptr_t)(INT64_C(-0x3C)))
-
-#define FS_OFFSET_1200_EXFAT_CLKRST_SET_MIN_V_CLK_RATE 0x14FCC0
-
-// Misc funcs
-#define FS_OFFSET_1200_EXFAT_LOCK_MUTEX          0x29350
-#define FS_OFFSET_1200_EXFAT_UNLOCK_MUTEX        0x293A0
-
-#define FS_OFFSET_1200_EXFAT_SDMMC_WRAPPER_CONTROLLER_OPEN  0x150850
-#define FS_OFFSET_1200_EXFAT_SDMMC_WRAPPER_CONTROLLER_CLOSE 0x1508E0
-
-// Misc Data
-#define FS_OFFSET_1200_EXFAT_SD_MUTEX            0xE4B3E8
-#define FS_OFFSET_1200_EXFAT_NAND_MUTEX          0xE46768
-#define FS_OFFSET_1200_EXFAT_ACTIVE_PARTITION    0xE467A8
-#define FS_OFFSET_1200_EXFAT_SDMMC_DAS_HANDLE    0xE2EDB0
-
-// NOPs
-#define FS_OFFSET_1200_EXFAT_SD_DAS_INIT         0x27244
-
-// Nintendo Paths
-#define FS_OFFSET_1200_EXFAT_NINTENDO_PATHS \
-{ \
-	{.opcode_reg = 3, .adrp_offset = 0x0006E810, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 3, .adrp_offset = 0x0007AEC0, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 4, .adrp_offset = 0x00081254, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 4, .adrp_offset = 0x00092850, .add_rel_offset = 0x00000004}, \
-	{.opcode_reg = 0, .adrp_offset = 0, .add_rel_offset = 0}, \
-}
-
-#endif // __FS_1200_EXFAT_H__