The following patch hasn't been committed yet (as it doesn't affect any other model, I think it could go to both 1.1 and trunk. The patch still applies cleanly to 1.1 and almost cleanly to current trunk. The A2200 port is planned to also use this new code path.
Here's my updated patch to prevent the possibility of a SD override related crash on the Ixus850/SD800. I think this code will need some cleanup in the future - but that would require tests on cameras none of the current developers have...
Thanks for the reminder, I'll add this when I get a chance.
Another issue: I noticed changeset 1988, which made me do a little research.
CAM_FIRMWARE_MEMINFO is only activated for the following cameras:
a2100, a540, a590, d10, g10, g12, g1x, ixus310_elph500hs, s100, s95, sx130is, sx20, sx30, sx40hs
With this enabled, my usual DIGIC II test cameras showed a big performance improvement during multi file upload over CHDK-PTP (for small files: about 1-2 second/file without CAM_FIRMWARE_MEMINFO, at least five times faster with it).
That's useful info, I knew the old way was bad, but never tested how bad. This probably affects live view performance too.
Don't know how this situation should be handled:
a) enable for all DryOS (i.e. trust the sigfinder)
b) enable for all
c) enable only individually, after tests
If it's c), I have tested it on 3 cameras, patch attached.
I think turning it on for all dryos should be fine. I meant to do this before the least release but didn't get to it. In this post
http://chdk.setepontos.com/index.php?topic=2509.msg66350#msg66350 I wanted to get a few more models tested, but I expect it's OK.
For vxworks, we need to find sys_mempart_id, which I haven't finished doing for all cameras. Baring typos, I think to should be safe to turn on for all that have been found.
edit:
Added sd override fix in trunk
changeset 2029, meminfo in
changeset 2030, merged both to stable in
changeset 2031