Adding new cameras, applying patches into trunk (with source code prepared) - page 6 - General Discussion and Assistance - CHDK Forum supplierdeeply
« previous next »
Pages: 1 2 3 4 5 [6] 7 8 9 10 11 ... 168   Go Down

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

  • 1672 Replies
  • 725701 Views
*

Offline reyalp

  • ******
  • 14003
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #50 on: 15 / November / 2008, 07:40:13 »
Advertisements
Merged. I haven't added the romlog stuff yet. I also had to do significant surgery on the sig stuff. Needs testing.
Logged
Don't forget what the H stands for.
*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #51 on: 02 / January / 2009, 00:47:48 »
IXUS850 / SD800 1.00e fix

i found it while comparing SD800 / SD900...

shooting.c diff : last tv value is "1/1600":
Code: [Select]
--- platform/ixus850_sd800/shooting.c (revision 661)
+++ platform/ixus850_sd800/shooting.c (working copy)
@@ -65,7 +65,7 @@
     {  29,  928, "1/800",  1250 },
     {  30,  960, "1/1000", 1000 },
     {  31,  992, "1/1250",  800 },
-    {  32, 1008, "1/1500",  667 },
+    {  32, 1021, "1/1600",  625 },   // ROM:FF9B5A9C 0x3FD (word) = 1021
 };

SD800 1.00e firmware:
Code: [Select]
ROM:FF9B5A68 a11250          DCB "1/1250",0
ROM:FF9B5A6F                 DCB    0
ROM:FF9B5A70 a11250_1        DCB "1250",0
ROM:FF9B5A75                 DCB    0
ROM:FF9B5A76                 DCB    0
ROM:FF9B5A77                 DCB    0
ROM:FF9B5A78                 DCW 1
ROM:FF9B5A7A                 DCW 0x4E2
ROM:FF9B5A7C                 DCW 0x3E0     // 992
ROM:FF9B5A7E                 DCW 0x3E0
ROM:FF9B5A80                 DCW 0x3EE
ROM:FF9B5A82                 DCW 0x8A
ROM:FF9B5A84                 DCW 0x8B
ROM:FF9B5A86                 DCW 0x149
ROM:FF9B5A88 a11600          DCB "1/1600",0    // <--- 1/1600 is last TV
ROM:FF9B5A8F                 DCB    0
ROM:FF9B5A90 a11600_1        DCB "1600",0
ROM:FF9B5A95                 DCB    0
ROM:FF9B5A96                 DCB    0
ROM:FF9B5A97                 DCB    0
ROM:FF9B5A98                 DCW 1
ROM:FF9B5A9A                 DCW 0x640
ROM:FF9B5A9C                 DCW 0x3FD    // <--- 1021
ROM:FF9B5A9E                 DCW 0x3FD
ROM:FF9B5AA0                 DCW 0x2710
ROM:FF9B5AA2                 DCW 0x8D
ROM:FF9B5AA4                 DCW 0x8D
ROM:FF9B5AA6                 DCW 0x155
Attached the diff...
« Last Edit: 02 / January / 2009, 07:14:54 by pixeldoc2000 »
Logged
*

Offline garnwraly

  • *
  • 1
Re: Adding new cameras, applying patches into trunk (with source code prepa
« Reply #52 on: 12 / January / 2009, 23:15:49 »
um...could anyone port chdk for a2000is?
I tried to learn through the posts but I really can't figure out what to do after loading the dump into IDA and running the scripts..
Logged
*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #53 on: 01 / February / 2009, 14:29:36 »
IXUS850 / SD800 1.00e Update #2

i've added EnterToCompensationEVF & ExitFromCompensationEVF for sd800.  8)

I'll look forward to hunt down the remaining issus with my sd900 port to include it in thrunk...  ::)
« Last Edit: 01 / February / 2009, 14:45:04 by pixeldoc2000 »
Logged
*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #54 on: 02 / February / 2009, 17:14:54 »
great work so far :)

