[Pipo-Project] M7Pro kernel

[stevejc]

I agree to start back from 1.03,
but it seems that your repo does not have it, just 1.05 if i understand correctly what I see..

see on other threads, I have extracted

Maybe yo can try on your tablet the 1.05 because mine malfunctions a little !

[raxy]

ok, so the idea is to use 1.05 code with .config extracted from 1.03 kernel.img

[raxy]

find attached zip kernel built from 1.05 code with 1.03 config for m7pro;

for the record, time command around make said :
real 34m15.347s
user 22m28.900s
sys 1m39.296s

I know, do not laugh, my linux box is weak...

differences between logs when building with 1.03 and 1.05 configs are only :

1009,1014d1008

<   CC      drivers/input/gsensor/lis3dh.o
<   LD      drivers/input/gsensor/built-in.o
<   CC      drivers/input/gyroscope/l3g4200d.o
< drivers/input/gyroscope/l3g4200d.c: In function 'l3g4200d_probe':
< drivers/input/gyroscope/l3g4200d.c:755:8: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized]
<   LD      drivers/input/gyroscope/built-in.o

[raxy]

I've pushed my latest code so suggest you pull and re-compile
...
Currently using the toolchain provided in the SDK (4.6 non-hf) to ensure complete compatibility with Pipo until we are happy everything is working to our satisfaction. For all other kernel sources I use the latest linaro (4.8.2 HF)

Hi,
I've taken my 32bit toolchain 4.7 binaries from here :https://github.com/boeboe/android_pr...oolchain_32bit

To correctly set my toolchain path,
no need to mod the Makefile at the root of your repo,
I just did..
export CROSS_COMPILE=<whatever_is_your_path>/bin/arm-eabi-
before doing any make..

Works for me at least, and on our (priv) kernel repo

[d33]

Test kernel 1.06

Pushed to Git

[stevejc]

Test kernel 1.06

Pushed to Git

got same problem with touch screen, will do a report soon (need to charge it a little)

[d33]

got same problem with touch screen, will do a report soon (need to charge it a little)

Was hoping that at least it was all in same direction now and "all I needed to do" was fix the touchscreen to fix full screen

[stevejc]

Was hoping that at least it was all in same direction now and "all I needed to do" was fix the touchscreen to fix full screen

The touch event seems very strange, I don't have a continues touch like before, it jumps when I slide my finger (I have set the visual feedback for touches)

And screen orientation is reverse like before.

[d33]

The touch event seems very strange, I don't have a continues touch like before, it jumps when I slide my finger (I have set the visual feedback for touches)

And screen orientation is reverse like before.

It's important to be clear. You suggested that x-axis was ok in 1.03 and y-axis was still reversed.

Can you compare 1.03 and 1.06 and give me an idea as to how I can progress? Thanks

[d33]

Please compare this kernel (v1.07) with v1.06 and let me know how to proceed

[stevejc]

Please compare this kernel (v1.07) with v1.06 and let me know how to proceed

With 1.06, touchscreen not working well as is not continious.

With 1.07, touchscreen is reversed :
(left to right) -> (down to up)

(down to up) -> (right to left)

And the width zone is not all the screen, only right part of the screen has touch input when in landscape mod with button up.

When I touch the screen from right to left the cursor start from the 1.5 cm from the top of the screen.


And always, landscape and portrait mode are reversed : need a 90° counterclockwise to be OK.

[d33]

Steve,

If you are okay to build and test yourself then take "config.m7pro.1.06" and copy to .config then:

1. Change the orientation settings in the board file (arch/arm/mach-rk3188/board-rk3188-ds1006.c) on line 493

2. Set the config for touchscreen (Device Drivers -> Input Device Support -> Touchscreen -> VTL36x Touchscreen) to "use new touchpoint structure" ON, Swap x,y ON, reverse x OFF reverse Y OFF

Try experimenting from there

[stevejc]

Steve,

If you are okay to build and test yourself then take "config.m7pro.1.06" and copy to .config then:

1. Change the orientation settings in the board file (arch/arm/mach-rk3188/board-rk3188-ds1006.c) on line 493

2. Set the config for touchscreen (Device Drivers -> Input Device Support -> Touchscreen -> VTL36x Touchscreen) to "use new touchpoint structure" ON, Swap x,y ON, reverse x OFF reverse Y OFF

Try experimenting from there

I have set the same options except Reverse x ON and now touchscreen is in correct order but not all the screen is mapped (like before)

And I can't reverse orientation even when changing the file you tell me.

[d33]

I have set the same options except Reverse x ON and now touchscreen is in correct order but not all the screen is mapped (like before)

And I can't reverse orientation even when changing the file you tell me.

The ts driver is configured for 1920x1200 so it's not that that is wrong. You can turn on CT36X_TS_EVENT_DEBUG in tscore.h (change from 0 to 1) to track touch points and see what values are reported.

[d33]

Test this one v1.08