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

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

  • 1679 Replies
  • 790845 Views
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #650 on: 24 / February / 2012, 20:24:08 »
Advertisements
Patch file 9 for USB remote v2 update.  Allows cameras with separate video button to activate filming via USB remote.

Thanks to msl for making this happen.

Added in revision 1694.

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 #651 on: 25 / February / 2012, 13:06:40 »
Okay - here's another orphan camera that should go into the svn as an alpha - the sx210is.

Based on the latest code in the forum <link here>, I got these to build against both trunks and have posted the executables to the porting thread to see if someone will test them.

There as a couple of funky things with this port.   

It wanted to create a propset5 but from the quick look I took,  it seemed that was mostly because it started as propset3 and changes were made that seemed to result in something a lot like propset4.  So I just changed it to use propset4.

I changed the stubs_entry_2.S file to not override addresses found by the new sig finder.  However,  there is something goofy going on with boot.c - several  ROM subroutine addresses were added manually to stubs_entry_2.S because they were not picked up during the compile process.  Some sort of address range issues ?

There are a few stubs_entry.S suggestions for different DEF() values.  Also,  several of the mode map values show up in stubs_entry.S as "not in current modemap".

Other than that, its a pristine port :)

Update : Deleted patch file for dev trunk as user testing says it does not run.  Updated patch for stable trunk to use propset3 rather than propset4 based on user testing.
« Last Edit: 26 / February / 2012, 15:30:17 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 14084
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #652 on: 25 / February / 2012, 15:37:42 »
It wanted to create a propset5 but from the quick look I took,  it seemed that was mostly because it started as propset3 and changes were made that seemed to result in something a lot like propset4.  So I just changed it to use propset4.
Being a dryos R43 camera, I'd expect it to be a propset3, but I suppose it's possible Canon changed mid stream (or the other R43 cams are wrong...)
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4451
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #653 on: 25 / February / 2012, 19:49:19 »
Fixes and enhancements for the A1000.
Tested on 1.00b by Nando in the German forum here.
My only real work on this was finding
enabled_refresh_physical_screen
and enabling
CAM_STARTUP_CRASH_FILE_OPEN_FIX (because of the startup failure)
all other values were already found by finsig_dryos.


Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #654 on: 26 / February / 2012, 08:57:02 »
Hello!

Might I ask to unlock math.sqrt() function in Lua? I found it usefull in calculations between tv_96 and shutter time. Currently I have to do an ugly walk around... It requires changes in /lub/lua/lmathlib.c:

  • uncomment line 262
  • lines 109-113 have to be excluded from #if 0

Forgive me that I don't attach patch, but I'm using mobile Internet and I've reached the limit for this month, so my Internet speed is to slooooow to attach anything... Even opening forum is a pain:)
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

*

Offline reyalp

  • ******
  • 14084
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #655 on: 26 / February / 2012, 15:01:32 »
Hello!

Might I ask to unlock math.sqrt() function in Lua?
Since lua numbers are integers in CHDK, I'm not sure how useful or correct this will be.

The tv96 etc values are APEX*96. I'd suggest doing all your exposure calculations in these units. See http://dougkerr.net/Pumpkin/#APEX for an excellent description of APEX.

I think someone already wrote a pure lua library for conversions, but I haven't managed to find it. This would be a good candidate for a standard library if we can find or rewrite it.

http://chdk.setepontos.com/index.php?topic=5176.msg50316#msg50316 may be useful.

Note that we could expose apex2us (apex*96 to microseconds) in lua quite easily.
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4451
Ixus220hs/Elph300hs: hiker_jon's confirmed addresses turned into a patch - affects recreview_hold and vid_get_viewport_fb_d(). See his posts from here on: http://chdk.setepontos.com/index.php?topic=6341.msg80886#msg80886

I would also like to ask something: I tried to help imtheguy in the same thread by implementing dark frame subtraction control. I tried two possible locations for capt_seq_hook_set_nr, but reportedly neither works properly (stops working after some time  ???). Has anybody experienced something like this on a recent camera? CaptSeqTask's code seems correct, I don't know what could go wrong...

And finally: the patch in my previous post here hasn't been committed yet (A1000).
Thx.

*

Offline reyalp

  • ******
  • 14084
Ixus220hs/Elph300hs: hiker_jon's confirmed addresses turned into a patch - affects recreview_hold and vid_get_viewport_fb_d().
release  changeset 1717
Quote
And finally: the patch in my previous post here hasn't been committed yet (A1000).
release changeset 1716. Thanks for the reminder.

Both merged into trunk in changeset 1718
Quote
I would also like to ask something: I tried to help imtheguy in the same thread by implementing dark frame subtraction control. I tried two possible locations for capt_seq_hook_set_nr, but reportedly neither works properly (stops working after some time  ???). Has anybody experienced something like this on a recent camera? CaptSeqTask's code seems correct, I don't know what could go wrong...
No idea, the described behavior is very strange.
Don't forget what the H stands for.


*

Offline reyalp

  • ******
  • 14084
I've been experimenting with working only in Linux on CHDK.   So I took the liberty of using mland's  A800-100.c port to exercise the linux svn commands.   I've attached a patch file for the latest build for trunk rev 1650 - the dev trunk.  Its not a Windows TortoiseSVN file so I will be curious to see if its useful ?

http://chdk.setepontos.com/index.php?topic=7409.msg81169;topicseen#msg81169

The only change that I made from his zip file was to change the case of the sub directory from 100C to 100c.
Thanks.

Added to trunk, changeset 1723. I'll look at doing the release branch later.

I only give this a brief look through, but I didn't see anything horribly wrong.
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3450
    • Photos
Okay - here's another orphan camera that should go into the svn as an alpha - the sx210is.

Based on the latest code in the forum <link here>, I got these to build against both trunks and have posted the executables to the porting thread to see if someone will test them.

There as a couple of funky things with this port.   

It wanted to create a propset5 but from the quick look I took,  it seemed that was mostly because it started as propset3 and changes were made that seemed to result in something a lot like propset4.  So I just changed it to use propset4.

I changed the stubs_entry_2.S file to not override addresses found by the new sig finder.  However,  there is something goofy going on with boot.c - several  ROM subroutine addresses were added manually to stubs_entry_2.S because they were not picked up during the compile process.  Some sort of address range issues ?

There are a few stubs_entry.S suggestions for different DEF() values.  Also,  several of the mode map values show up in stubs_entry.S as "not in current modemap".

Other than that, its a pristine port :)

Update : Deleted patch file for dev trunk as user testing says it does not run.  Updated patch for stable trunk to use propset3 rather than propset4 based on user testing.

Added to release-1.0 in revision 1725.

Not sure what you want to do about the trunk 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)

 

Related Topics