Attached patch adds:- C wrapper functions TurnOnDisplay & TurnOffDisplay (wrappers for DispCon_TurnOnDisplay_FW & DispCon_TurnOffDisplay_FW)
Attached patch adds:- C wrapper functions TurnOnDisplay & TurnOffDisplay (wrappers for DispCon_TurnOnDisplay_FW & DispCon_TurnOffDisplay_FW)- Lua and uBasic function set_LCDdisplay, works the same as set_backlight; but calls new display control functions.
Quote from: philmoz on 22 / October / 2013, 07:20:35Attached patch adds:- C wrapper functions TurnOnDisplay & TurnOffDisplay (wrappers for DispCon_TurnOnDisplay_FW & DispCon_TurnOffDisplay_FW)- Lua and uBasic function set_LCDdisplay, works the same as set_backlight; but calls new display control functions.Thanks Phil. Tested okay on :1) G10 : propset 2 DryOS camera2) IXUS120_SD940 : propset 3 DryOS camera3) A1200 : propset 4 DryOS camera4) SX50HS : propset 5 DryOS cameraNice to see this post and the pause for people to test and comment. I've been criticized here lately for not accepting that a script version of this concept was "well tested" based on the author testing his own code with the same script over & over on four post-2011 cameras. As you collect real data on this, I hope it makes it into the svn. edit : found my sx50 and tested it too
I'll add it to SVN tonight or tomorrow, unless anyone has any issues.
Quote from: philmoz on 23 / October / 2013, 22:58:35I'll add it to SVN tonight or tomorrow, unless anyone has any issues.No objection.For consistency I'd prefer to stick to the lower case + underscores naming used by most of the rest of the script api, but that's just my $0.02.
Implementing for DryOS only right now is fine, but it would be desirable to support on vxworks as well.
Does not appear to be equivalent event procs on VxWorks, if the functions are there I'm not sure how easy they will be to find.I figured making it fall back to the backlight on/off was a reasonable compromise.Phil.
Quote from: philmoz on 23 / October / 2013, 23:51:55Does not appear to be equivalent event procs on VxWorks, if the functions are there I'm not sure how easy they will be to find.I figured making it fall back to the backlight on/off was a reasonable compromise.Phil.I did a good bit of my original testing on a540... edit:Again, checking in dryos only is fine for now, I can probably add the vxworks stuff later. The eventprocs should be findable just by looking for pointer to name, pointer to function pairs, which tools/find_eventproc.c can do.
Hmm, if the event procs are there with the same name I wonder why the new finsig_vxworks is not finding them?Will need to take a closer look - if you know the function addresses on a VxWorks camera that would help.
Quote from: philmoz on 24 / October / 2013, 00:09:07Hmm, if the event procs are there with the same name I wonder why the new finsig_vxworks is not finding them?Will need to take a closer look - if you know the function addresses on a VxWorks camera that would help.A540DispCon_TurnOnDisplayFFD218FCDispCon_TurnOffDisplayFFD2190CThe eventproc table containing these is at FFEF8288, which is copied to the firmware data segment in RAM as 0x5D98 and registered by sub_FFD21924 from DispDev_EnableEventProc.On vxworks, many of the event proc tables are registered like that.edit:In http://chdk.wikia.com/wiki/User:ReyalP/EventProcNotes#Driver_EnableEventProc I noted many of the ones that come from ram.
Started by Michael L General Help and Assistance on using CHDK stable releases
Started by danielkun General Help and Assistance on using CHDK stable releases
Started by bugsplatter Script Writing
Started by vihar1 « 1 2 » General Discussion and Assistance
Started by muhlisgursoy General Discussion and Assistance
