1366x768 resolution?

[corruptsector]

I think this can only be done with a Custom Kernel.
I think Omegamoon has something done with this. Must take a look there.

Neomode

Gesendet von meinem GT-I9305 mit Tapatalk 2

Thanks Neomode. That was very fast. Ive seen references to the Omegamoon blog before when people talk about creating custom kernels, but i cant find the information that i need.

Ill Keep looking thanks.

[Machomotofan]

I found a firmware RK3066 tablet with a screen resolution of 1366 * 768
Wexler TAB 10iS

http://wexler.ru/download/10iS_basic.rar

[gerry1980]

Hello together,

I'm glad that I'm not the only one with the demand of that resolution.
I'm looking forward to get the K-R42 running with the Motorola Lapdock as christmas gift for my mother.
And many thanks to wasser, who works on it, too.
I've done some investigations and I will try to make a kernel patch, but it needs some time.
Look here.

Any help is appreciated !

Stay tuned !

[gerry1980]

News and a working patch

Hello together,

I successully run the lapdock with 1366x768, today
by patching two kernel files.

First thing to know, the EDID data from motorola lapdock doesn't provide
any usefull CEA resolutions. I read the EDID block and harvested some info.
If you want... check it out: http://gerrytec.de/LAPDOCK/EDID.7z.

Solution->Step 1:
Change: kernel/drivers/video/rockchip/hdmi/hdmi-core.c
Source: https://www.miniand.com/forums/forum...olution?page=2

Add the following in hdmi-core.c::hdmi_wq_parse_edid() after the line
"rc = hdmi_edid_parse_base(buff, &extendblock, pedid);"
extendblock = 0; // g2t: force the "no CEA-fallback"

In the linked post I tried the so called "better solution" without success.
After this step I was able to set 1280x720. WHOA, what a great improvement
but still not the maximum resolution, yet.

Solution->Step 2:
Add to: kernel/drivers/video/rockchip/hdmi/hdmi-lcdc.o the following (long) line:

    { {     "1366x768p@60Hz",       60,                     1366,   768,    85500000,       256,    58,     17,             1,             112,             3,        FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,                   0,              4       },    91,      1,        OUT_P888    },

so it looks something like this:


This patch works fine for the K-R42 and the T-R42.
And the boxes still running full HD on TV


Greetings from Saarland,
Gerry

[wasser]

Hello together,

I successully run the lapdock with 1366x768, today
by patching two kernel files.

First thing to know, the EDID data from motorola lapdock doesn't provide
any usefull CEA resolutions. I read the EDID block and harvested some info.
If you want... check it out: http://gerrytec.de/LAPDOCK/EDID.7z.

Solution->Step 1:
Change: kernel/drivers/video/rockchip/hdmi/hdmi-core.c
Source: https://www.miniand.com/forums/forum...olution?page=2

In the linked post I tried the so called "better solution" without success.
After this step I was able to set 1280x720. WHOA, what a great improvement
but still not the maximum resolution, yet.

Solution->Step 2:
Add to: kernel/drivers/video/rockchip/hdmi/hdmi-lcdc.o the following (long) line:

    { {     "1366x768p@60Hz",       60,                     1366,   768,    85500000,       256,    58,     17,             1,             112,             3,        FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,                   0,              4       },    91,      1,        OUT_P888    },

so it looks something like this:


This patch works fine for the K-R42 and the T-R42.
And the boxes still running full HD on TV


Greetings from Saarland,
Gerry

i'm uploading new kernel which has the g2t's quick hack and correct gpio for bluetooth and wifi.
It would be great if you could test and post the results, don't forget to post the gpio list with the new kernel

Thanks

[dsank]

EDID Output

Hello together,

I successully run the lapdock with 1366x768, today
by patching two kernel files.

First thing to know, the EDID data from motorola lapdock doesn't provide
any usefull CEA resolutions. I read the EDID block and harvested some info.
If you want... check it out: http://gerrytec.de/LAPDOCK/EDID.7z.

Solution->Step 1:
Change: kernel/drivers/video/rockchip/hdmi/hdmi-core.c
Source: https://www.miniand.com/forums/forum...olution?page=2

In the linked post I tried the so called "better solution" without success.
After this step I was able to set 1280x720. WHOA, what a great improvement
but still not the maximum resolution, yet.

