Read about our upcoming Code of Conduct on this issue

Commit f4137afe authored by alex@thinkpad's avatar alex@thinkpad
Browse files

EOS M: enabled FRAME_SHUTTER_BLANKING_WRITE. Does it work?

To be tested with FPS override:
- in Low Light mode, shutter speed in Canon menu should be scaled (e.g. 25 -> 12.5 fps should give shutter speeds 1/100 -> 1/50, 1/4000 -> 1/2000 etc)
- in all other modes, shutter speed should match the value dialed in Canon menu

--HG--
branch : crop_rec_4k
parent 1b674d149589
......@@ -181,7 +181,7 @@
#define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x40481B20) // ADTG register 805f
#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x40481B24) // ADTG register 8061
#define FRAME_SHUTTER_BLANKING_READ (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM) /* when reading, use the other mode, as it contains the original value (not overriden) */
//~ #define FRAME_SHUTTER_BLANKING_WRITE (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)
#define FRAME_SHUTTER_BLANKING_WRITE (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)
#define LV_DISP_MODE (MEM(0x89BAC + 0x7C) != 3)
// see "Malloc Information"
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment