Unless the SD card happens to both be accessible and contain a
`gm9/scripts` directory, a system booted with a NTR cartridge isn't going
to have access to the stock scripts and will just show an error upon
going to the menu and selecting `Scripts...`. This patch adds scripts
to the vram tarball only for ntr builds so they can be available even
on completely untouched systems. It shouldn't be necessary when we've
booted from something else because in those cases we've already written
GodMode9.firm to flash using some other means and could have copied all
the scripts then.
One might argue this is sub-optimal because the menu will point there
even if a scripts directory happens to exist on the SD card. One might
instead argue that that behavior is preferable because there's no telling
what gm9 version the scripts on the SD card were intended for.
- properly performs gpu/backlight reset
- nukes vram so the initrd had to be moved to arm9 memory, and have its size (at least temporarily) limited to 256k
Calling firmtool directly may not work as expected on Windows, where
Python is not added to PATH by default. However, the py launcher is
always added to a directory in PATH by default.
The only downside is that firmtool with Python 2 will not automatically
be called. Since Python 3.5 is required for add2tar, however, this
shouldn't be an issue.
- removed most of lodepng's optional features
- lodepng now uses the already existing CRC32 code instead of using its own copy
- fixed GIC interrupt priority
This commit adds an edited README.md to be built into GM9 as user guide.
The scrubbed parts include refs to the GM9 banner, unused MarkDown and
the whole "How to build this / developer info" block.
Links have been replaced with their corresponding anchor text, when
replacing them could be done without altering the sentences' original
meaning.
Certain parts have been further altered, such as the "License"
paragraph, which now includes the full link to GM9's "license.txt".
