Esato Mobile
Sony Ericsson / Sony : Software, Firmware and Drivers : All about camdriver modding (for modders)
> New Topic
> Reply
< Esato Forum Index > Sony Ericsson / Sony > Software, Firmware and Drivers > All about camdriver modding (for modders) Bookmark topic
Page <  123, ... 282930>

pietropizzi Posts: 130


On 2008-01-28 18:17:31, SonarikK510 wrote:
$s5 %0 $-5 08 #COM_EVENT(56,$w5);

Anybody can explain to me that code? ( i know, that is a sharpness param)

I don't know this codes (with $s5, $-5 and so on), only macroses such as #COM_EVENT(56,$w5), #SET_REG, and others....

So, anybody can explain what does mean
$s5 - ?
%0 - ?
$-5 - ?
08 - ?

Where i can get manual about this commands?

@ alvink83
Open main programm, open the *lng file, search a necessary text, change it, click apply, save as..... and upload to your phone, to a hidden FS



$s5 %0 $-5 08 #COM_EVENT(56,$w5);

can also write as

$s5 %0
$-5 08
#COM_EVENT(56,$w5);

$s5 %0 --> put the selected param into local Reg 5 (set)
$-5 08 --> then subtract 08 from Reg 5
#COM_EVENT(56,$w5); ---> the result will be the sharpness parameter ($w5 reads it from Reg 5)
--
Posted: 2008-01-28 18:41:35
Edit : Quote

SonarikK510 Posts: 156

pietropizzi, Ok, thanks, but what does mean Reg5? Where i can see it in a camdriver?
--
Posted: 2008-01-28 18:44:45
Edit : Quote

number1 Posts: > 500

if you mean
seq_set_prop_15 = $s5 %0
$-5 08
#COM_EVENT(56,$w5);

it's digital postprocessing settings this is the main value that can be changed 08, 08 is off

--
Posted: 2008-01-28 18:45:01
Edit : Quote

pietropizzi Posts: 130


On 2008-01-28 18:44:45, SonarikK510 wrote:
pietropizzi, Ok, thanks, but what does mean Reg5? Where i can see it in a camdriver?


From what I think is
that Reg 5 is a LOCAL Reg which is just used in that property to help calculation... So Reg 5 can be used more often

What I learned from Raidersky is that there are Regs that are stored GLOBAL like he used RegE in his protoptype. But I' not sure about that.....Raidersky help me !
--
Posted: 2008-01-28 18:58:25
Edit : Quote

jomateixa Posts: > 500


On 2008-01-28 18:44:45, SonarikK510 wrote:
pietropizzi, Ok, thanks, but what does mean Reg5? Where i can see it in a camdriver?



These regs (all from 00 to 0f I think) are used for store temp values 4 make math operations or check conditions or wherever...

If there's any stored globally I don't know.

$sX ----> 's' from 'Set'
$cX ----> 'c' from 'Check'
$dXXXX -----> 'd' from 'Delay'
...
...
etc...

$-a XX ----> Substract 'a' from XX
$+a XX ----> Add 'a' to XX
...
...
etc...

With some conditional operators and these regs you can do a lot of things


[ This Message was edited by: jomateixa on 2008-01-28 20:33 ]
--
Posted: 2008-01-28 21:28:35
Edit : Quote

jomateixa Posts: > 500

Oh sorry pizzi already answered you
--
Posted: 2008-01-28 21:35:45
Edit : Quote

petkoxray Posts: 76

How i can add or edit color corection to original driver ?
--
Posted: 2008-01-28 21:38:23
Edit : Quote

jomateixa Posts: > 500


On 2008-01-27 23:31:00, jomateixa wrote:
Hey Pros, there's a little bug when using the force flash code:


seq_set_prop_e_2 = $sb 04 // Forced ON, for service menu and production tests
$c9 08 // R5 camera version?
#COM_EVENT(5a,83) // Forced xenon 0b10000011, slow sync at beginning
$cl
#COM_EVENT(51,00) // Sensor scene "Auto 00"
#COM_EVENT(5a,9b) // FLASH_MODE 0b10001011: Flash on, RER off, sync on beginning.
$cx;


When switching to doc mode, #SET_REG(40,01) in doc macro is overrided, being AE_XENON_ISO 320 or wherever but only the first pic. If we semi-press the camera button for take another pic ISO is 100, but not in any other case. I putted a macro to force xenon ISO 100 if doc mode selected but it does nothing.

In two or three days I can spend time on it, but now I don't have the time. It should be very easy to force flash changing some register values in property 23, and it will be more elegant.

I just wanted to inform about that bug.

Cheers

[ This Message was edited by: jomateixa on 2008-01-27 22:48 ]


Fixed the bug very easily just implementing FF by forcing Reg 5 to value 03 in Property 23 (00 for R5).

Cheers

[ This Message was edited by: jomateixa on 2008-01-28 21:52 ]
--
Posted: 2008-01-28 22:48:03
Edit : Quote

Raiderski Posts: > 500

1. all register are general purpose registers - some of them are used to store data, some are free or used for calculations
2. SE called them 'platform' registers
3. we have 16 registers reg0 - regF
4. probably they are 32bit registers but in compare command ($cR VV) only first 8 bits are compared
5. you can reorganize and use them as you want

in K800 driver:

// 0, Used for macros
// 1, Used for macros
// 2, Used for macros
// 3, Used for macros

in macros like COM_EVENT, SET_REG, CHANGE_MODE etc. so, they can be used for calculations but in limited way. you will loose all values in this registers if you call any code operation or event (CO&E) macro. if you will not use CO&E macro before calculations then registers can be used for normal arithmetic operations

// 4,

it's free

// 5, Used in Property 6

looks like reserved but it's not. it's free

// 6, Used for resolution ids

reserved but can be freed. resolution ID can be retrieved by command $zR (R = platform register) and then compared with ss/vf_config_NN value

// 7, Used ACM abort flag for synchronized viewfinder images.
// 8, Used to remember ISO setting since one has to change to AE_MODE to "auto" for IS.
// 9, Firmware version, checked in init_sequence

all are reserved but can be moved to different free registers

// a,

it's free

// b, Used for Flash
// c, Used for sensor scenes

all are reserved but can be moved to different free registers or squeezed to one register only

// d, 0 => normal, burst 1 => read out pict 1 ...
// e, Image stabilization 1 => ON, 0 => OFF
// f, Image format 1 => JPEG, 0 => YCbCr

all three registers are reserved but 2 of them can be freed. all values are 0 or 1 - this is normal boolean state and only 1bit value. bit operations come in handy ($bR):

$bR BB S L

R = platform register
BB = set of bits
S = index of first bit to replace
L = amount of bits to replace

this command will copy L bits from BB (from right to left). first replaced bit will be S in register R

r1 = 0bXXXXXXX
after $b1 03 2 4
r1 = 0bX0011XX (03 = in bit notification: 0b0011)


_________________
K800 R1KG001 (driver in development)
W800 CID36 R1BD001 (driver 6.7.2)
raider.4shared.com
flickr.com/photos/raiderek

[ This Message was edited by: Raiderski on 2008-01-28 22:10 ]
--
Posted: 2008-01-28 23:09:57
Edit : Quote

jomateixa Posts: > 500



5. you can reorganize and use them as you want




--
Posted: 2008-01-28 23:17:18
Edit : Quote
Page <  123, ... 282930>

New Topic   Reply
Forum Index

Esato home