Added in revision 2725/2726 (trunk) and 2727 (release-1.1).
Note this broke the release autobuild, so I added skip_autobuild. Since I was on my lunch break, I didn't look closely, but I think it was related to changes in the trunk core that aren't in the release branch.
I encourage building before every checkin, even if it seems trivial.
My bad - normally I do build before commit; will fix it tonight if I get time.
Phil.
sorry, I forgot to say I tested in trunk only 
Anyway, here's another load of changes (yes, for trunk), this time for S100 (tested with s100 101b):
hacked loader, removed useless comments, fixed platform_camera
with the hacked loader now booting with power button short press works
fixed defines in platform_camera for correct dng generation
tested movie_rec and it works
link to patch: https://github.com/c10ud/CHDK/commit/bee5ee88f8c94a9fb6d708bde2db3f7fea9cb36c.patch
I've added this to the trunk in revision 2730.
However the S100 platform_camera.h file contains the active area and color matrices from your G15 port - is this correct?
Once you've confirmed (or fixed) platform_camera.h I'll update release-1.1.
Phil.
I'm not at home (so I cannot check if I did something wrong) but I got the active area and color matrices from the CR2->DNG Adobe conversion of a S100 raw file
Looking at the diff with the previous S100 platform_camera active area looks the same, just with numbers explicited (I guess S100 and G15 probably have the same sensor or something?)
The color matrices are different, I also remember the S100 DNG missing the calibration info, probably you looked at the wrong diff?
Anyway once I'm home I'll double check this just to be sure
p.s. While we're at it, I didn't really get what the CAM_JPEG_{WIDTH, HEIGHT} are for and which value should the hold (e.g. 4000x3000 for 12Mpix? or CAM_ACTIVE_AREA_X2-CAM_ACTIVE_AREA_X1? or else?)
