Atmosphere v0.13.0
This version breaks all system modules that use Atmosphere libraries! They must first be adapted to the new API.
File-based EmuMMC has been speeded up considerably and is now almost as fast as that based on raw partitions.
Attention, Hekate users must imperatively use the latest version 5.3.0 which has just been put online because there are important changes in Atmosphere 0.13.0.
Atmosphere v0.13.0 is the thirty-second official version of Atmosphere, and it should also be noted that SciresM promises Mariko support for this summer!
fusee-primary has been updated and thanks to the Switchbrew team, Atmosphere 0.13.0 is delivered with version 2.3.2 of the hbl and version 3.3.0 of the hbmenu.
Changes in Atmosphere 0.13.0
fusee-primary was last updated in: 0.13.0.Download/Link: Atmosphere v0.13.0
With thanks to the @switchbrew team, Atmosphere 0.13.0 is bundled with hbl 2.3.2, and hbmenu 3.3.0.
The following was changed since the last release:
exosphere, atmosphere'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 ambiance'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.
atmosphere will want to have software support for mariko hardware, and this is not possible to fit in 1 KB.
The exosphere rewrite (which was codenamed exosphere2 during development) solves these problems.
The new codebase is C ++ 20 written in ambiance'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: exosphere 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 exosphere binary is not abi-compatible with the old one. Users who boot using hekate should upgrade to hekate v5.3.0 before running 0.13.0 (or boot fusee-primary via hekate).
atmosphere'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 ambiance 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 ambiance's future development plans, the project's roadmap was updated.
General system stability improvements to enhance the user's experience.
0 Comments