Adding feature support "File Write Task" (FWT): 52 Cams || 41 done || 11 to go - page 12 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 ... 7 8 9 10 11 [12] 13 14 15 16 17 ... 26   Go Down

Adding feature support "File Write Task" (FWT): 52 Cams || 41 done || 11 to go

  • 258 Replies
  • 96089 Views
*

Offline koshy

  • *****
  • 1096
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #110 on: 03 / October / 2014, 08:28:45 »
Advertisements
I made two 4MiB mem dumps for the A1000 just as I did with the G7 yesterday.

Edit: Did the same for IXUS 95. Will stop here though as you didn't say yet if it's useful.
« Last Edit: 03 / October / 2014, 08:34:16 by koshy »
Logged
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: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #111 on: 03 / October / 2014, 08:43:39 »
Quote from: nafraf on 03 / October / 2014, 08:32:34
Please do a quick test, replace :
int vid_get_palette_type() { return 4; }
by
int vid_get_palette_type() { return 2; }
Done. A bit more legible.
Logged
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 srsa_4c

  • ******
  • 4451
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #112 on: 03 / October / 2014, 16:24:46 »
g7 100i:
Code: [Select]
void *vid_get_bitmap_active_buffer()
{
    return (void*)(*(int*)0x6ae8); //Found @ 0xff966264 - Two refs to "BmpDDev"
}Compared to a410, the fw routine @ff966264 looks the same as its a410 equivalent.

About the RAM dumps: I expected a buffer flip between the "before menu" / "after menu" states but both cases use the 1st buffer... Perhaps entering the Canon menu triggers it, I can't predict.
Logged
*

Offline koshy

  • *****
  • 1096
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #113 on: 03 / October / 2014, 17:58:02 »
Quote from: srsa_4c on 03 / October / 2014, 16:24:46
g7 100i:
About the RAM dumps: I expected a buffer flip between the "before menu" / "after menu" states but both cases use the 1st buffer... Perhaps entering the Canon menu triggers it, I can't predict.
I made a few more entering the Canon menu...
Logged
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: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #114 on: 03 / October / 2014, 18:11:33 »
Quote from: srsa_4c on 03 / October / 2014, 16:24:46
g7 100i:
Code: [Select]
void *vid_get_bitmap_active_buffer()
{
    return (void*)(*(int*)0x6ae8); //Found @ 0xff966264 - Two refs to "BmpDDev"
}Compared to a410, the fw routine @ff966264 looks the same as its a410 equivalent.
It didn't become clear if you have the A410 to compare. So... A410 works fine, screencap attached.
« Last Edit: 03 / October / 2014, 19:32:11 by koshy »
Logged
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 srsa_4c

  • ******
  • 4451
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #115 on: 03 / October / 2014, 18:23:20 »
@koshy

You should be able to determine which frame buffer is active by using chdkptp: if the overlay is correct, it's the first buffer. This method is obviously for ports that do not report the current bitmap buffer. In your latest g7 samples, "inside canon menu" has the 1st buffer active, the rest is 2nd (address is @ 0x6ae8).
I don't need more memdumps at the moment.
Quote from: koshy on 03 / October / 2014, 18:11:33
It didn't become clear if you have the A410 to compare. So... A410 works fine, screencap attached.
I have that cam, I was the one who added the support routines, so I assumed I tested it back then ;)
Logged
*

Offline nafraf

  • *****
  • 1308
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #116 on: 04 / October / 2014, 17:07:54 »
Patch for ixus95_sd1200 v2.
Previous patches did not include void *vid_get_bitmap_active_buffer().
Logged
*

Offline nafraf

  • *****
  • 1308
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #117 on: 04 / October / 2014, 17:32:14 »
a2100 palette patch.
Logged
*

Offline nafraf

  • *****
  • 1308
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #118 on: 04 / October / 2014, 18:27:42 »
patch for sx100is.
Port was rewritten using code_gen, please do a full test as done for a2100.
Thanks.
Logged
*

Offline koshy

  • *****
  • 1096
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 34 to go
« Reply #119 on: 04 / October / 2014, 19:16:54 »
Quote from: nafraf on 04 / October / 2014, 18:27:42
patch for sx100is.
Port was rewritten using code_gen, please do a full test as done for a2100.
Thanks.
Thank you. I couldn't get it to compile after applying the patch to the trunk though.

Code: [Select]
ERR-SX100IS-100C.TXT
gmake.exe[1]: *** No rule to make target `filewrite.c', needed by `stubs_auto.S'.  Stop.
gmake: *** [all-recursive] Error 1
Can you post a built version for me? FW 100C
Logged
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...)
Pages: 1 ... 7 8 9 10 11 [12] 13 14 15 16 17 ... 26   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal