Messages

I have no idea if it even works since I don't have a 6D, but it compiled, so you can test it if you want. I put in the raw_rec and mlv_rec modules with the SRM changes. And added the stubs from this thread.
https://bitbucket.org/mk11174/magic-lantern/downloads/magiclantern-Nightly.2014Jul09.6D113.zip

Please someone test this new nightly - especially do some memory tests. Additionally provide reported SRM values and if possible provide the increased values for recording time in different resoltions. Please report your findings in the SRM thread here (read the whole thread to know what this is):
http://magiclantern.fm/forum/index.php?topic=12528.msg121372

I have no idea if it even works since I don't have a 6D, but it compiled, so you can test it if you want. I put in the raw_rec and mlv_rec modules with the SRM changes. And added the stubs from this thread.
https://bitbucket.org/mk11174/magic-lantern/downloads/magiclantern-Nightly.2014Jul09.6D113.zip

Yeah I knew that it can campile as a1ex already mentioned it after posting the first stubs for 6d. Now I need to post this in 6D dev thread to get feedback. thanx for your efforts.

It would be great if you finally decide on a 6D, since this port is all but unmaintained currently, and you seem capable of keeping that port in an active state. 

Hrrrr dunno dunno. I know I can maintain 6D platform and keep nightlies up2date. I did this for android device trees, too 
Will make a decision soon and ofc whichever canon body that will be I am going to contribute as much as I can to help this great project. If anyone knows where to grab a 6D for good price (also used) in Germany or Europe then PM me.

[So now see following. These are my findings for 6D_113]

Anyone able to compile for 6D and provide it for 6D owners to test recording time increase on 6D? Indeed, increased results posted here are very encouraging. I posted necessary stubs some days ago but am still trying to decide if I buy a 6D or move with something else like 7D. This could help me in making a decision and I think other 6D owners would like to test this, too.

So now see following. These are my findings for 6D_113:

Code Select Expand

NSTUB(0xFF0F0098,  SRM_AllocateMemoryResourceFor1stJob)
NSTUB(0xFF0F40C8,  SRM_FreeMemoryResourceFor1stJob)
NSTUB(0xFFCCE714 - RAM_OFFSET,  CreateMemoryChunk)
NSTUB(0xFFCCF210 - RAM_OFFSET,  AddMemoryChunk)


If you need others then just say so....

[SRM 39 MiB]

i made some changes to mlv_rec to support this new memory interface to make some tests.
it looks very promising. here some results:

5D3 v1.1.3:
Memory details: total 277 MiB [exmem 238 MiB, SRM 39 MiB] in 89 slots

7D v2.0.3:
Memory details: total 371 MiB [exmem 182 MiB, SRM 188 MiB] in 164 slots

600D v1.0.3:
Memory details: total 129 MiB [exmem 67 MiB, SRM 62 MiB] in 44 slots

this is another powerful push. thanks a lot, alex

after posting the missing stubs for 6D (see above), can anyone verify "SRM job total" for 6D? Could I find this out myself in QEMU w/o owning the cam?
Congrats dmilligan 250MB sounds amazing

180 - 250Mb sounds amazing....

[So now see following. These are my findings for 6D_113]

So now see following. These are my findings for 6D_113:

Code Select Expand

NSTUB(0xFF0F0098,  SRM_AllocateMemoryResourceFor1stJob)
NSTUB(0xFF0F40C8,  SRM_FreeMemoryResourceFor1stJob)
NSTUB(0xFFCCE714 - RAM_OFFSET,  CreateMemoryChunk)
NSTUB(0xFFCCF210 - RAM_OFFSET,  AddMemoryChunk)


If you need others then just say so....

Thanks, you will probably have to find a few more tonight

No problem I am continuously watching commits on butbucket...

[Here you are. These are for 6D_113]

hm i dont have a recent 6D firmware dump i could use to find the stubs.

Here you are. These are for 6D_113:

Code Select Expand

NSTUB(0xFF0F0098,  SRM_AllocateMemoryResourceFor1stJob)
NSTUB(0xFF0F40C8,  SRM_FreeMemoryResourceFor1stJob)

awesome! Once this allows faster shutter speeds it will become even more fun to experminet with. I could think of some useful cases in conjunction with flash to bypass some restritions with flash sync speed...

Yes, I tried to search to find dupicates.
No, I couldn't try myself as I have still no cam so scratch that if it's not possible or already done.

Could dual iso be of any use to improve low light shutter speed and get a correct exposed picture after postprocessing? As I know dual iso improves DR. You have to post process the outcome to get a nice looking improved picture.