Solution->Step 2:
Add to: kernel/drivers/video/rockchip/hdmi/hdmi-lcdc.o the following (long) line:

    { {     "1366x768p@60Hz",       60,                     1366,   768,    85500000,       256,    58,     17,             1,             112,             3,        FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,                   0,              4       },    91,      1,        OUT_P888    },

so it looks something like this:

This patch works fine for the K-R42 and the T-R42.
And the boxes still running full HD on TV


Greetings from Saarland,
Gerry

Regarding the EDID CEA resolution data, I have a lapdock and wanted to use a kernel for a rk3188 device using linuxium or picuntu. So I was having the same issue, all the tricks with closing the lid havent worked for me either.

I do have a raspberry pi and this works on the lapdock perfectly, here is the EDID output using that device:

Hopefully it will help!

pi@raspberrypi ~/Desktop $ edidparser edid.out
Enabling fuzzy format match...
Parsing edid.out...
HDMI:EDID version 1.3, 1 extensions, screen size 26x14 cm
HDMI:EDID features - videodef 0x80 !standby !suspend !active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor S/N descriptor tag 0xff
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 50-75 Hz, horizontal is 30-85 kHz, max pixel clock is 150 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is MotoAttach
HDMI:EDID found preferred DMT detail timing format: 1366x768p @ 60 Hz (86)
HDMI:EDID established timing I/II bytes are 00 00 00
HDMI:EDID standard timings block x 8: 0x0101 0101 0101 0101 0101 0101 0101 0101 
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:no, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:1
HDMI:EDID found DMT detail timing format: 1366x768p @ 60 Hz (86)
HDMI:EDID found DMT detail timing format: 1366x768p @ 60 Hz (86)
HDMI:EDID failed to find a matching detail format for 0x1080i hfp:88 hs:44 hbp:-116 vfp:2 vs:5 vbp:16 pixel clock:0 MHz
HDMI:EDID calculated refresh rate is 0 Hz
HDMI:EDID guessing the format to be 0x1080i @24 Hz
HDMI:EDID found unknown detail timing format: 0x1080i hfp:88 hs:44 hbp:-116 vfp:2 vs:5 vbp:16 pixel clock:0 MHz
HDMI:EDID found CEA format: code 1, 640x480p @ 60Hz 
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz 
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz 
HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48|96|192 kHz, sample size: 16|20|24 bits
HDMI:EDID found HDMI VSDB length 5
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB has no extension fields
HDMI:EDID adding mandatory support for DMT (4) 640x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (2) 720x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (17) 720x576p @ 50Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 43432)
HDMI:EDID best score mode is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MHz (score 45736)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 36864
HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID best score mode is now DMT (86) 1366x768p @ 60 Hz with pixel clock 72 MHz (score 5188835)
HDMI:EDID preferred mode remained as DMT (86) 1366x768p @ 60 Hz with pixel clock 72 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0

[gerry1980]

Hello dsank,

thank you for the information.
Your EDID output confirms my discovered behavior of the rockchip driver.
My previous post is a solution, let me try to explain why.
As you can see in your output, the EDID data results in two available CEA resolutions.
Your Pi graphic driver use the "default" resolution which the driver gets from
the Detailed Monitor Timing (DMT), also stored in EDID.

[B]HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 45736[/B]
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 36864
[B]HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736[/B]
HDMI:EDID [COLOR=#ff0000][B]best score mode is now DMT[/B][/COLOR] (86) 1366x768p @ 60 Hz with pixel clock 72 MHz (score 5188835)

I analized the rockchip drivers behavior on a TV and two monitors.
If there is no valid CEA entry, the rockchip driver works fine.
Thats a fact on all my working devices :-)
But the lapdock delivers valid (but to less) CEA modes and rockchip
consequently just recognize them.

With the first patch in my post we can fix exactly that issue.
The second patch just adds the 1366x768 resolution.

Wasser added this patches to his kernel
I will check it out tonight.

... YEAH, it works !

Gerry

[dsank]

Hello dsank,

thank you for the information.
Your EDID output confirms my discovered behavior of the rockchip driver.
My previous post is a solution, let me try to explain why.
As you can see in your output, the EDID data results in two available CEA resolutions.
Your Pi graphic driver use the "default" resolution which the driver gets from
the Detailed Monitor Timing (DMT), also stored in EDID.

