Loading CHDK in AgentRAM for a few more cameras - page 5 - General Discussion and Assistance - CHDK Forum
supplierdeeply

Loading CHDK in AgentRAM for a few more cameras

  • 73 Replies
  • 18450 Views
*

Offline nafraf

  • *****
  • 1308
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #40 on: 20 / October / 2014, 21:56:44 »
Advertisements
A3200 patch replaced EXMEM support by ARAM, we got worse results, then A3200 won't be modified.

Patch for ixus980_sd990.

*

Offline reyalp

  • ******
  • 14082
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #41 on: 20 / October / 2014, 23:02:27 »
A3200 patch replaced EXMEM support by ARAM, we got worse results, then A3200 won't be modified.
Note there should be no harm in enabling both.
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 1096
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #42 on: 21 / October / 2014, 10:51:57 »
Patch for ixus980_sd990.
That works, the largest free block in RAM is a bit larger still. It now is 1252648 bytes.

I found a palette problem in CHDKPTP for Ixus 980. But that's unrelated to this patch of course.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Offline nafraf

  • *****
  • 1308
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #43 on: 21 / October / 2014, 22:10:38 »
Thanks.
Please test if this patch fix bitmap palette on ixus980_sd990.


*

Offline nafraf

  • *****
  • 1308
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #44 on: 21 / October / 2014, 23:04:50 »
Patch for a480:
- simpler loader
- CHDK loaded in ARAM
- fwt support

This patch was tested on fwt porting thread, but memory sizes were not verified.
« Last Edit: 21 / October / 2014, 23:06:42 by nafraf »

*

Offline koshy

  • *****
  • 1096
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #45 on: 22 / October / 2014, 19:28:08 »
Thanks.
Please test if this patch fix bitmap palette on ixus980_sd990.
Yes this fixes it.

PS: If this camera can also be included in the custom color palette work I'd like that.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Offline koshy

  • *****
  • 1096
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #46 on: 22 / October / 2014, 19:36:11 »
This patch was tested on fwt porting thread, but memory sizes were not verified.
The memory size with it is a solid improvement. The largest free block is now 697616 bytes.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Offline nafraf

  • *****
  • 1308
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #47 on: 23 / October / 2014, 00:46:38 »
PS: If this camera can also be included in the custom color palette work I'd like that.
We can try to implement custom colors for ixus980, I think it is better to discuss this on ixus980_sd990 porting thread.

We need to discover the value of active_palette_buffer on rec and play mode. Please use the patch in attachment, and enable Misc values (CHDK menu -> Miscellaneous Stuff -> Debug Parameters -> Show Misc. Values [ x ] )
Please tell me the value of active_palette_buffer (APB) on rec and play mode.

Additionally, please post an image of palette on rec and play mode. (CHDK menu -> CHDK Settings -> Color Settings -> Draw Palette).

 Thanks


*

Offline koshy

  • *****
  • 1096
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #48 on: 23 / October / 2014, 13:51:35 »
I think it is better to discuss this on ixus980_sd990 porting thread.
I took it and the reply there.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Offline koshy

  • *****
  • 1096
Re: Loading CHDK in AgentRAM for a few more cameras
« Reply #49 on: 23 / October / 2014, 14:12:15 »
On A2100 I had used my latest version in the original report so the numbers on page 1 were with ARAM already as we had added loading to ARAM on the FWT thread. Largest free block without was 780664 bytes and with is 973008 bytes. Here is more verbose info:

Code: [Select]
!return con:execwait[[return get_meminfo'system',get_meminfo'aram',get_meminfo'exmem']]
={
 start_address=1390224,
 allocated_count=1452,
 chdk_size=149308,
 total_size=1699344,
 free_size=782632,
 end_address=3089568,
 allocated_size=904984,
 allocated_peak=964224,
 free_block_max_size=780664,
 chdk_start=2176580,
 free_block_count=15,
 chdk_malloc=true,
 name="system",
},false,false

CHDK loaded to ARAM
Code: [Select]
!return con:execwait[[return get_meminfo'system',get_meminfo'aram',get_meminfo'exmem']]
={
 start_address=1240920,
 allocated_count=598,
 chdk_size=150912,
 total_size=1848648,
 free_size=983448,
 end_address=3089568,
 allocated_size=860352,
 allocated_peak=916856,
 free_block_max_size=973008,
 chdk_start=2027276,
 free_block_count=9,
 chdk_malloc=true,
 name="system",
},{
 start_address=3616128,
 allocated_count=870,
 chdk_size=150912,
 total_size=53888,
 free_size=672,
 end_address=3670016,
 allocated_size=53136,
 allocated_peak=53824,
 free_block_max_size=576,
 chdk_start=2027276,
 free_block_count=5,
 chdk_malloc=true,
 name="aram",
},false
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

 

Related Topics