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

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

  • 1640 Replies
  • 537526 Views
*

Offline philmoz

  • *****
  • 3164
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1430 on: 14 / February / 2015, 20:08:41 »
Advertisements
Patch file (1.4.0) to cleanup USB remote code per the discussion here : http://chdk.setepontos.com/index.php?topic=7127.msg120508#msg120508

Patch simplifies the code by removing unnecessary interlocks,  fixes some issues with debug mode, and adds a usb_sync_wait() function to Lua and uBASIC for scripting use with multi-camera setups.

Updates to the usb_force_active() function per this discussion : http://chdk.setepontos.com/index.php?topic=7127.msg120539#msg120539  deferred pending reyalp updates to kbd.c files.

For consistency the 'usb_sync_wait_flag' entry in module_exportlist.c should be '&usb_sync_wait_flag' - this generates a variable reference instead of a function reference in module_hashlist.c.

(Both generate the same code with current compilers.)

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)

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1431 on: 14 / February / 2015, 20:25:28 »
For consistency the 'usb_sync_wait_flag' entry in module_exportlist.c should be '&usb_sync_wait_flag' - this generates a variable reference instead of a function reference in module_hashlist.c.
Patch  :-X
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 12693
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1432 on: 14 / February / 2015, 20:41:30 »
done in 4003
Don't forget what the H stands for.

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1433 on: 20 / February / 2015, 20:01:34 »
Patch for S100 ND filter as discussed here : http://chdk.setepontos.com/index.php?topic=7887.msg120563#msg120563

Tested on S100.
Ported :   A1200    SD940   G10    Powershot N    G16


Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1434 on: 20 / February / 2015, 23:38:30 »
Patch to re-enable the creation of a ps.fi2 file for the S100.   Tested on the 1.02A  and thus assumed to likely work on the other versions.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 12693
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1435 on: 21 / February / 2015, 00:18:44 »
Patch for S100 ND filter as discussed here :
Added in trunk 3028, stable 4029
Quote
Patch to re-enable the creation of a ps.fi2 file for the S100.   Tested on the 1.02A  and thus assumed to likely work on the other versions.
Added in trunk 4030. As you suggested in IRC, I'll leave it there for people to try other firmware versions before enabling in 1.3
Don't forget what the H stands for.

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1436 on: 23 / February / 2015, 10:02:22 »
Patch to show gps errors (no signal, no gps info in image, ...) using the message box instead of writing directly to the screen and wait/block for a few seconds. Because of the limited string length in the message box I had to insert some newlines (only fixed english and german).

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1437 on: 28 / February / 2015, 14:48:19 »
Patch to show gps errors (no signal, no gps info in image, ...) using the message box instead of writing directly to the screen and wait/block for a few seconds. Because of the limited string length in the message box I had to insert some newlines (only fixed english and german).
This was definitely on my list of things to clean up but I'm currently traveling with almost no internet access so have not had a chance to test it.  Perhaps it would have been better to post to the forum thread for the GPS code first? I try to make it a point to submit my patches that way in case there is any discussion.

Having said that, rudi also sent me a list of things he wanted to do but can't currently find the time for. When I get back next week I'll get a combined list to the forum to discuss?
Ported :   A1200    SD940   G10    Powershot N    G16


Patch file to add codegen for the G10.  Includes the addition of filewrite.c

Tested on 1.02a and by using arm-elf-objdump to compare the new boot.o, capt_seq.o, movie_rec.o files to the originals (after tweaking chdk_disasm.c to remove some of the optimization for nullsub and double jump removal for the validation only).

Would be good to add only to unstable until the 1.03b & 1.04a are tried.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 12693
Patch file to add codegen for the G10.  Includes the addition of filewrite.c
Added, trunk 4066. Did you check remote capture, including -cont?
Quote
Would be good to add only to unstable until the 1.03b & 1.04a are tried.
Added to testing needed page. That said, diffing the files between platforms and verifying that only offsets change is probably good enough.
Don't forget what the H stands for.

 

Related Topics