Messages

Thanks dmilligan for the clarification about the memory-size limit. I currently don't have the time to look into disabling features in my 600D nightly ML-builds so I disabled the cron-job and removed all builds, that are broken due to the bootloader being too big.

The build from 2015-12-21, which is the last one that should be ok in this respect, is still available.

Sorry, I didn't remove the broken binaries earlier...

The only thing I could imagine is in an emergency case to take one of the 600D ML SD cards to the 600D, format it there so I would at least be able to use the card in the 6D.

Have you tried starting the camera with the "wrong" ML version, while having the SET button pressed? I'm not sure if this ML bypass works with the wrong autoexec.bin, but if it does you could at least use the card in the other camera without ML (or format it there).

[USE AT YOUR OWN RISK]

Since the official nightly build is still not being updated, I created a small cronjob that pulls the unified branch from the magic-lantern repository and builds a new version if there have been any changes.

It is available here: https://hege.cc/magic-lantern/

I use the gcc-arm-embedded toolchain from this repository and the build seems to work fine. I have not had any obvious problems with it on my 600D, but I have not done any thorough testing. So, as always:

USE AT YOUR OWN RISK

I will probably stop providing these builds once the official nightly builds are available again.