changelog of trunk including comments / devtalk - page 14 - General Discussion and Assistance - CHDK Forum

changelog of trunk including comments / devtalk

  • 298 Replies
  • 190368 Views
Re: changelog of trunk including comments / devtalk
« Reply #130 on: 02 / May / 2013, 23:01:50 »
Advertisements
Only difference is the g10 has 128 megs of RAM where the others have 64.

Canon G10 -  The Black Tank
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 13502
Re: changelog of trunk including comments / devtalk
« Reply #131 on: 04 / May / 2013, 18:32:10 »
In trunk changeset 2756, I completely removed the  CAM_FIRMWARE_MEMINFO define. All ports were already using it since srsa added the last of the vxworks ones.

I'm am going to do this in the release branch as well. All the vxworks ones cams have been using it since 2613, and dryos has had it enabled in the trunk for much longer. I count this as a bug fix, since the malloc version was proven to cause crashes and other problems with ptp.

edit:
done changeset 2758
« Last Edit: 04 / May / 2013, 21:25:49 by reyalp »
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 13502
Re: changelog of trunk including comments / devtalk
« Reply #132 on: 04 / May / 2013, 21:47:51 »
While I'm on things I said I should put in the release branch, I've merged get_image_dir() http://chdk.setepontos.com/index.php?topic=8851.msg92341#msg92341 into 1.1, changeset 2760

I'm not going to spin this as bug fix, but it's self contained and low risk.
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3356
    • Photos
Re: changelog of trunk including comments / devtalk
« Reply #133 on: 09 / May / 2013, 04:30:23 »
Trunk revision 2764 - I've moved stubs_asm.h to include and removed all the copies from platform (242 of them).

This also required changing printf to _printf in lolevel.h for the ixis 60 & ixus 65.

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

  • ******
  • 13502
Re: changelog of trunk including comments / devtalk
« Reply #134 on: 27 / May / 2013, 15:08:25 »
In trunk changeset 2805 I've enabled CAM_STARTUP_CRASH_FILE_OPEN_FIX for all dryos cameras.

I actually meant to do this much earlier in the 1.2 development cycle, but apparently never actually did it. I'd like to move this over to the stable branch as well, but want to give it a little time in the trunk first. I was a bit concerned that early DryOS version could be incompatible, but it looks like it has been enabled back to R23. I think this means that S5is is the only earlier cam. If anyone can verify it works ok in trunk 2805, that would be appreciated.
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 13502
Re: changelog of trunk including comments / devtalk
« Reply #135 on: 02 / June / 2013, 00:23:22 »
In trunk changeset 2830 I added macros for manipulating the cached bit:

ADR_TO_UNCACHED(x)
ADR_TO_CACHED(x)
ADR_IS_CACHED(x)

I find this much clearer than doing the bit manipulation everywhere. Note this uses the gcc typeof extension to cast the resulting pointer back into whatever was originally passed in. As far as I know, this is supported in any GCC version we are likely to encounter, and anyone attempting to compile CHDK on a non-gcc compiler will have plenty of other things to worry about.
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 13502
Re: changelog of trunk including comments / devtalk
« Reply #136 on: 03 / June / 2013, 00:13:54 »
I was a bit concerned that early DryOS version could be incompatible, but it looks like it has been enabled back to R23. I think this means that S5is is the only earlier cam. If anyone can verify it works ok in trunk 2805, that would be appreciated.
An s5is user reported it works OK.
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 13502
Re: changelog of trunk including comments / devtalk
« Reply #137 on: 25 / August / 2013, 15:59:59 »
Regarding http://trac.assembla.com/chdk/changeset/3042 it seems like being able to query the value is a good thing. Otherwise a script has to try to make a call and catch the error to detect if they are enabled.

perhaps set_config_value should throw an error if you try to set it?
Don't forget what the H stands for.


*

Offline philmoz

  • *****
  • 3356
    • Photos
Re: changelog of trunk including comments / devtalk
« Reply #138 on: 25 / August / 2013, 16:04:52 »
Regarding http://trac.assembla.com/chdk/changeset/3042 it seems like being able to query the value is a good thing. Otherwise a script has to try to make a call and catch the error to detect if they are enabled.

perhaps set_config_value should throw an error if you try to set it?

get_config_value(1999) will still work.

What sort of error? A popup box for the user, or a return code for the script?

Phil.

Edit: updated config number.
« Last Edit: 25 / August / 2013, 19:44:04 by philmoz »
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

  • ******
  • 13502
Re: changelog of trunk including comments / devtalk
« Reply #139 on: 25 / August / 2013, 16:21:11 »
get_config_value(999) will still work.
Right, but if we are going to allow access by mnemonics for the rest, it would be nice to include this one.
Quote
What sort of error? A popup box for the user, or a return code for the script?
I was thinking something like luaL_error(L,"script_allow_lua_native_calls is read only"), so the script ends and the author knows that it isn't legal.

I suppose this does make iterating over the entire list slightly more complicated, but that shouldn't be a huge deal.
Don't forget what the H stands for.

 

Related Topics