Question about kernel
Started by
GuyOverThere
, Aug 09 2012 02:08 PM
#21
Posted 19 August 2012 - 11:04 PM
#22
Posted 19 August 2012 - 11:13 PM
equiliym, on 19 August 2012 - 10:16 PM, said:
wait, those exact pointercal values are in deadlinks kernel?? i didnt know that D: well its possible when i think about his sensitivity a bit..
Yeah, I think they're same, this is what deadlink uses:
// values from pointercal (stock 2.2.2) static int32_t msm_tscal_xscale = 17388; static int32_t msm_tscal_xoffset = -871728; static int32_t msm_tscal_yscale = 25403; static int32_t msm_tscal_yoffset = 45240; static int32_t msm_tscal_gesture_pressure = 1375; // optimized value static int32_t msm_tscal_gesture_blindspot = 30; static int32_t msm_tscal_pressure_limit = 200; static int32_t msm_haptic_feedback = 1; static int32_t msm_virtual_key_pressed = 0; // if virtual key pressed static int32_t msm_zoomhack_enabled = 1; // enable zoomhack static int32_t msm_tscal_min_jump = 30; // for dejitter static int32_t msm_tscal_max_jump = 70; // for variance
but again, this is not from the msm_ts.c hi have in his github, is from another msm_ts.c hi posted about his zoomhack patch
Here's the complete file from deadlink http://pastebin.com/f2sLQDV4
Well, I don't know if "complete", with that stock file virtualkeys doesn't work, it is not because ts_keys_size array (I tested those values and they work with vamshi's kernel) but you can see many of his implementation of virtualkeys depends on not having config_touchscreen_virtual_keys enabled, is not entirely different from what other use, however most don't require you to have touchscreen_virtual_keys off
Edited by GuyOverThere, 19 August 2012 - 11:19 PM.
#23
Posted 20 August 2012 - 03:16 PM
well it doesnt really matter, what matter is that it now works.. gratz 
Suffering-oriented programming.. "First make it possible. Then make it beautiful. Then make it fast."
if i helped please press the vote up button :3
if i helped please press the vote up button :3
#24
Posted 20 August 2012 - 03:27 PM
yeah, calibration is wonky xD but I'll see what to do about that, I'm uploading the sources to my github in case of disaster from my part
and if I get calibration less wonky then I can try again with .35 
#25
Posted 20 August 2012 - 03:35 PM
lol yeah, newer kernel is somewhat of a good thing to have 
Suffering-oriented programming.. "First make it possible. Then make it beautiful. Then make it fast."
if i helped please press the vote up button :3
if i helped please press the vote up button :3
#26
Posted 20 August 2012 - 03:35 PM
Nice to see a kernel dev after a long time..vamshi is long gone and so is deadlink 
#27
Posted 20 August 2012 - 04:02 PM
I'm not a kernel dev
, however there are a few things that can only be changed at kernel level and if you want to improve upon it or used as base for porting, then it's better to have at least a working source tree 
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users







Sign In
Create Account


Back to top









