I cannot find any actual explanation of what the "atmosphere=1" boot config entry does for Hekate. The readme on the Hekate repo just says "Enables Atmosphere patching" which means nothing to me. I did a search of the entire repo and I can see that Hekate checks this value a few different times in hos, fss, and secmon, but I don't understand what it actually does.
I ask this because I see most current guides omit this line, regardless of how they are booting Atmosphere (fusee primary or secondary), so I'd like to know what it actually does and if it's even necessary.
Honestly, the explanation of a lot of the Hekate configuration file is incredibly vague and I wish it was explained better, because there are several other entries that I don't understand. Part of the problem is the use of completely unexplained acronyms, such as PMU (which based on some Google results that brought up listings for replacement pats, I can only assume means "Power Management Unit"). Another example is "fullsvcperm=1" which is described as "Disables SVC verification (full services permission)". Again, based on some Googling I can only assume this enables access to all SVC system calls, but a bit more explanation of when/why you would/wouldn't want this enabled would be great (I assume it's for developers).
I ask this because I see most current guides omit this line, regardless of how they are booting Atmosphere (fusee primary or secondary), so I'd like to know what it actually does and if it's even necessary.
Honestly, the explanation of a lot of the Hekate configuration file is incredibly vague and I wish it was explained better, because there are several other entries that I don't understand. Part of the problem is the use of completely unexplained acronyms, such as PMU (which based on some Google results that brought up listings for replacement pats, I can only assume means "Power Management Unit"). Another example is "fullsvcperm=1" which is described as "Disables SVC verification (full services permission)". Again, based on some Googling I can only assume this enables access to all SVC system calls, but a bit more explanation of when/why you would/wouldn't want this enabled would be great (I assume it's for developers).
Last edited by AdmiralSpeedy,