[B]HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 45736[/B]
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 36864
[B]HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736[/B]
HDMI:EDID [COLOR=#ff0000][B]best score mode is now DMT[/B][/COLOR] (86) 1366x768p @ 60 Hz with pixel clock 72 MHz (score 5188835)

I analized the rockchip drivers behavior on a TV and two monitors.
If there is no valid CEA entry, the rockchip driver works fine.
Thats a fact on all my working devices :-)
But the lapdock delivers valid (but to less) CEA modes and rockchip
consequently just recognize them.

With the first patch in my post we can fix exactly that issue.
The second patch just adds the 1366x768 resolution.

Wasser added this patches to his kernel
I will check it out tonight.


Gerry

Thanks Gerry!

I am trying to compile a Kernel for a rk3188 device, wassers kernel is for a rk3088 device.

Would you be able to provide instructions for how you went about compiling?

Many Thanks in Advance!

[gerry1980]

Thanks Gerry!

I am trying to compile a Kernel for a rk3188 device, wassers kernel is for a rk3088 device.

Would you be able to provide instructions for how you went about compiling?

Many Thanks in Advance!

Hello dsank,

wassers kernel is for the rk3188. But not every kernel is the same and supposed to be running on each device. I can support you with basic steps of kernel compiling, but you have to know the fundamentals of linux, crosscompiling and maybe some progamming skills. No offence, but I don't know your skills.
For a good explanation, look at http://www.freaktab.com/showthread.p...rk3066-devices. Furthermore, there are lot of kernel sources out there, so I don't know which is the best one for your device and what fixes the different sources has (To speak frankly, thats a mess! And I hope that there will be a project structure likewise Freetz or OpenWrt in the future). I use wassers kernel, because his kernel works great on my K-R42 and T-R42 and interact good with his FW image. Unfortunately, I don't know on which source his kernel is based on and what else he has fixed.

Here are some kernel sources.

http://www.freaktab.com/showthread.php?5795-Some-Kernel-sources-in-github

I heard something about a kernel config helper tool for multiple device configs.
But I don't have the time to check it out, yet. It's name is marvin and I'm looking forward to it.

Maybe I could help you a little bit. Feel free to ask if something is unclear.


Greeting,
Gerry

[dsank]

Thank you very much for the Tips!

Do you mind providing the following files you used, as I would like to compare:
- hdmi-core.c
- hdmi-lcdc.o

Cheers!

[gerry1980]

Thank you very much for the Tips!

Do you mind providing the following files you used, as I would like to compare:
- hdmi-core.c
- hdmi-lcdc.o

Cheers!

Hello dsank,

here are my 2 files. I added some additional log output, because it was needed for debugging purpose.

[ATTACH]4189[/ATTACH]
[ATTACH]4190[/ATTACH]

cya,
Gerry

[dsank]

Thanks, although that did not work for me, are you able to let me know the source code you had used?

It would be great to if you could upload your kernel and the files you compiled

I have the mk802iv so I just want to see the differences.

Did you edit the "rk_hdmi.h" at all?

Many Thanks!

[gerry1980]

Hello,

Sorry, I was far away from home last days. I'm available again ;-)

To get the source do the following steps.
1. git clone https://github.com/thesawolf/android_kernel_rockchip_rk3188
2. Replace the following two files (remove txt extension, first ;-)).
hdmi-core.c.txt
hdmi-lcdc.c.txt

This 2 files are the only ones I touched but in my last post I sent you a file with the patch, but it was commented out because of debugging issues. Sorry for that! Hope that this gets you a working solution, now.

Greetings,
Gerry

[davidw]

Hello. I don't know if anyone here can help me but I have a Minix Neo X5 which is a 3066-based device. I have troubles with it - almost every time the TV to which it is attached is powered on, the Neo crashes. I have been trying for some time now to compile a kernel (I am using Finless 1.3 which is 4.2.2 on a 3.0.36+ kernel) but without success. At best, my results do not boot. At worst, they soft-brink the device requiring Mask ROM mode to recover. This TV also has a 1366x768 native resolution so that too would nice to have. But right now I mostly want to be able to enable HDMI debugging so I can maybe see what is causing the crashes. They never happen on an HD computer monitor nor has it happened on other TVs. Only my Vizio VA-26L. So if someone can help me find a "correct" kernel repository and config for my Neo X5 and other info that might help me get a kernel that works, I can really use the help. Thanks