rk3188 tablet kernel sources

[dnkn]

Hello dnkn;

Do you have a overclocked kernel faster than 528 + lower brightness? I'm looking to try the fastest kernel with lower brightness and I don't really care aboot battery life all that much; as long as it doesn't fry the tablet

Which kernel has lower brightness; post 39 or 40?

Thanks!

Both, its the same image, but from #40 it has been rkcrc'd (may be needed for flashing from windows).

As for more freq, look in RileyRom2.0 thread, I posted 696mhz DDR version there.

And I'm on pause for some time. All this work took too much time, I need to do my everyday tasks.

And need to make some power efficiency tests, looks like it nearly doubled.

[leolas]

Kernel work in stick without the device is a nightmare, in tablets is more difficult yet, more hardware to setup that in the sticks, if you are not familiarized with kernels, I suggest phjanderson tool to patch stock kernel: http://www.freaktab.com/showthread.p...rk3188-kernel!

With this tool you can patch your stock kernel and add some overclocking and more.

And agree with dnkn, work to make a kernel requires a lot of time, and if you are not a code master (my code capabilities sucks) more yet.

[Vibsi]

Thank you DNKN for breathing back new life in this tablet. I was at the verge of trading it for another device, since a have some issues with it.

My biggest problem is WiFi - with stock or RR WiFi sometimes comes not back when I wake up the tablet or it disconnects during use. I do not have this problem when I flash OMA's CM10.1 with the latest stock kernel. CM10.1 shows wrong values for the reception but it never disconnects.
I also noticed that other devices discover 5-8 WLANs around me, the M9 often only 1-3.
I will check if it runs better with your kernel.

I noticed that your kernel.img is only half the size of the stock kernel (4 compared to 8 MB). On the other hand, the 7-zipped size of a kernel.img archive is bigger than stock (4 compared to 3MB)
What is the reason for this big difference?

I'm also a big fan of the SlimROMs - I use one for my Galaxy SII. Is there any chance of development of a SlimROM now that the kernel sources are available? What would one have to do to develop a SlimROM version for the M9? Also a CM edition for the M9 would be nice since we do not longer depend on PiPO to release undocumented stock ROMs (do that guys ever learn what a change log is?).

So once again - thanks for sharing your hard work and I'm looking forward what will come next for this great device.

[dnkn]

Can i flash 696 kernel on pipo m9 4.1.2 rom? thk

Not tested with 4.1 only with 4.2.2

[P.A]

Flash the 696 kernel with Riley Rom 2.1, the rom boot up ok but the touch screen is not responding any idea?

What about stock? Is working? Maybe your example of tablet requires higher voltage, that lowered ones in non-stock kernel. Maybe dnkn should increase it a little bit to make this kernel mass usage ready.

[P.A]

the default 2.1 rom kernel work ok, the 696 and oc kernel it boot up to the lock screen but the touch screen not responding

You flashed it like in image below?




By doing that, kernel from post 40 will be flashed

http://www.freaktab.com/showthread.php?7732-rk3188-tablet-kernel-sources&p=108376&viewfull=1#post108376

[d33]

DNKN,

Firstly - superb work!

Second, I think I've worked out the display on the M8HD, it's an AHVA device hence different driver needed to IPS/LVDS screens. I'm guessing its model number is B101uan (http://www.revo-sys.com/b101uan021-a...n-optional.php). I can see a driver in the rockchip tree (https://github.com/dnkn/rk3188_table...no_1920x1200.c).

Do you think you can do a quick compile swapping to this LCD for me to test? I should have my laptop back on Monday night and so can join you in figuring this out from Tuesday (work allowing!)

[linkages]

3723[/ATTACH]

You flash from Linux? How? I hate having to keep a windows machine around to flash my tablet. Can you point me at the tools please. Thanks.

[900supersport]

rkflashtool does a good job at flashing kernel.

[leolas]

Re: rk3188 tablet kernel sources

rkflashtool does a good job at flashing kernel.

Agree is the fastest way to test them

leolas.

[dnkn]

DNKN,

Firstly - superb work!

Second, I think I've worked out the display on the M8HD, it's an AHVA device hence different driver needed to IPS/LVDS screens. I'm guessing its model number is B101uan (http://www.revo-sys.com/b101uan021-a...n-optional.php). I can see a driver in the rockchip tree (https://github.com/dnkn/rk3188_table...no_1920x1200.c).

Do you think you can do a quick compile swapping to this LCD for me to test? I should have my laptop back on Monday night and so can join you in figuring this out from Tuesday (work allowing!)

I gave you a kernel with that config selected, but you had blank screen, so may be just LCD_EN gpio is different.

[d33]

Re: rk3188 tablet kernel sources

I gave you a kernel with that config selected, but you had blank screen, so may be just LCD_EN gpio is different.

Ah right. How did you work out all the necessary gpios when you were building the m9 max?

Sent from my M8HD using Tapatalk

[dnkn]

