SX30 IS porting thread - page 10 - General Discussion and Assistance - CHDK Forum supplierdeeply

SX30 IS porting thread

  • 109 Replies
  • 33596 Views
*

Offline reyalp

  • ******
  • 13231
Re: SX30 IS porting thread
« Reply #90 on: 01 / January / 2011, 16:23:16 »
Advertisements
Does anyone have a download link for sx30 100e dump somwhere ?
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 13231
Re: SX30 IS porting thread
« Reply #91 on: 01 / January / 2011, 18:04:14 »
Comments on the patch from http://chdk.setepontos.com/index.php?topic=650.msg59036#msg59036

Some of this is for g12 as well, but I don't want a bunch of discussion in the sticky thread

for viewport buffer width, can we have a weak default function that just returns viewport width, and allows the cams that need it to override ? Would be nice to have less ifdefs scattered around the code. Looks like some places would still need extra code, e.g. histogram.

On the AF video key, would be (gui.c gui_video_af_key_enum) would be nice to not have the camera specific ifdefs, but we really need a generic way of specifying which keys cameras have.

In raw.c:
What's the deal with the gamma special case for these cams?

The double buffer raw code is also a bit ifdef spaghetti, not clear how to make it cleaner.

In kbd.h/kbd.c new keys are added, but they aren't added to keyid_by_name, so script won't be able to use them. Intentional ? I haven't really looked at the implications of adding new keys.
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3319
    • Photos
Re: SX30 IS porting thread
« Reply #92 on: 01 / January / 2011, 21:00:49 »
Comments on the patch from http://chdk.setepontos.com/index.php?topic=650.msg59036#msg59036

Some of this is for g12 as well, but I don't want a bunch of discussion in the sticky thread

for viewport buffer width, can we have a weak default function that just returns viewport width, and allows the cams that need it to override ? Would be nice to have less ifdefs scattered around the code. Looks like some places would still need extra code, e.g. histogram.

On the AF video key, would be (gui.c gui_video_af_key_enum) would be nice to not have the camera specific ifdefs, but we really need a generic way of specifying which keys cameras have.

In raw.c:
What's the deal with the gamma special case for these cams?

The double buffer raw code is also a bit ifdef spaghetti, not clear how to make it cleaner.

In kbd.h/kbd.c new keys are added, but they aren't added to keyid_by_name, so script won't be able to use them. Intentional ? I haven't really looked at the implications of adding new keys.

Thanks for taking the time to review and comment, really appreciated.
I'll take a look at the viewport stuff and see if I can clean it up (not sure about the weak function concept, will do some research).

I'm not too keen on all the #ifdef code; but I couldn't see a way to do it without breaking all the existing code.
I've got even more coming up - I'm trying to fix the variable size viewport and screen buffer window for the different image sizes (G12 has 4:3, 3:2, 1:1, 4:5 and 16:9 image sizes). Will try and do this as cleanly as possible.

The raw gamma was my attempt to improve the DNG thumbnail generation which was really bad on the SX30. This give a slight boost to darker shades and gives me a slightly better DNG thumbnail on both cameras. Happy to lose it if you want.

Hadn't seen the keyid_by_name stuff (oversight on my part), will add the new keys there.

Regards,
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 reyalp

  • ******
  • 13231
Re: SX30 IS porting thread
« Reply #93 on: 01 / January / 2011, 21:12:48 »
Thanks for taking the time to review and comment, really appreciated.
I'll take a look at the viewport stuff and see if I can clean it up (not sure about the weak function concept, will do some research).
You can look at vid_get_viewport_width (in generic/wrappers.c and lib.c for the cameras that define it) for an example. This is hacky abuse of a gcc extension...

Note that the weak version has to go in a different .o file than override version, hence having one wrappers and the other lib

Quote
I'm not too keen on all the #ifdef code; but I couldn't see a way to do it without breaking all the existing code.
I've got even more coming up - I'm trying to fix the variable size viewport and screen buffer window for the different image sizes (G12 has 4:3, 3:2, 1:1, 4:5 and 16:9 image sizes). Will try and do this as cleanly as possible.
No problem, if it can't be done another way without major surgery, I'm OK with it. OTOH, if you want to do the surgery to make things cleaner, I'm OK with that too. I'm also ok with small runtime/size penalties to reduce the ifdef mess, it's getting really nasty in some places.

Quote
The raw gamma was my attempt to improve the DNG thumbnail generation which was really bad on the SX30. This give a slight boost to darker shades and gives me a slightly better DNG thumbnail on both cameras. Happy to lose it if you want.
Chances are this is applicable to all cameras, the thumbnail code is not expected to produce quality results.
Don't forget what the H stands for.


*

Offline philmoz

  • *****
  • 3319
    • Photos
Re: SX30 IS porting thread
« Reply #94 on: 02 / January / 2011, 02:13:03 »
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: SX30 IS porting thread
« Reply #95 on: 11 / February / 2011, 08:30:54 »
So has no progress been made past a BETA version? That seems to be all I can locate for the SX30.

*

Offline whim

  • ******
  • 2040
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: SX30 IS porting thread
« Reply #96 on: 13 / February / 2011, 17:53:15 »
So has no progress been made past a BETA version? That seems to be all I can locate for the SX30.

It's in trunk, so downloads are at the Autobuild site

hth,

wim

Re: SX30 IS porting thread
« Reply #97 on: 20 / February / 2011, 11:14:55 »
Deleted.
« Last Edit: 20 / February / 2011, 11:26:59 by Microfunguy »


*

Offline fe50

  • ******
  • 3131
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: SX30 IS porting thread
« Reply #98 on: 29 / April / 2011, 00:58:51 »
Av bracketing seems to be broken in the SX30 (1.00h) port - http://chdk.kernreaktor.org/mantis/view.php?id=363

Re: SX30 IS porting thread
« Reply #99 on: 02 / June / 2011, 03:25:03 »
Hi,

it seems that there is a new Firmwareversion 1.00n out for SX30IS. My brand new Cam arrived yesterday and after trying to get CHDK running i've noticed that the Firmware is 1.00n and this doesn't match with the available ones 1.00e, 1.00h or 1.00l !

Therefore i've dumped the 1.00n Firmware manually via Scripting and you can download it here:

https://rapidshare.com/files/2708163410/PRIMARY.BIN

Hopefully someone is able to get the CHDK running with this Firmware together.

Best regards
tekknix

 

Related Topics