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

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

  • 1685 Replies
  • 838986 Views
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #480 on: 16 / October / 2011, 18:35:51 »
Advertisements
Patch file to enable colored icons on IXUS120-SD940.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #481 on: 16 / October / 2011, 19:04:56 »
Patch to fix one of the "simple" scripts recently added.   As a "C" programmer, I need to learn that in Lua,  a zero value does not evaluate to the same thing as "false".  Don't know how I missed that in the testing - probably because the uBasic version worked so I missed it when translating to Lua.  My bad.

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #482 on: 17 / October / 2011, 03:18:29 »
Patch file to enable colored icons on IXUS120-SD940.


Patch to fix one of the "simple" scripts recently added.   As a "C" programmer, I need to learn that in Lua,  a zero value does not evaluate to the same thing as "false".  Don't know how I missed that in the testing - probably because the uBasic version worked so I missed it when translating to Lua.  My bad.



Both added in changeset 1370.

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 ERR99

  • ****
  • 339
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #483 on: 17 / October / 2011, 18:01:32 »
Hello,

so finally i found some time to rebase my port for the A3000IS to the current trunk and create a diff file.
So please add this port for the A3000IS (FW Versions 1.00b, c and d) to the trunk.


*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #484 on: 19 / October / 2011, 04:42:59 »
Hello,

so finally i found some time to rebase my port for the A3000IS to the current trunk and create a diff file.
So please add this port for the A3000IS (FW Versions 1.00b, c and d) to the trunk.


Added in changeset 1372.

I've also added the camera to the auto-build as a BETA version.

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)

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #485 on: 22 / October / 2011, 21:55:44 »
IXUS1000-SD4500 :   firmware 1.00d & 1.00f
  • based on Bernd R's port.   
  • stubs_entry.S updated with latest sigfinder results.
  • camera_list.csv marked as SKIP_AUTOBUILD
  • NOT TESTED

Gets it off my hard drive and available for tweaking prior to inclusion in autobuild.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #486 on: 23 / October / 2011, 00:06:50 »
IXUS1000-SD4500 :   firmware 1.00d & 1.00f
  • based on Bernd R's port.   
  • stubs_entry.S updated with latest sigfinder results.
  • camera_list.csv marked as SKIP_AUTOBUILD
  • NOT TESTED

Gets it off my hard drive and available for tweaking prior to inclusion in autobuild.

Added in changeset 1382.

(Note: the included camera_list.csv patch is missing commas on many of the lines - there should be five entries on each line.)

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)

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #487 on: 23 / October / 2011, 02:14:24 »
(Note: the included camera_list.csv patch is missing commas on many of the lines - there should be five entries on each line.)
Yup - I wondered about that.  I opened the camera_list.csv with a slightly older version of Excel and then saved it after adding the IXUS1000.  I noticed a lot of "changes" in the patch file that really were not changes.  Which makes me think using .CSV as a file format might be a source of problems if people edit it with spreadsheet software rather then text editors ?
 
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #488 on: 23 / October / 2011, 02:18:08 »
(Note: the included camera_list.csv patch is missing commas on many of the lines - there should be five entries on each line.)
Yup - I wondered about that.  I opened the camera_list.csv with a slightly older version of Excel and then saved it after adding the IXUS1000.  I noticed a lot of "changes" in the patch file that really were not changes.  Which makes me think using .CSV as a file format might be a source of problems if people edit it with spreadsheet software rather then text editors ?
 

It's an easy file format to process - so long as anyone committing changes to SVN is careful it should be OK.

It's certainly a lot easier to update and add new versions to though :)

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)

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #489 on: 23 / October / 2011, 02:26:50 »
It's an easy file format to process - so long as anyone committing changes to SVN is careful it should be OK.

It's certainly a lot easier to update and add new versions to though :)
I'm with you there - the six or so separate places in Makefile for a new port took patience to find.   Still,  it will be interesting to see what the various spreadsheet programs out there do to the CSV file format ....
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal