Adding new cameras, applying patches into trunk (with source code prepared) - page 68 - General Discussion and Assistance - CHDK Forum

Adding new cameras, applying patches into trunk (with source code prepared)

  • 1685 Replies
  • 824819 Views
*

Offline reyalp

  • ******
  • 14110
Advertisements
A420 for both trunk and release 1.0
I decided to designate it "alpha" because:
- I'm the only one who tested it (the "beta" releases have been downloaded 50+ times)
- Got a weird crash while testing it (photo overrides) with the reyalp-ptp-live branch (romlog seems to indicate a kernel crash involving spytask). Couldn't reproduce it...
Otherwise it should be as functional as the A430 port.
Thanks. Added in 1734,1735 and 1736.
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4451
@reyalp: thx.

Small correction for the SX210IS, as reported by new123456 here. This model has 14x zoom. Maybe that's the reason behind this flood  http://chdk.setepontos.com/index.php?topic=5045.msg82868#msg82868  :)

Code: [Select]
Index: platform/sx210is/main.c
===================================================================
--- platform/sx210is/main.c (revision 1737)
+++ platform/sx210is/main.c (working copy)
@@ -41,7 +41,7 @@
   {  62,  16200},
   {  78,  22300},
   { 102,  35900},
-  { 125,  60000},
+  { 125,  70000},
 };
 #define NUM_FL (sizeof(fl_tbl)/sizeof(fl_tbl[0]))

And a small correction for SX10 1.00c: http://chdk.setepontos.com/index.php?topic=7831.msg82906#msg82906
« Last Edit: 16 / March / 2012, 16:34:37 by srsa_4c »

*

Offline philmoz

  • *****
  • 3450
    • Photos
@reyalp: thx.

Small correction for the SX210IS, as reported by new123456 here. This model has 14x zoom. Maybe that's the reason behind this flood  http://chdk.setepontos.com/index.php?topic=5045.msg82868#msg82868  :)

Code: [Select]
Index: platform/sx210is/main.c
===================================================================
--- platform/sx210is/main.c (revision 1737)
+++ platform/sx210is/main.c (working copy)
@@ -41,7 +41,7 @@
   {  62,  16200},
   {  78,  22300},
   { 102,  35900},
-  { 125,  60000},
+  { 125,  70000},
 };
 #define NUM_FL (sizeof(fl_tbl)/sizeof(fl_tbl[0]))

And a small correction for SX10 1.00c: http://chdk.setepontos.com/index.php?topic=7831.msg82906#msg82906

Fixed these in revision 1739.

I added DNG_LENS_INFO for the SX210 so the signature finder will find the focus len table in the firmware, then used that in the main.c code.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

*

Offline blackhole

  • *****
  • 942
  • A590IS 101b
    • Planetary astrophotography
Croatian language for development and stable trunk.

Patches by waterwingz.
 


*

Offline fe50

  • ******
  • 3152
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Croatian language for development and stable trunk.
Patches by waterwingz.
Done, #1749 and #1750.

Change Summary : default motion detection scripts now loop back after each picture is taken.

By popular demand (well, at least two newbie questions ...)   I've modified the simple motion detection scripts to loop back and take pictures every time motion is detected.   Not sure if the two extra lines in each script might be considered bloat but I suggest we take that chance.


Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 14110
Added.

FWIW, for stuff like this that's pretty much the same for both branches, it's fine to just post one patch. Applying it to one and then merging to the other keeps the history of what is both trees clearer, and is no more work. Where the affected code is actually significantly different (e.g. the usb remote/kbd stuff) having independent patches is useful.
Don't forget what the H stands for.

FWIW, for stuff like this that's pretty much the same for both branches, it's fine to just post one patch. Applying it to one and then merging to the other keeps the history of what is both trees clearer, and is no more work. Where the affected code is actually significantly different (e.g. the usb remote/kbd stuff) having independent patches is useful.
Wondered about that.  Especially as the two patch files turn out to be identical in my last post  :D

Is it better to post for the stable branch and let you merge to the other or visa-versa ?

Also, I guess ports to new cameras kind of sit on the side of needing both patch files ?



Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline reyalp

  • ******
  • 14110
Is it better to post for the stable branch and let you merge to the other or visa-versa ?
Doesn't really matter, whichever one is most convenient for you.
Quote
Also, I guess ports to new cameras kind of sit on the side of needing both patch files ?
I guess so. Maybe you could split it up, so there was one common set of changes, plus a patch to clean up one or the other. Since the platform kbd.c files are new, you could just include both the files, and the rest should be pretty manageable. Don't know if any of this is worth the effort.
Don't forget what the H stands for.

Don't know if any of this is worth the effort.
I kind of thought the stable branch would freeze after it was forked off.  But the CHDK-DE and new cam stuff keeps creeping back in.
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal