SX200is Porting - page 41 - DryOS Development - CHDK Forum
« previous next »
Pages: 1 ... 36 37 38 39 40 [41] 42 43 44 45 46 ... 111   Go Down

SX200is Porting

  • 1105 Replies
  • 571934 Views
*

Offline smartkiller

  • ***
  • 139
Re: SX200is Porting
« Reply #400 on: 22 / September / 2009, 13:40:03 »
Advertisements
I have Found the SX200 options for the Bracketing in Custom Timer.
I read it with the Debug Funktion.

Code: [Select]
223 Timer Mode (0,1,2,3,4 = Off, 2 Second, 10 Second, Custom, Face detection)
102 RO Drive Mode (0,1,2 = single, continuous, AF Row)

Ihar can you fix it in the raw.c ?

Here http://chdk.wikia.com/wiki/PropertyCaseDump can you found a lua script to log the changes when Timer or Row is set!

Smartkiller
« Last Edit: 22 / September / 2009, 14:05:37 by smartkiller »
Logged
SX200 IS Firm. 100c
SX1 IS Firm. 201a
*

Offline ihar

  • **
  • 55
Re: SX200is Porting
« Reply #401 on: 22 / September / 2009, 15:13:39 »
sorry, but have one problem.

usualy:
102    RO    Drive Mode (0,1,2 = single, continuous, custom timer)

sx200is
102    RO    Drive Mode (0,1 = single, continuous)

I it and rules:)
Logged
*

Offline ihar

  • **
  • 55
Re: SX200is Porting
« Reply #402 on: 22 / September / 2009, 17:25:20 »
New change

insert in canera.h in sx200settings

Quote
#undef CAM_HAS_ZOOM_LEVER
#define CAM_AF_SCAN_DURING_VIDEO_RECORD 1

for activate opticalZoom by button down in video_record and focus set by button

Ihar
« Last Edit: 22 / September / 2009, 17:47:20 by ihar »
Logged
*

Offline ihar

  • **
  • 55
Re: SX200is Porting
« Reply #403 on: 22 / September / 2009, 17:30:11 »
 
Quote
# Optical zoom in movie record requires "zoom out" after starting record for it to work: Open
I fixed :)

Ihar
Logged
*

Offline reyalp

  • ******
  • 14126
Re: SX200is Porting
« Reply #404 on: 23 / September / 2009, 00:48:49 »
Ok, I've got everything in a trunk working copy and starting going through it. A few questions
- 100c and 100d directories appear 100% identical (except a stray item in stubs_auto.S that goes away when I rebuild). Is there any reason not to make a copy of the final binary, like the other identical ports ? This makes maintenance easier.

- in edgeoverlay.c and gui_osd.c someone has added draw_txt_string calls with various debug messages, but this will not really be effective since they will only last until the next display update. Are they actually useful ?
Logged
Don't forget what the H stands for.
*

Offline smartkiller

  • ***
  • 139
Re: SX200is Porting
« Reply #405 on: 23 / September / 2009, 00:53:04 »
Code: [Select]
[quote author=ihar link=topic=3994.msg40208#msg40208 date=1253646819]
sorry, but have one problem.

usualy:
102 RO Drive Mode (0,1,2 = single, continuous, custom timer)

sx200is
102 RO Drive Mode (0,1 = single, continuous)

I it and rules:)
[/quote]

102    RO    Drive Mode (0,1,2 = single, continuous, custom timer) I have found this Options with debug Mode.

102    RO    Drive Mode (0,1 = single, continuous) that must have other Cams.

Smartkiller
« Last Edit: 23 / September / 2009, 01:52:55 by smartkiller »
Logged
SX200 IS Firm. 100c
SX1 IS Firm. 201a
*

Offline smartkiller

  • ***
  • 139
Re: SX200is Porting
« Reply #406 on: 23 / September / 2009, 01:01:53 »
Quote from: reyalp on 23 / September / 2009, 00:48:49
Ok, I've got everything in a trunk working copy and starting going through it. A few questions
- 100c and 100d directories appear 100% identical (except a stray item in stubs_auto.S that goes away when I rebuild). Is there any reason not to make a copy of the final binary, like the other identical ports ? This makes maintenance easier.

- in edgeoverlay.c and gui_osd.c someone has added draw_txt_string calls with various debug messages, but this will not really be effective since they will only last until the next display update. Are they actually useful ?

Hallo
I mean that the 100c and 100d are identical. (Works with the Firmware Versions)
Firmware 100d owners must be confirm it.

@Ihar  Can you update your Profile, so we can see what Firmware you have?


Smartkiller
Logged
SX200 IS Firm. 100c
SX1 IS Firm. 201a
*

Offline OldGit

  • ****
  • 303
Re: SX200is Porting
« Reply #407 on: 23 / September / 2009, 01:58:09 »
Quote from: reyalp on 23 / September / 2009, 00:48:49
Is there any reason not to make a copy of the final binary, like the other identical ports ? This makes maintenance easier.
@reyalp,
the 100D is an exact copy of 100C, it was kept seperate during development so Darkness could check memory addresses.
He has not found any, so I would say we should only publish only 1 port to cover both versions.

Thanks for your help on this.

OldGit
Logged
SX200 IS-100C
*

Offline OldGit

  • ****
  • 303
Re: SX200is Porting
« Reply #408 on: 23 / September / 2009, 02:03:04 »
Quote from: smartkiller on 23 / September / 2009, 01:01:53
I mean that the 100c and 100d are identical. (Works with the Firmware Versions)
Firmware 100d owners must be confirm it.
@smartkiller,
we should publish the 100C as is.
If we then find that 100D users get problems that 100C users do not, then we can just copy the source to 100D and alter.
But we have not found any difference in the firmware dump that would suggest a need for a seperate port.
OldGit
Logged
SX200 IS-100C
*

Offline OldGit

  • ****
  • 303
Re: SX200is Porting
« Reply #409 on: 23 / September / 2009, 02:11:55 »
@wim
regarding the root makefile diff and lf/cr.
We had problems with this file before, it should only have 6 new lines (for the sx200) that are different.
I will try to clean it up for you.
Thanks, OldGit
Logged
SX200 IS-100C
Pages: 1 ... 36 37 38 39 40 [41] 42 43 44 45 46 ... 111   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal