I remember to the thread and also the repo pointing it out as the "first custom 3ds sysmodule"HorizonM doesn't have a kernel extension you dolt.
yay, I succesfully baited 5 pages of cfw war
go me
Wow HZMod also is a custom sysmodule, that doesn't turn it into an actual custom firmware, if somone presents me something like the linux 3ds project (which doesn't really do that much atm) that boots a complete different os, thats a custom firmware
well you started it Mr.Luma so don't complain about it.yay, I succesfully baited 5 pages of cfw war
go me
I remember to the thread and also the repo pointing it out as the "first custom 3ds sysmodule"
hmmIt runs a custom sysmodule with a kernel extension, that's pretty actual-cfwy to me.
?well you started it Mr.Luma so don't complain about it.
Yeah, customized is actually the best term for 3ds signature patchers, can we just take that and use it instead of custom? that would make some things clearer to some peopleI would like to propose we refer to Luma et. al as "customized firmware", since the "custom firmware" label is apparently inaccurate and we're all pedants.
How does "CFW" sound as an abbreviation to everyone?
She's still publicly available, just not on temp.The war over CFWs is quite petty.. don't blame AW for leaving the 'public' scene of things.
You missed the joke. Completely.Yeah, customized is actually the best term for 3ds signature patchers, can we just take that and use it instead of custom? that would make some things clearer to some people
Yeah, customized is actually the best term for 3ds signature patchers, can we just take that and use it instead of custom? that would make some things clearer to some people
Damnit, now you're just fucking with us.You'll probably like my next 3DS release, but it's a while away.
It's pretty neat
You'll probably like my next 3DS release, but it's a while away.
It also provides zero new functionality to end users!
Ah! Thank you for clearing that up!If the primary loader for a platform (as B9S does) provides argc/argv, all applications designed to be run on the arm9 can and should expect it -- that kind of standardization of execution environment is part of what I mean by saying it's a platform.
Luma, as far as I'm aware, complies with this in order to support payloads that rely on this standardized execution environment, as it should.
Payloads can ignore what's passed to them trivially, by simply overwriting the contents of R0 and R1 in init and thus losing argc and argv....but every chainloader should (and does, presently) comply to the standard to support the payloads that rely on it.