Ah right. How did you work out all the necessary gpios when you were building the m9 max?

Sent from my M8HD using Tapatalk

I ran gpio_dump script on stock kernel, then on mine (while with blank screen, it did not power up at first) then examined difference, then looked through code and searched for gpios mentioned. Than I've found the right gpio, which was disabled lcd_en_something and lcd_cs_something as I remember, edited the code , rebuilt the image and vuala , got the screen on.
Also the GPS section of board-ds1006h will lead to flash on on boot, disable it. It is not enabled as it depends on rk_GPS config option, but still it claims gpios , don't know why.

[rrileypm]

Hey guys!!!!!

Like I've said before, I am wholeheartedly in support of your efforts, but I'm pretty overwhelmed with ROM development ATM. I'll keep an eye on these two kernel threads, but not as closely as the ROM threads. If you have a finished product to offer, feel free to post on the specific ROM thread it applies to. Just explain as much as possible what it is, what it's for, what are the pro's and con's...etc... I'm not saying the ROM threads are off limits, but please try to keep kernel discussion short and simple. You still have to spark interest, so you may get people to test for you.

I would love to have a custom kernel for EVERY Pipo device and include them in my ROM's. I realize that isn't realistic, because we don't have every tablet to test with. You may have to recruit some testers with these devices, like I have.

Thanks for the hard work!!!!!!

[d33]

I ran gpio_dump script on stock kernel, then on mine.

In the GPIO info I can see the touchscreen device (VTL CT36x), compass (ak8963), Display controller (ssd2828), wifi (AP6330), accelerometer, (gs_lis3dh), Gyroscope(l3g4200d_gryo) and battery charge controller (oz8806).

Does any of that help?

<4>[ 672.352789] GPIO gpio0 160 poweronpin
<4>[ 672.352852] GPIO gpio0 164 play
<4>[ 672.352866] GPIO gpio0 165 ap6330_wake_host
<4>[ 672.352896] GPIO gpio0 167 ssd2828_reset
<4>[ 672.352938] GPIO gpio0 170 oz8806_dc_det
<4>[ 672.352969] GPIO gpio0 172 l3g4200d_gryo
<4>[ 672.352985] GPIO gpio0 173 rtc gpio
<4>[ 672.352999] GPIO gpio0 174 ct36x_ts_rst
<4>[ 672.353016] GPIO gpio0 175 gs_lis3dh
<4>[ 672.353070] GPIO gpio0 179 camera flash
<4>[ 672.353086] GPIO gpio0 180 ap_ready
<4>[ 672.353101] GPIO gpio0 181 bp_wakeup_ap
<4>[ 672.353116] GPIO gpio0 182 modem_power_en
<4>[ 672.353132] GPIO gpio0 183 modem_usb_en
<4>[ 672.353203] GPIO gpio0 188 ssd2828_spi_miso
<4>[ 672.353220] GPIO gpio0 189 ssd2828_spi_mosi
<4>[ 672.353237] GPIO gpio0 190 ssd2828_spi_sck
<4>[ 672.353255] GPIO gpio0 191 ssd2828_spi_cs
<4>[ 672.353314] GPIO gpio1 195 ap6330_rts
<4>[ 672.353483] GPIO gpio1 207 ct36x_ts_int
<4>[ 672.354114] GPIO gpio2 252 modem_uart_en
<4>[ 672.354131] GPIO gpio2 253 modem_power
<4>[ 672.354145] GPIO gpio2 254 hdmi gpio
<4>[ 672.354190] GPIO gpio3 257 sdmmc-power
<4>[ 672.354205] GPIO gpio3 258 mmc0-clk
<4>[ 672.354219] GPIO gpio3 259 mmc0-cmd
<4>[ 672.354234] GPIO gpio3 260 mmc0-data0
<4>[ 672.354249] GPIO gpio3 261 mmc0-data1
<4>[ 672.354263] GPIO gpio3 262 mmc0-data2
<4>[ 672.354278] GPIO gpio3 263 mmc0-data3
<4>[ 672.354350] GPIO gpio3 268 camera powerdown
<4>[ 672.354366] GPIO gpio3 269 camera powerdown
<4>[ 672.354411] GPIO gpio3 272 mmc1-cmd
<4>[ 672.354425] GPIO gpio3 273 mmc1-data0
<4>[ 672.354440] GPIO gpio3 274 mmc1-data1
<4>[ 672.354455] GPIO gpio3 275 mmc1-data2
<4>[ 672.354471] GPIO gpio3 276 mmc1-data3
<4>[ 672.354486] GPIO gpio3 277 mmc1-clk
<4>[ 672.354500] GPIO gpio3 278 ap6330_wake
<4>[ 672.354531] GPIO gpio3 280 wifi_power
<4>[ 672.354546] GPIO gpio3 281 ap6330_poweron
<4>[ 672.354589] GPIO gpio3 284 ssd2828_shut
<4>[ 672.354630] GPIO gpio3 287 ak8963