Now take this. let's assume I have no image stabilization in my lens. I have no flash or can't use it. I would have to expose let's say a picture at iso 3200 and 1/5th of a second with an attached lens. Could dual iso be of any use here? Let's say I set "low light dual iso" in camera and now I could take the shot with iso 800/3200 (or whatever) and 1/40th of a second. thi would avoid blurry image by hand shake and the outcome would be dark. But after post processing I get the same look (not HDR alike) like shot without dualiso and normal iso 3200 and 1/5th.

So using it for overriding camera values when operating in "aperture priority mode" in low light to get faster shutter speeds and postprocessing afterwards on pc. Hope you got what i am thinking of. Some might ask why not simply set iso to 6400 or anything like that. It's just an idea of myself if dual iso can be of any use in such situation.

There is a reason why I'm asking for people to compile this test themselves. The test results are not the only thing I'm looking for - I'm also looking for potential contributors, to keep the project alive.

Got my 6d delivered but had to send it back immediately cause battery and battery door cover were missing. 6D had been sold as almost new to me but looked like crap when it arrived. hopes were high. price was to good to believe. Got my money back now and looking for another used one as I cannot spend money for a new one. Have to spend what i got from selling my Nikon D7000 equipment.

dunno if that's used on 6D but noticed getTaskname in latest commits on 600D and have ssen it in 5d 123. If used on 6D then it should be:

Code Select Expand

NSTUB(0xFFCCCDF0, GetTaskName)

[You were right]

Hmm sorry neither have QEMU up & running nor do I hold an 6D in my hands. Build environment is broken atm. Just ordered a 6D and tried to find some stubs via learning by doing while waiting for it to arrive. You were right I flipflopped some values but I think it should now be ok for FIO_SeekSkipFile and SetTimerAfter and the rest. Can you or anyone confirm?

Code Select Expand


/** File I/O **/
NSTUB(0xFF3327F0,  FIO_SeekSkipFile)

/** GUI timers **/
NSTUB(0xFFCD1890 - RAM_OFFSET,  SetTimerAfter)
NSTUB(0xFFCCB328 - RAM_OFFSET,  SetHPTimerAfterNow)         
NSTUB(0xFFCCB418 - RAM_OFFSET,  SetHPTimerNextTick)         
NSTUB(0xFFCD1A90 - RAM_OFFSET,  CancelTimer)               

/** Task info **/
NSTUB(0xFFCCCDF0, GetTaskName)


NSTUB(0xFF1A9E80,  gui_massive_event_loop)             //not used on 6D

Here you go for the missing stubs for 6D_113. Someone please commit 'em:

Code Select Expand

/** File I/O **/
NSTUB(0xFF3CE674,  FIO_SeekSkipFile)


/** GUI timers **/
NSTUB(0xFFABDF40 - RAM_OFFSET,  SetTimerAfter)
NSTUB(0xFFCCB328 - RAM_OFFSET,  SetHPTimerAfterNow)          // 1st sub called before [DL Error] startNormalSpeedADC. For EOS_6D_113 this is sub_007E44. Add RAM_OFSET to it and you get FFCCB328
NSTUB(0xFFCCB418 - RAM_OFFSET,  SetHPTimerNextTick)          // 1st sub called before [DL Error] normalSpeedADCCBR. For EOS_6D_113 this is sub_007F34. Add RAM_OFSET to it and you get FFCCB418
NSTUB(0xFFCD1A90 - RAM_OFFSET,  CancelTimer)                // called from CancelUnaviFeedBackTimer and many others like DP_CancelTimer_AbortEndEvent and pick 2nd sub. For EOS_6D_113 this is sub_00E5Ac. Add RAM_OFSET to it and you get FFCD1A90


/** GUI **/
NSTUB(0xFF1A9E80,  gui_massive_event_loop)             //warning unsure if this is ok. looks different compared to 5d3 but shall be ok. EOS 6D_113

To answer myself. these seem to be ok after spending some time to recheck. I will post GUI timer stubs later, too.

EOS 6D V113

Code Select Expand

NSTUB(0xFF3327F0,  FIO_SeekSkipFile)

Can anyone check if that's right???

Is there anyway to extract ROM1.BIN from vendors firmware update (FIR) file?

I have the same question.

Anyone care to share ROM1.BIN of EOS 6D with me?. Just wanted to disassemble it and follow alex's "finding stubs" tutorial cause today I ordered a 6D. Might take some days to arrive and in the meantime I could try to help in finding missing stubs.