[Pipo-Project] M7Pro kernel

[TriA]

1.34.03
No touch screen

Brightness levels are ok
No problems with Wi-Fi
The rest of tested features are same to 1.34.01

[JohnThomson]

I have had a problem with my touch screen at least since Riley 2.8.1, and found that if
I plug in a USB keyboard when booting that mostly wakes up the touch screen.

[raxy]

The same bootloop as with previous kernel..
It doesn't even show a logo.
I'm testing with RileyROM 3.4.2

@d33,
do you remember when I was not able to boot on my m7p the kernel I compiled from same pipo source and you said you managed to make it boot on your m8hd ?
now we have tria facing the same situation!

We are not really sure of the quality of this source code tree until the binary we build from it proves that all the hardware components is working perfectly with it.

[d33]

1.34.03
No touch screen

Brightness levels are ok
No problems with Wi-Fi
The rest of tested features are same to 1.34.01

I'll post up two new versions - could you provide DMESGs please?

[d33]

v1.34.04

Reset CT363 - tidied GPS (option 1)

Re-uploaded at 12:07 BST

[d33]

v1.34.05

Reset CT363 - tidied GPS (option 2)

re-uploaded @ 12:07 BST

[TriA]

1.34.04 and .05 -
No OTG, BT, GPS with both kernels, I didn't notice any difference.
I flashed the 1.34.01 back and OTG was restored.

6 dmesg logs are attached.
My test sequence:
- flash a kernel
- wait for bootup
- shutdown
- power on
- wait for bootup
- get a DMESG *_power.txt
- test the features (Wi-Fi, OTG, BT, GPS...)
- soft reboot
- wait for bootup
- get a DMESG *_reboot.txt
- test the features

[d33]

v1.34.06

RE-instated GPIO requests in init

[TriA]

1.34.06
OTG is ok (mouse, flash drive)
no BT
i'm in doubt about GPS - the app eats battery just like when GPS is working, but it sees no satellites

[micmail]

For what is worth, here is my dmesg...

[d33]

For what is worth, here is my dmesg... [ATTACH=CONFIG]temp_10279_1432070847474_494[/ATTACH]

I can see it fine. What do you report regarding functionality? I see the temporary touchscreen CT363 driver loaded. What was the result?

I've rebuilt with a new CT363 driver - please only flash this AFTER succesfully flashing a stock kernel if you have a CT363 touchscreen as it doesn't write the firmware.

v1.34.07

Notes
Completely re-written CT363 support
Minor amends to init
No BT changes as I can't see a problem!!!

[TriA]

1.34.07
Bootloop with 6-seconds period

[d33]

1.34.07
Bootloop with 6-seconds period

Bugger!
Recompiled with 'old' ct363 driver

v1.34.08

[TriA]

1.34.08
This is good, except for BT and GPS

I've looked at dmesg...
Is it suspicious?

<6>[ 167.545855] [BT_RFKILL]: Enter rfkill_rk_set_power
<6>[ 167.545896] [BT_RFKILL]: Set blocked:1
<6>[ 167.572416] [BT_RFKILL]: bt shut off power

here is the last time BT is mentioned in the dmseg

[d33]

May have spotted a possible error in BT

v1.34.09

Notes:
Added more debug messages to debug
Added name to BT_wake_host GPIO