Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,701,448
  • Replies Replies 9,233
  • Likes Likes 92
impeeza said:
View attachment 566742
Click to expand...
FS patches remains the same, ES patches changed but nothing major, I'm going to test on a test emunand just now, I think it'll probably work fine.

EDIT: Nope, don't update - doesn't get to the switch screen. Wait for an AtmosphereNX update.
 
Last edited by AmeliaFox,
  • Wow
Reactions: impeeza

Attachments

  • Love
  • Like
Reactions: Chalon, juanvlc, Ngacoi and 3 others
bth said:
it's just enum changes, like the ones at https://github.com/Atmosphere-NX/At...nges/020ed307b1c404eeb5d16949bc3ecd3b2997fa54

if you want to recompile the current pending pull request of ( https://github.com/Atmosphere-NX/Atmosphere/pull/2786 )
git remote add alula https://github.com/alula/Atmosphere.git
git fetch alula
git rebase alula/alula
make -j4

result:
atmosphere-1.11.1-master-020ed307b
Click to expand...
WTF, why spam the forum with these non original releases? just let people wait for an official release from the original sources. That way they will get releases with proper hashes. I think you are trying to help but you are not really helping. There's probably going to be an original release later today.
 
  • Like
Reactions: XenoFredo and Andre63
AmeliaFox said:
WTF, why spam the forum with these non original releases? just let people wait for an official release from the original sources. That way they will get releases with proper hashes. I think you are trying to help but you are not really helping. There's probably going to be an original release later today.
Click to expand...
They are original sources... And maybe the PR that will become the oficial 22.1.0 support in main branch.
 
josete2k said:
They are original sources... And maybe the PR that will become the oficial 22.1.0 support in main branch.
Click to expand...
The build hash isn't original though and FYI you don't know if anything else is going to be added that isn't on the git yet. There's a release page for a reason. I get bth is excited or whatever to post a release, but it's not needed for him to post his own compiled release. In recent weeks there's been quite a few people on here posting unfinished/modified releases which only confuses people and spams the forum.
 
  • Like
Reactions: Nephiel
AmeliaFox said:
The build hash isn't original though and FYI you don't know if anything else is going to be added that isn't on the git yet. There's a release page for a reason. I get bth is excited or whatever to post a release, but it's not needed for him to post his own compiled release. In recent weeks there's been quite a few people on here posting unfinished/modified releases which only confuses people and spams the forum.
Click to expand...
that quite literally is the build hash for the commit that introduces the enum changes

you seem misinformed, do the steps yourself on master branch of atmosphere and you will end up with the same result.


reproducable steps:
git clone https://github.com/Atmosphere-NX/Atmosphere.git
cd Atmosphere
git remote add alula https://github.com/alula/Atmosphere.git
git fetch alula
git rebase alula/alula
make -j4

1:1


no unofficial sources.

you might not know, but I do. nothing else was changed for 22.1.0

if you're going to make nonsense claims, back it up with proof.

https://switchbrew.org/wiki/22.1.0

log.jpg
 
Last edited by bth,
  • Love
Reactions: impeeza
bth said:
that quite literally is the build hash for the commit that introduces the enum changes

you seem misinformed, do the steps yourself on master branch of atmosphere and you will end up with the same result.


reproducable steps:
git clone https://github.com/Atmosphere-NX/Atmosphere.git
cd Atmosphere
git remote add alula https://github.com/alula/Atmosphere.git
git fetch alula
git rebase alula/alula
make -j4

1:1


no unofficial sources.

you might not know, but I do. nothing else was changed for 22.1.0

if you're going to make nonsense claims, back it up with proof.

https://switchbrew.org/wiki/22.1.0

View attachment 566798
Click to expand...
FYI, I know how to build this so no need for you to post instructions, you don't have a time machine so you don't know for certain that the released build will have the same hash and you certainly don't know if anything else is going to be added before that release. Once again, let me be clear - there's a release page for a reason. I get you are "excited" or whatever it is you get from posting these unofficial releases, however please just let people get it from the official github release page in future. You already have your own github page where people can download your "patched" version if they feel the need. There's no need to spam the forum.
 
  • Haha
Reactions: ChibiMofo
AmeliaFox said:
FYI, I know how to build this so no need for you to post instructions, you don't have a time machine so you don't know for certain that the released build will have the same hash and you certainly don't know if anything else is going to be added before that release. Once again, let me be clear - there's a release page for a reason. I get you are "excited" or whatever it is you get from posting these unofficial releases, however please just let people get it from the official github release page in future. You already have your own github page where people can download your "patched" version if they feel the need. There's no need to spam the forum.
Click to expand...
Build the enum commit as per instructions and your build hash will be identical.

stop spreading misinformation or false accusations.

kindly do apologize.

"my own github page" contains a different version of atmosphere, it is my fork. the compiled output described is not that.


that commit will be canonical in the git timeline, aside from a PR merge commit which will override "latest" sha1, but that commit will still be what introduces it.
it's 1:1 what needs to boot 22.1.0

no unofficial sources, nothing extra.

substantiate claims (you can't) -> apologize
 
Last edited by bth,
  • Like
  • Love
Reactions: ChibiMofo and josete2k
Ultimos54 said:
to confirm we can update to latest patch and atmostphere is now up to date? where do i download
Click to expand...

Not up to date yet. The update is supposedly small, so you can try building it on your own if you know what you're doing. IMO it's better to just wait for the official release, which should be soon.
 
Ultimos54 said:
to confirm we can update to latest patch and atmostphere is now up to date? where do i download
Click to expand...
If you update to 22.1.0 this build is made with official sources...

bth

Hacking  Post in thread 'Atmosphere-NX - Custom Firmware in development by SciresM'

it's just enum changes, like the ones at https://github.com/Atmosphere-NX/At...nges/020ed307b1c404eeb5d16949bc3ecd3b2997fa54

if you want to recompile the current pending pull request of ( https://github.com/Atmosphere-NX/Atmosphere/pull/2786 )
git remote add alula https://github.com/alula/Atmosphere.git
git fetch alula
git rebase alula/alula
make -j4

result:
atmosphere-1.11.1-master-020ed307b
  • Love
  • Like
 
  • Like
Reactions: LuigiGad
bth said:
that quite literally is the build hash for the commit that introduces the enum changes

you seem misinformed, do the steps yourself on master branch of atmosphere and you will end up with the same result.


reproducable steps:
git clone https://github.com/Atmosphere-NX/Atmosphere.git
cd Atmosphere
git remote add alula https://github.com/alula/Atmosphere.git
git fetch alula
git rebase alula/alula
make -j4

1:1


no unofficial sources.

you might not know, but I do. nothing else was changed for 22.1.0

if you're going to make nonsense claims, back it up with proof.

https://switchbrew.org/wiki/22.1.0

View attachment 566798
Click to expand...
Is there any significant improvements on this release? like the 22.0 claimed major 'HD' res overhaul?
 
@bth Can you please explain why you add the alula fork when it states it's 52 commits behind Atmosphere-NX / Atmosphere master? Thank you. 🙂
 
VioletRose said:
@bth Can you please explain why you add the alula fork when it states it's 52 commits behind Atmosphere-NX / Atmosphere master? Thank you. 🙂
Click to expand...
You're not using the git cli like instructed and looking at github.com, and as suggested by nature of your question, don't understand how things work.

the pull request originates from the branch alula ( https://github.com/alula/Atmosphere/tree/alula ), to introduce commit "020ed307b1c404eeb5d16949bc3ecd3b2997fa54",

which is now merged into mainline atmosphere at https://github.com/Atmosphere-NX/Atmosphere/commit/020ed307b1c404eeb5d16949bc3ecd3b2997fa54

with two commits ontop of that doing nothing, one for the pull request merge (as the maintainers of atmosphere doesn't seem to know they can just rebase it in), and an additional subrepo update, which does nothing.

all in all @AmeliaFox still does owes me an apology, as nothing else was changed, and the canonical representation is as I said it would be.
 
bth said:
You're not using the git cli like instructed and looking at github.com, and as suggested by nature of your question, don't understand how things work.

the pull request originates from the branch alula ( https://github.com/alula/Atmosphere/tree/alula ), to introduce commit "020ed307b1c404eeb5d16949bc3ecd3b2997fa54",

which is now merged into mainline atmosphere at https://github.com/Atmosphere-NX/Atmosphere/commit/020ed307b1c404eeb5d16949bc3ecd3b2997fa54

with two commits ontop of that doing nothing, one for the pull request merge (as the maintainers of atmosphere doesn't seem to know they can just rebase it in), and an additional subrepo update, which does nothing.

all in all @AmeliaFox still does owes me an apology, as nothing else was changed, and the canonical representation is as I said it would be.
Click to expand...
Subrepo are used for compiling homebrew that needs libraries from AMS, Mission Control submodules is one of them.
 
josete2k said:
Subrepo are used for compiling homebrew that needs libraries from AMS, Mission Control submodules is one of them.
Click to expand...
No. The subrepo PR for this merge is in the other direction.

subrepo commit does nothing for the atmosphere repository in this context.

The canonical commit which introduces the change did so directly to atmosphere libraries (in the atmosphere repository), instead of like how scires does it, to atmosphere libs repository and then sync subrepo to atmosphere (which would introduce the commits that way).


you can tell how this works with a perfect example, being my fork.

https://github.com/borntohonk/Atmosphere/compare/master...Atmosphere-NX:Atmosphere:master

i have rebased in the 020ed307b1c404eeb5d16949bc3ecd3b2997fa54 commit way before 1.11.1 release

the two commits i do not have, do nothing.
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  New Homebrew "Foil Server"?

Homebrew  Full List of N64 Recompilation Switch ports

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Is it fixable

Hacking Emulation  Switch Prod Keys downloading from sites okay?