This is great news.
This probably means that we can replace some other tasks too (if not all), and makes me wonder why i spent time on reversing so many routines 
I'm starting to realize just how different the 5dc is from all cameras. There is nothing else in the same group as it. The startup code is more like the 400d, while the tasks (like gui main task) seem to be more like modern DryOS cameras like the 5d2.
I do not understand 400plus very well, specifically the main event queue you guys hijack, something about event proxy or something. I have not found anything like this in the 5dc yet, it seems to be very similar to modern DryOS cameras. I think 5dplus is going to take a very similar path to MagicLantern. It's very similar to DryOS cameras, but not similar enough to port MagicLantern on it (mainly because of things like the bmp vram being half the size, so all printing routines like bmp_hexdump need to be rewritten to fit on the 5dc screen).
At the rate things are going, I'm projecting 5dplus to be available to the public by the end of this month. I've almost got the framework written for a hack, it's just a matter of finishing now. Once I have the property system figured out, that will be the last thing on the list before I begin writing a menu system and add features.
I'm excited to see what this camera can do
Here's a (not so organized) list of things I've discovered recently:
- setting ISO property above ISO3200 does not seem to have any effect, so ISO caps out a 3200.
- inbetween ISO values like iso2500 don't seem to work, it just sets it to ISO3200.
- the properties seem to work the same as in magic lantern dryos cameras, I used the values for the ISO property from lens.h of magic lantern to test the ISO stuff.
- I discovered that the maximum size for an autoexec.bin seems to be about 2mb, anything higher causes the camera to crash in play mode. This means 5dplus has plenty of room to grow for the future.
