What I found was that 'init_file_modules_task' was not getting hooked at startup unless I added a delay when the keyboard task was being hooked (have at look at what I implemented in boot.c for these cameras). I still haven't figured out why this is needed; but it seems to work for me.
I've already tested some different values for:Code: [Select](int*)0x1938=(int)taskHookAFAIK 0x1938 is software irq?
What I've found is that having two addresses pointing to taskHook as shown below fixes my problem without the need for the startup delay - so ignore my previous post (thanks for the hint ).Code: [Select](int*)0x1938=(int)taskHook(int*)0x193C=(int)taskHook
ASSERT!! FsIoNotify.c Line 457Occured Time 2011:02:19 02:26:01Task ID: 1441797Task name: SpyTaskSP: 0x0037D000StackDump:0x000000000xFF86EA840x000001C90x000000000x000000030x000200000x0018DCF40x199802180x199802180x199802180x199802180xFF86EBA80x000200000x0018DCF40x000000030x000000000x199802180xFF86F1840x0018DCF40x000000AF0x0017B4E40x199802180x199802180x001622700x00168AD50x000000030x000000040x000000050x000000060x0018DCF40x000000AF0x0017B4E40x199802180x00152F6B0x0017C2900x001532D70x0018A29C0x000000160x000001910x001533990x000000440x0000D2730x0018A29C0x000000160x000001910x199802180x199802180x199802180x0018A29C0x000000160x000001910x199802180x0014B5110x003727080x199802180x199802180x199802180xFF816AEC0x199802180x199802180x00000208ShootConDump:0f 0f 0f 0f 0f 0f 0f 0f 0f 0f CameraConDump:07 0f 0f 0f 0f 0f 0f 0f 0f 0f 00000160: *** Camera Log Start ***00000200: UI:LogicalEvent:0x5001:adr:0,Para:000000260: SS:S-Imag00000260: UI:ScreenLock00000260: UI:ScreenUnLock00000270: UI:LogicalEvent:0x300a:adr:0,Para:000000270: UI:HDMIConnectCnt00000270: UI:PB.Create00000270: UI:DispSwCon_TurnOnBackLight00000270: UI:TurnOnBackLight00000300: UI:LogicalEvent:0x5006:adr:0,Para:000000430: UI:DispSwCon_MuteOffPhysicalScreen00000430: UI:MuteOffPhysicalScreen00000430: UI:LogicalEvent:0x3138:adr:0,Para:000000440: UI:LogicalEvent:0x112c:adr:0,Para:000000460: UI:ScreenLock00000460: UI:ScreenUnLock00000480: UI:PB.CreateE00000480: UI:AC:StartPB00000480: UI:DispSwCon_TurnOnDisplayDevice00000480: UI:AC:EBtn00000480: UI:PB.Start00000480: UI:DSIC:47,000000480: UI:CC_CompFlhJpg00000480: UI:_CompFlhJpg00000480: UI:PB.Flash00000480: UI:ScreenLock00000490: UI:DSIC:47,000000490: UI:ScreenUnLock00000520: UI:Button:0x00001004:UnpressPBButton
Quote from: pixeldoc2000 on 01 / February / 2011, 14:10:50We have to check if override cause any change:1. image processing2. exif data3. nothingAFAIK it common override image processing does work, but exif doesn't reflect changes.Best to go with big differents in settings, so its easier to spot any changes to image.Here there is a sample of my resultsTV mode, on the left I choosed iso 16, on the right iso 125. Both are from TV mode 10'' http://img695.imageshack.us/i/iso125iso13.jpg/I tried some more times and it seems that the image quality is better both in raw and in jpg using iso 16 (that I obtained requiring ISO 20).
We have to check if override cause any change:1. image processing2. exif data3. nothingAFAIK it common override image processing does work, but exif doesn't reflect changes.Best to go with big differents in settings, so its easier to spot any changes to image.
Started by Packhorse
Hotwire! Hardware Mods, Accessories and Insights
Started by gene
Started by mojo43
General Discussion and Assistance
Started by eXistenZ
Started by Bernd R
« 1 2 3 »
General Discussion and Assistance