StumbleUponDiggTwitterFacebookRedditLinkedIn

With this simple update on twitter, alex from Magic Lantern announces how work is going on porting Magic Lantern for the Canon EOS 5D Mark III to the latest version of the Canon firmware 1.2.3 (which includes the full HDMI output)…

So, according to this thread over there on bitbucket.org, it turns out that there’s some good progress (tho not everything is working yet) and remember, they’re working in the “alpha” fork (meaning this is still incredibly early and potentially not stable.

And, it appears from reading thru what’s going on with the code, that there’s a heck of a lot of work and that progress might be slow and difficult… but at least there’s hope!

I cannot imagine how much work there is to accomplish there… it would seem a daunting task (and let’s pray that Canon doesn’t suddenly spring some new firmware version on the team – tho of course we all want whatever Canon would put out, but that would just seem cruel HA!).


From alex in the thread:

Status update:

  • Seems to work a little better now, but didn’t try all the stuff.

  • It’s much harder than I’ve expected. Canon changed a bunch of things on the display side (quad-buffered LiveView, digic registers changed and so on). Had to refactor a bunch of things to make the code more portable, so it needs testing on the other cameras too.

  • I have disabled fast zebras, full-screen magic zoom, brightness/contrast/saturation and some smaller tweaks; these require more investigation. Fast zebras are doable, the others… I don’t consider them essential. See commit log and features.h for detailed info.

  • Please give it a try and let me know what works and what doesn’t. Simply try every single item from the menu (with every option). I know, it takes a lot of time, but this upgrade is almost as tricky as a brand new port (if not even trickier in some aspects).

  • (reminder for myself before merging) Bump module API to prevent loading 123 modules on 113 or viceversa. For now, be careful and delete old modules when switching between firmware versions.

  • ADTG research tools will not work yet (do not try to run them on 1.2.3).

  • regarding bootflag: I have a possible fix from horshack (the author of DotTune).

Thanks Chris for doing most of the dirty work!

Bitflag?

I wrote to alex about his bitflag comment as I wanted some clarification:

I’m doing a blog post on the latest tweet about the move to the 5D3 firmware 1.2.3 – cool stuff by the way

i notice you said:
regarding bootflag: I have a possible fix from horshack (the author of DotTune).

does that mean you’re possibly getting to the point where the boot flag doesn’t need to be switched? That’d make the install much easier right?

His reply:

Nope, I might be able to turn it off safely when you want to uninstall.

Good news!

So this is great news for many – tho of course the task isn’t complete yet, but there’s a ray of sunshine on the horizon!

This has been one of the most common questions I’ve had about Magic Lantern… “what version of firmware?” and “Where do it get 1.1.3?”

So, if they can indeed get the 1.2.3 version working, we’ll all be a bit better off!

(cover photo credit: snap from the Magic Lantern site)



planetMitch

chief astronomer at planet5D LLC
Mitch "planetMitch" Aunger is the creator and mastermind behind planet5D.com

He's incredibly happy running planet5D and sharing so much joy of photography and filmmaking with his readers.

Latest posts by planetMitch (see all)