Tested the framebuffer mod on an IXUS70/SD1000 1.01a, using 1.01b from trunk-r285.
Address is 6FBC, so code in platform/ixus70_sd1000/sub/101b/lib.c reads
void *vid_get_viewport_live_fb()
{
void **fb=(void **)0x6F8C;
return fb[ *((unsigned char*)0x6F9C) ];
}
It gives consistent results, but they are not faster, more to the slower end of the spectrum.
From other posts I learn that the framebuffer when shoof(half) is pressed is not
gotten from viewport_live_fb but from viewport_fb, and that function is not changed.
Note that in the script used shoot_half is pressed when the MD routine is called.
Furthermore, there is an error in motion_detector.c,
it dumps a frame buffer of incorrect size (360x240), it should be (360x230),
apparently it uses the size of the OSD buffer (360x240), not of the viewport buffer.
W.r.t. viewport buffer size the following remark.
For the IXUS70 the size of this buffer depends on the digital zoom,
in the following way, with zf = zoomfactor, mem_size is memory size,
digital zoom starts after optical zoom 3x.
zf mem_size widthxheight
1.0 ox3CA50 360x230
3.0 3CA50 360x230
3.6 336A8 300x234
4.5 28DE8 232.5x240
5.8 1FE78 182.5x240
7.2 1A1A8 148.5x240
9.0 144D8 120x231
12. F8E8 90x236
The width and heigth are just guesses to match the size of the buffer,
and I do not understand 4.5/5.8/7.2 with those halves.
This implies that adressing of the pixels is done incorrectly
by the motion_detector.c code when digital zoon is used.
