reticulatedpines

Closed by 890073910bf1ec5a43ab0546c0ff045290751f9e

This has stalled I think, and the build system has changed significantly since then, anyway - no longer needs python2.

This ticket probably becomes: - check cache / uncache logic from roms on each digic gen - document cache / uncache behaviour per gen (maybe in source, next to CACHE...

Also see IS_ROM_PTR

No idea, but I'm pretty sure it won't include object code for functions that are provably never called. However, if a function is non-static, because the symbol must be externally...

One-shot task with a delay seems an obvious approach (unless Canon repeatedly overwrites it?).

I'd have thought it was more intuitive to not update the string if "set" has minimised ML functionality. Does it matter that much which happens?

Possibly useful for diagnosis, a library for producing much more detailed stack information: https://www.mcternan.me.uk/ArmStackUnwinding/ Might want a separate ticket, depending on how hard it is to integrate.

Hmm, improved stack traces might not help much with a callback timeout. Still worth a try. Perhaps a better debugging approach would be a minimal ML with only logging facilities...

I hacked this in quickly for the 200d release. I haven't closed the ticket because it's not very neat, and again, the build will fail if you have a copy...