edit: this was meant for the sd900 thread ;)

what i meant was: will prolly add to trunk soon. however, this thread he is more or less obsolete, please create a ticket in the mantis ticket browser :)
« Last Edit: 02 / February / 2009, 17:19:30 by PhyrePhoX »
Logged
*

Offline hph@

  • *
  • 3
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #55 on: 19 / October / 2009, 22:15:37 »
Help me !, i need chdk for A1100-fw GM1.00b
Adj.ver : 004.010
Is firmver : 2.11
Is paranver : 2.07
Logged
*

Offline barberofcivil

  • ****
  • 268
    • deviantART Gallery
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #56 on: 18 / November / 2009, 11:55:46 »
A small patch to fix an annoyance I thought I'd share.

I found I was trying to watch propcases with the debug, but every time I restarted, the page got set back to 0.
This patch adds the propcase page to the conf file.

*EDIT* fixed my patch so it's MUCH smaller.
« Last Edit: 27 / November / 2009, 16:30:28 by barberofcivil »
Logged
*

Offline barberofcivil

  • ****
  • 268
    • deviantART Gallery
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #57 on: 27 / November / 2009, 16:27:01 »
I fixed my extended shutter speed Diff patch from here http://chdk.setepontos.com/index.php/topic,4392.15.html to be smaller.
« Last Edit: 27 / November / 2009, 16:28:59 by barberofcivil »
Logged
*

Offline barberofcivil

  • ****
  • 268
    • deviantART Gallery
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #58 on: 02 / December / 2009, 09:01:35 »
Based on my conversation on the CHDK-Shell thread (http://chdk.setepontos.com/index.php/topic,845.msg43820.html#msg43820) and my exoeriences with the autobuilding of reference signatures and stubs_entry.c, I have prepard a patch that adds to the compiling functionality.  Currently, if the reference dump binaries are present in /tools, the compiler will always use the signature generator and build signatures_vxworks.h/signatures_dryos.h.  Likewise, if the PRIMARY.BIN firmware dump for the model(s) being coompiled is present, the stubs_entry.c file will always be rebuilt.  This means that to turn off rebuilding either of these, the binaries need to be removed or renamed so the compile rdoesn't see them.
To simplify this, the attached patch adds the OPT_UPDATE_STUBS and OPT_GEN_SIGS compile options.  When enabled (in buildconf.inc), the stub/sigs will be rebuilt (if binaries are present, i.e., current operation).  If not enabled, the compiler ignores stub/sig rebuilding regardless of if the binaries are present.


Logged
*

Offline reyalp

  • ******
  • 14003
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #59 on: 02 / December / 2009, 22:38:49 »
Hmm, I used PRIMARY_ROOT to control building of stubs, which has the added advantage you can nuke your working copy without touching your primaries (and you only need one primaries tree for any number of working copies).

I was going to add an option to use the primaries for the reference bins, which would make PRIMARY_ROOT control both if set.

I guess we can add your options too, if people want to keep the primaries in their source tree.

edit:
I guess you might want to generate stubs without regenerating sigs each time, to speed up building, so options to control them individually are good.

edit 2:
Ok, I've committed this as changeset 851 with the following modifications
- OPT_UPDATE_STUBS is renamed to OPT_GEN_STUBS
- both OPT_GEN_STUBS and OPT_GEN_SIGS default to one, so previous behavior is preserved by default. Note that you can still undefine them on the make command line (e.g. make OPT_GEN_STUBS= clean fir) to turn them off, or override them in localbuildconf.inc

edit 3:
In  changeset 852, I've added the propcase page thing. I also made it save the misc debug vals option.
« Last Edit: 03 / December / 2009, 01:33:48 by reyalp »
Logged
Don't forget what the H stands for.
Pages: 1 2 3 4 5 [6] 7 8 9 10 11 ... 168   Go Up
« previous next »
 

Related Topics