Messages

Thank you for pointing out that you already released a proper "bootflag" FIR file for the 5D3; I apologize for having missed it in the original post.

Is there anything which is keeping the 5D3 from being included in the nightly builds, now that (AFAIK) the major stability issue has been dealt with?

Sorry -- I just noticed the amendment you had made to the initial message.

For anyone else reading the forum, the direct link to this is:

http://a1ex.magiclantern.fm/bleeding-edge/5D3/5D3-113-bootflag.fir

(Same basic disclaimed as a1ex gave originally -- don't use it unless you vaguely know what you're doing.)

To clarify my last post:

From what I understand about the ML booting/loading process for nightlies, there's a "loader" FIR file (which we shouldn't tamper with) and the AUTOEXEC.BIN file (which contains the actual ML code). This relies on there being a "stable" FIR release, which seem to weigh in at about 64k apiece. Right now, the only FIR releases available for the 5D3 are the ones in the alpha releases. The Alpha 3 release weighs in at well over 256k, and has no companion AUTOEXEC.BIN file. I believe that the reason for a "missing" AUTOEXEC.BIN file in the 5D3 Alpha releases were given a while back.

I tried loading a compiled version of the 5D3.113 build onto my Mark III -- but it currently ignores the AUTOEXEC.BIN file and simply loads the Alpha 3 version. I hadn't seen anyone else in the forums complaining about a similar problem, so it could be a "pebcak" thing -- but I figured I'd ask for it to be rolled into the nightlies.

Are there any chances of adding 5D3 support to the nightly builds? AFAIK, the original blocking issue which was keeping it out has been dealt with.

I've been trying to watch the commits for other models to try to make sure that the 5D3 port isn't neglected for any bugfixes or large changes. (For example, https://bitbucket.org/hudson/magic-lantern/commits/30f69a59cf275599490f66fcd20b4aa447c6bf9f was implementing a change which was done for every other model *but* the 5D3)

Perhaps this just comes with being an "unsupported" model, at the moment. I don't know what the intended release date for a "stable" 5D3 port is supposed to be, but I'll keep trying to make sure that the 5D3 port is still workable in the meantime, as best I can.